Contact Event Subscriptions
Choose which workspace contact events should post Slack alerts and how each alert should be formatted.
An event subscription connects a Slack destination to one or more contact lifecycle events. Leadpush sends a Slack delivery when a subscribed event happens and both the subscription and destination are enabled.
Before you start
- Create at least one Slack destination.
- Send a test delivery to confirm the destination works.
- Decide which contact events should produce Slack alerts.
- Draft the text fallback and optional Block Kit message for the alert.
- Make sure you are in the correct workspace.
Create an event subscription
Open Slack
Open Integrations, choose Slack, and go to Event Subscriptions.
Create a subscription
Click Create Subscription.
Choose a destination
Select the Slack destination that should receive the alerts.
Name the subscription
Use a recognizable name, such as Lifecycle Alerts or Unsubscribe Watch.
Select events
Choose one or more contact lifecycle events.
Configure the Slack message
Enter a required text fallback and optional Block Kit JSON. Use message presets or template variables when helpful.
Save the subscription
Save the subscription and leave it enabled when alerts should start immediately.
Supported contact events
| Event | Use it when |
|---|---|
contact.created | A team should know when a new contact is created. |
contact.updated | A team should know when contact profile or attribute data changes. |
contact.deleted | A team should know when a contact is removed. |
contact.subscribed | A team tracks contacts becoming subscribed. |
contact.unsubscribed | A team tracks unsubscribe events. |
Delivery behavior
Leadpush only sends a contact event Slack delivery when:
- the event subscription is enabled
- the destination is enabled
- the subscription includes the event type
- the event belongs to the same workspace as the destination
- the rendered text fallback is not empty
- the rendered Block Kit JSON is valid when blocks are configured
If a destination is disabled, Leadpush does not create new contact event deliveries for that destination.
Subscription strategy
Use separate subscriptions when teams need different messages or different event sets. For example:
- send
contact.createdandcontact.updatedto a revenue operations channel - send
contact.unsubscribedto a compliance channel - send all lifecycle events to an internal audit channel
Use one subscription with multiple events when the same Slack message format and destination should handle the same payload family.
Edit or disable a subscription
Edit a subscription when you need to change the destination, name, enabled state, selected events, text fallback, or Block Kit template.
Disable a subscription when you want to pause new alerts but keep the configuration. Deleting a subscription stops future deliveries for that subscription. Existing delivery history remains tied to delivery records that were already created.