2. Choose channels
Crawle lists available Slack channels after authorization so each workspace or site can send notifications to the right place.
Use channel search when the workspace has many channels.
Pick one default channel for workspace-level digests.
Override the channel for high-risk sites when a client or team needs a dedicated feed.
Send a test notification before enabling production alerts.
3. Match Slack to alert policy
Slack delivery follows the same alert windows and recipient rules as email and Teams.
Keep critical incidents real-time when fast action matters.
Use daily digests for noisy lower-priority changes.
Route parameter traps and suppression suggestions to a channel someone actually reviews.
Review recipient settings when teammates belong to multiple workspaces.
Troubleshooting
Most Slack issues are caused by installing the wrong workspace, missing channel access, or testing before the app has finished authorization.
Reconnect Slack if the channel list is empty or belongs to the wrong workspace.
Invite the Crawle app into private channels before selecting them.
Use the test notification button after every channel change.
Check alert windows if real-time alerts work but daily digests do not appear yet.
Private beta note
Crawle is currently invite-only. Some features depend on workspace permissions, connected accounts, API quotas, or integration setup by the organization.