Connect Slack
Send account digests, hot-lead alerts, and personalization-health notifications to Slack.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
Connect
- In Integrations → Connections, choose Slack → Set up. Authorize the intended workspace.
- Select a channel separately for Pulse digest, Hot leads, and Personalization health, then enable each purpose you want.
- Set digest cadence in Sales → Pipeline; a channel alone does not override a disabled cadence.
Verify the result
Send test posts a real message to the selected channel. Verify the channel and the last-delivery status.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Invite the app if it cannot post to a private channel. If the deployment says the Slack app is not configured, contact the AXO operator. Disconnect stops AXO posting; remove the Slack app in Slack to revoke it there too.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.