Slack
Wrangler can post to a Slack channel when a ticket is opened, when a customer replies, and when a ticket is assigned. Each post shows the reference, the subject, who it is from, the start of the message, and an Open ticket button that goes straight to it in the control panel.
Connecting it
You create a small Slack app whose only permission is posting to one channel, then copy its webhook URL into Wrangler. It takes about two minutes. Slack redesigns these screens from time to time, so the wording may drift a little; what you are after is always an incoming webhook.
- Go to api.slack.com/apps, signed in to your workspace, and click Create New App.
- Under From scratch, choose Pick features and click Continue. (Not the AI agent or Starter app templates — Wrangler needs neither.)
- Give the app a name — Support — and pick your workspace.
- When asked what the app can do, choose Post messages. Its permission is shown as
incoming-webhook, and it is the only one needed. - When asked what it can respond to in Slack, add nothing. Leave the events empty and click Continue. Wrangler only posts; it never reads anything in Slack.
- On Review your app, check that What it can do in Slack lists just Post messages — incoming-webhook, then click Create and Install.
- Slack asks which channel the app may post to. Pick it —
#support, say — and click Allow. For a private channel you need to be a member of it first. - On the app's settings page, open Incoming Webhooks in the left menu. The webhook is listed
there: copy the URL that starts
https://hooks.slack.com/services/. - In Wrangler, paste it into Settings → Slack → Slack webhook URL, tick the events you want, and save.
- Click Send a test message on the settings page. A wave message should appear in the
channel. If Slack refuses it, the reason is shown right there —
no_servicemeans the webhook was removed in Slack, andchannel_not_foundmeans the channel was archived.
If your workspace only lets admins install apps, step 6 sends a request to an admin instead, and the webhook appears once they approve it.
Or paste a manifest
At step 2, Paste a manifest does steps 3 to 6 in one go. Paste this, then carry on from step 6:
{
"display_information": { "name": "Support" },
"features": { "bot_user": { "display_name": "Support", "always_online": false } },
"oauth_config": { "scopes": { "bot": ["incoming-webhook"] } }
}
Another channel later
Back on the app's Incoming Webhooks page, Add New Webhook creates a URL for a different channel. Wrangler posts to one channel per site; paste whichever URL you want it to use.
Treat the webhook URL like a password: anyone with it can post into that channel.
What gets posted
| Event | Post |
|---|---|
| A ticket is opened | Reference, requester, subject, custom field answers, the first 400 characters of the message, priority and queue. |
| A customer replies | Who replied, the ticket, the start of the reply, and who it is assigned to. Covers replies by email too. |
| A ticket is assigned | Who assigned it to whom. Self-assignment is posted too, so the channel can see who took what. |
Staff replies and internal notes are never posted. Anything a customer typed is escaped, so a
message containing @channel or <!here> cannot ping your workspace.
Posts follow the same notification ceiling as email: if the ceiling trips during a flood of spam, Slack goes quiet too.
If Slack is down
A failed post is written to the developer log and nothing else happens: the ticket is saved and the emails still go. Each post waits at most four seconds for Slack, so a slow Slack cannot make your support form hang.
Discord, Mattermost and others
- Discord: create a webhook in the channel's settings (Integrations → Webhooks), copy its URL
and add
/slackto the end. Discord then accepts Slack's format. - Mattermost and Rocket.Chat: their incoming webhooks accept this format as they are.
- Microsoft Teams uses a different format and is not supported here. A small extension on Wrangler's hooks can post to it.
More control
To send urgent tickets to one channel and the rest to another, or to format posts differently, use the developer hooks in your own extension instead.