Slack
Send contact lifecycle alerts and campaign workflow messages to Slack with reusable incoming webhook destinations, text fallbacks, Block Kit templates, and delivery monitoring.
The Slack integration lets Leadpush post messages to Slack through incoming webhook destinations. A destination stores the Slack webhook endpoint, event subscriptions decide which contact lifecycle events should produce Slack alerts, and campaign workflow Slack nodes send messages when an automation step runs.
What Slack can do
Use Slack destinations to notify teams about:
- new contacts entering a workspace
- contact profile or subscription changes
- contacts being deleted
- important campaign workflow steps
- test messages while configuring an alert
Slack destinations are reusable. The same destination can receive contact lifecycle event subscriptions and campaign workflow Slack actions.
Setup flow
Create a Slack destination
Create a destination with a name, Slack incoming webhook URL, timeout, and enabled state.
Send a test delivery
Use the destination row action to send a slack.test delivery and confirm the message reaches Slack.
Add contact event subscriptions
Create subscriptions for the contact lifecycle events that should post alerts to Slack.
Configure message templates
Use a required text fallback and optional Block Kit JSON. Add template variables such as {{ event.type }} and {{ contact.attributes.email }} where each message needs event context.
Use Slack in campaigns
Add a Send Slack node to a campaign workflow when a campaign step should notify a Slack channel.
Monitor delivery history
Review rendered text, rendered blocks, Slack responses, attempts, and failed retries from the delivery history.
Supported events
| Event | When it is sent |
|---|---|
contact.created | A contact is created in the workspace. |
contact.updated | A contact profile or attributes are updated. |
contact.deleted | A contact is deleted. |
contact.subscribed | A contact becomes subscribed. |
contact.unsubscribed | A contact becomes unsubscribed. |
slack.test | A manual test delivery is sent from a destination or workflow node. |
campaign.slack | A campaign workflow Send Slack node runs. |
Contact event subscriptions can only select contact lifecycle events. Test and campaign Slack deliveries appear in delivery history for monitoring and troubleshooting.
Message requirements
Every Slack message needs text fallback content. Block Kit JSON is optional and must be a JSON array of blocks.
Template variables are rendered before the message is sent. If a variable path is not available for the event, Leadpush renders it as an empty string.
Guides in this section
- Create Slack destinations
- Contact event subscriptions
- Message templates and Block Kit
- Campaign workflow Slack actions
- Test, monitor, and retry deliveries