Connect
Apps and webhooks
Post into a channel from other tools.
An app posts into one channel with a secret token. Workspace admins create apps in Settings → Apps & webhooks: choose a name and a channel; the token is shown once. Messages appear from an "App" user with an App mark and follow every normal rule (rate limits, mentions, unread counts, search, pins, retention).
#Incoming webhook
curl -X POST 'https://<your-work-address>/api/hooks/<token>' \
-H 'content-type: application/json' \
-d '{"text": "Build **passed** :tada:"}'text is required (up to 4,000 characters, same formatting as typed messages). Add threadId to reply in a thread. The URL is the credential — keep it private.
#Bot API
Send the same token as a header. POST /api/bot/messages with {"text", "threadId"?} posts as the app; add an Idempotency-Key header so a retried request posts only once. GET /api/bot/me checks a token and shows where it posts.
#Limits and safety
- Up to 60 messages a minute and 2,000 an hour per app (
429withRetry-Afterif faster). - Apps can do one thing only: post to their channel. They cannot receive direct messages.
- Only a hash of the token is stored, so a lost token cannot be recovered, only replaced. Remove an app to stop its token immediately; what it already posted stays.
- A private channel's app can only be created by someone in that channel.
#Outgoing webhooks
Settings → Outgoing webhooks sends each new message to your address, so other systems can react to conversations.