Zintara Slack notification troubleshooting: test connection and event selection

Define the decision

A successful connection test posts a generic message. It does not prove every selected event will be emitted, and the channel hint does not reroute the Slack webhook. Inspect the actual channel and selected event names.

Work through the procedure

1. Confirm the correct Zintara workspace and active Slack connection.
2. Check the enabled event list.
3. Run an intentional test to the approved channel.
4. If it fails, inspect sanitized provider errors and whether the incoming webhook remains valid.
5. If it succeeds but an alert is missing, investigate the originating event and application logs.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Test message: appears
Expected alert: import_completed
Saved selection: reply and bounce only
Diagnosis: event not selected, rather than a broken Slack connection

Read the result

The branch keeps secret rotation from becoming the default response to every missing alert. A real posting error can also happen after an event was generated because alerts are sent best-effort.

Check before moving on

1. Never paste the full hooks.slack.com URL into a ticket.
2. Verify channel membership is appropriate for notification content.

Limits and next action

No automatic replay of missed Slack alerts is promised. Use Zintara’s underlying records for recovery and treat the channel as an operational notification surface.

Source: Zintara implementation and product context