Skip to main content
For “candidate passed → hiring channel”, add a Slack destination under Developer → Destinations. Slack destinations do not use HMAC — Assess posts a formatted chat message.

​
If you are recruiting / ops

1

Connect Slack

In Developer → Destinations, choose Slack and click Connect Slack. Slack asks the org to install Praxicraft’s bot into their workspace — they do not create a Slack app or paste a client secret. After that, pick a channel. Assess posts with chat.postMessage.
2

Or paste an Incoming Webhook

Slack Incoming Webhook URLs (hooks.slack.com) still work as a fallback if Connect Slack is missing.
3

Subscribe and test

Subscribe to candidate.passed (and optionally candidate.failed, assessment.completed). Send a test ping.
Connecting a workspace is a one-time dashboard step. After that, POST /webhooks/create/ can use slack_channel_id with no url.
Prefer a Slack destination in Assess for simple pass/fail alerts. Use Zapier / n8n / Make Slack steps when you need extra routing (email, ATS, spreadsheets).

​
For engineers

Destinations use the same Public API as HTTPS webhooks: /webhooks/. There is no separate /destinations/ path. See Webhooks for create, test, deliveries, and retry. After Slack is connected in the dashboard:
HTTPS destinations still use whsec_… and X-Praxicraft-Signature. Slack destinations do not.

​
Next

Teams · Webhooks · Automations · Integrations
Last modified on August 24, 2026