Create Slack Destinations
Store the Slack incoming webhook endpoint Leadpush posts to for contact alerts, test messages, and campaign workflow notifications.
A Slack destination stores one Slack incoming webhook endpoint for a workspace. It includes the destination name, enabled state, incoming webhook URL, and timeout setting.
Before you start
- Create or choose a Slack incoming webhook URL for the channel that should receive Leadpush messages.
- Confirm the URL begins with
https://hooks.slack.com/services/. - Decide whether this destination is for operational alerts, lifecycle alerts, campaign notifications, or testing.
- Use a destination name that identifies the Slack channel or purpose, such as
Lifecycle AlertsorCampaign Ops.
Leadpush only accepts Slack incoming webhook URLs on hooks.slack.com with a /services/ path. Do not paste a Slack channel URL, workflow URL, or URL from another service.
Create a destination
Open Integrations
Open the dashboard, choose a workspace, and select Integrations from the sidebar.
Open Slack
Choose Slack from the integrations list.
Create a destination
On the Destinations tab, click Create Destination.
Configure the endpoint
Enter the destination name, incoming webhook URL, timeout, and enabled state.
Save the destination
Create the destination. Leadpush stores the webhook URL and shows whether an incoming webhook is configured.
Send a test
Use the destination row action to send a test message before subscribing events or using the destination in a campaign.
Destination fields
| Field | Purpose |
|---|---|
| Name | A human-readable label for the Slack receiver. |
| Enabled | Controls whether Leadpush can deliver to the destination. |
| Incoming Webhook URL | The Slack webhook endpoint Leadpush posts to. |
| Timeout Seconds | How long Leadpush waits for Slack to respond. |
Editing destinations
When you edit a destination, the incoming webhook URL field is blank by default. Leave it blank to keep the existing Slack URL. Enter a new incoming webhook URL when the Slack app, channel, or workspace receiver changes.
Use edits for changes such as:
- renaming a destination after a channel rename
- disabling a destination temporarily
- replacing a Slack incoming webhook URL
- adjusting the timeout for slower Slack responses
Enable, disable, and delete
Disable a destination when you want to pause Slack deliveries without losing configuration or delivery history. Disabled destinations do not send contact event alerts or campaign workflow Slack messages.
Delete a destination when it should no longer be used. Deleting a destination also removes its event subscriptions and related delivery records.
Destination strategy
Use separate destinations when messages need to go to different Slack channels or when different teams own different alert streams. For example:
Lifecycle Alertsfor contact created, updated, and deleted notificationsCompliance Alertsfor unsubscribe notificationsCampaign Opsfor workflow Slack nodes in active campaigns
Use one destination when the same Slack channel should receive all Leadpush messages.