triage/signal connects to Zendesk, Jira, Salesforce, and anything else in your stack through a plain outbound webhook — no native app or developer required. Zendesk Triggers, Jira Automation's "Send web request," and Salesforce Flow's HTTP Callout all work the same way. This guide walks through it using Zapier's "Webhooks" action, since it's the fastest path if you haven't wired a webhook by hand before — five minutes, start to finish.
Grab a free key from the triage/signal homepage — no card needed, 3 calls/month free, then $0.02/call with no minimum.
Pick whatever creates a new support ticket, review, or message for you — common ones:
| Trigger app | Event |
|---|---|
| Zendesk | New Ticket |
| Intercom | New Conversation |
| Gmail | New Email Matching Search |
| Google Forms / Typeform | New Response |
| Shopify | New Order Note / Review app webhook |
Choose POST, then configure it to call the API:
| Field | Value |
|---|---|
| URL | https://triagesupport.com/analyze |
| Payload Type | json |
| Data → text | map to the ticket/message body field from your trigger |
| Headers → x-api-key | your API key from step 1 |
| Headers → Content-Type | application/json |
# what Zapier sends, roughly equivalent to:
curl -X POST https://triagesupport.com/analyze \
-H "x-api-key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "{{ticket_body}}"}'The webhook step's output gives you three fields to use in the rest of your Zap:
| Field | Example |
|---|---|
sentiment | negative / neutral / positive |
urgency | low / medium / high |
reason | short phrase explaining the urgency |
Add a Filter by Zapier step: only continue if urgency exactly matches high. Then add whatever should happen next — a Slack message to your team channel, an SMS, a priority label in your helpdesk, or a task in your project tool.