Skip to main content
For more information on destinations, see the Destinations page. A Slack destination delivers messages to a Slack channel using a Slack incoming webhook. It’s a great fit for Notifications or quickly testing webhook payloads. For example, posting a message to your team’s channel whenever a customer connects an integration or a sync runs into an error may be a good fit for this destination.

​
Setting up a Slack destination

  1. In Slack, create a Slack app (or use an existing one), enable Incoming Webhooks, and add a webhook to the channel you want Ampersand to post to. Slack gives you a URL that looks like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXX.
  2. In the Ampersand Dashboard, add a new destination of type Slack and paste in that URL. (The URL must be a hooks.slack.com URL.)
The Slack channel is fixed when you create the incoming webhook. Ampersand posts to that channel and cannot override it.

​
Notifications

Notifications are rendered as a short, human-friendly sentence, followed by the raw notification payload for full detail. For example, a connection.error notification appears as:
⚠️ Salesforce connection for Acme (ID conn_123) encountered an error: The refresh token is invalid or expired
You can route notification events to a Slack destination the same way as any other destination. See the Notifications overview for setup.

​
Read & subscribe data

Data read via Read Actions or Subscribe Actions is delivered as the JSON payload nested directly into the Slack message text.
Slack renders roughly 16-20 KB per message and silently truncates anything larger. The request still succeeds, so oversized content is dropped without an error. Be careful using Slack destinations for data delivery: a large record or batch may be cut off. For anything beyond small payloads, use a webhook, Kinesis, or S3 destination instead.