Webhooks & Integrations
Connect FyneDesk to the tools your team already uses. Send ticket events to another system, or let a trusted system create tickets and add comments through a secure incoming endpoint.
What are webhooks
A webhook is an automated message sent from FyneDesk to another application when something happens. Instead of checking FyneDesk manually or polling for updates, your other tools get notified instantly.
For example, when a new ticket is created, FyneDesk can immediately send a notification to your team's Slack channel. When a ticket is marked urgent, it can trigger an alert in PagerDuty or Microsoft Teams. When a ticket is resolved, it can update a row in Google Sheets or your CRM.
Use webhooks in both directions
Outbound webhooks send ticket events from FyneDesk to Slack, Microsoft Teams, Zapier, n8n, Make, PagerDuty, or a custom API.
Inbound webhooks give a trusted external system its own endpoint in FyneDesk. A signed event can create a ticket or add a comment to an existing ticket. This works well for monitoring tools, internal apps, order systems, and operational alerts.
Inbound and outbound webhooks are available on Pro and Business. Configure them in Admin → Settings → Developer & Data → Connections → Webhooks.
What events can trigger a webhook
FyneDesk can send a webhook notification when any of these ticket events occur:
- Ticket created - a new ticket is submitted by a customer, agent, or via email
- Status changed - a ticket moves from one status to another (e.g., New to Active, Active to Resolved)
- Priority changed - a ticket's priority is updated (e.g., Low to Urgent)
- Ticket assigned - a ticket is assigned to an agent or team
- Comment added - a new comment is posted on a ticket
You choose which events each webhook listens for. Set up one webhook for everything, or create separate webhooks for different events going to different destinations.
Where you can send webhooks
FyneDesk sends a standard HTTP POST request with a JSON payload, which means it works with virtually any modern tool or platform:
- Slack - post ticket updates to a channel using Slack's incoming webhook URL
- Microsoft Teams - send alerts to a Teams channel via a webhook and a Power Automate flow. See the step-by-step guide →
- Discord - notify a Discord channel when tickets need attention
- Zapier - use a Zapier webhook trigger to connect FyneDesk to 6,000+ apps
- n8n - route events through n8n workflows for advanced automation
- Make (Integromat) - build multi-step scenarios triggered by FyneDesk events
- Your own API - send events to any custom endpoint you control
Setting up a webhook
You need to be an Admin. In the left sidebar, open Admin, then Settings. Under Developer & Data, choose Webhooks.
- 1 Click Add Webhook to create a new webhook endpoint.
- 2 Give it a name (e.g., "Slack - Support Channel" or "Zapier - CRM Sync") so you can identify it later.
- 3 Paste the destination URL. This is the webhook URL from your receiving tool (Slack, Zapier, n8n, or your own API).
- 4 Select which events should trigger this webhook.
- 5 Save. FyneDesk will start sending events to that URL immediately.
You can add multiple webhooks pointing to different destinations, each listening for different events. You can also enable or disable individual webhooks without deleting them.
Common use cases
Get Slack alerts for new tickets
Create an incoming webhook in Slack, paste the URL into FyneDesk, and select the "Ticket created" event. Every new ticket will post a message to your team's channel with the ticket title, priority, and a link to open it in FyneDesk.
Escalation alerts for urgent tickets
Set up a webhook that triggers on "Priority changed" and point it at a dedicated Slack channel or PagerDuty. Your on-call team gets notified the moment any ticket is escalated to Urgent.
Sync tickets to a CRM or spreadsheet
Use Zapier or n8n to catch FyneDesk webhook events and push ticket data into Salesforce, HubSpot, Google Sheets, Airtable, or any tool your team tracks customer interactions in.
Build custom internal workflows
Point webhooks at your own API endpoints to trigger custom logic. Auto-assign tickets based on content, create tasks in your project management tool, or log support activity in your data warehouse.
Frequently asked questions
Does FyneDesk support webhooks?
Yes. Pro and Business support outbound ticket events and secure inbound endpoints that can create tickets or add comments.
How are incoming webhook endpoints protected?
FyneDesk verifies a timestamped HMAC signature before accepting an event. Each endpoint also has an action allowlist, optional source IP restrictions, secret rotation, enable and disable controls, and an event log.
Can I connect FyneDesk to Slack or Microsoft Teams?
Yes. FyneDesk webhooks send standard JSON payloads over HTTP. You can connect directly to Slack and Microsoft Teams using their incoming webhook URLs, or use automation platforms like Zapier and n8n to route events to any tool. See our Microsoft Teams setup guide for step-by-step instructions.
Does FyneDesk integrate with Zapier or n8n?
Yes. FyneDesk sends webhook events as standard HTTP POST requests with JSON payloads. Point them at a Zapier webhook trigger, an n8n webhook node, or a Make scenario to connect FyneDesk to thousands of other applications.
Is there a limit on how many webhooks I can create?
You can create multiple webhooks, each pointing to a different destination and listening for different events. There is no hard limit on the number of webhook endpoints.
What format does the webhook payload use?
FyneDesk sends a standard JSON payload via HTTP POST. The payload includes the event type, ticket details, and relevant metadata. This format is compatible with virtually every modern automation tool and API.