When a ticket is created in Freshdesk, send ticket details to n8n.io

Each new Freshdesk ticket is passed to n8n.io with the ticket details you map, so an n8n workflow you’ve already built can pick it up and carry on from there.

Freshdesk

n8n.io

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 885 sites Free to import

The When a ticket is created in Freshdesk, send ticket details to n8n.io workflow on the FlowMattic canvas, with 2 steps across Freshdesk, n8n.io — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

If part of your support process already lives in n8n.io, new Freshdesk tickets need to reach it somehow. This workflow is the bridge: FlowMattic listens for the ticket, then hands its details to n8n, where your own nodes decide what happens next.

The Freshdesk trigger, New Ticket, fires when a ticket is created in your helpdesk. The ticket's data, such as its subject, description and requester, becomes available to map. The second step is Submit Data from n8n.io. It sends the ticket fields you map to n8n, where a workflow that starts with a Webhook node receives them.

FlowMattic sends the data and ends the run there; whatever n8n does with the ticket is set up on the n8n side. Every new ticket is sent, because the template has no Filter. Task History keeps a record of each run, so you can see exactly what was passed to n8n for any ticket.

Classify tickets with an existing n8n flow

You built an n8n workflow that tags and routes support requests. Each new Freshdesk ticket is sent to it as soon as it's created, instead of n8n having to poll the helpdesk.

Copy tickets into an internal database

An n8n workflow writes support data to your own database for reporting. Sending every new ticket from Freshdesk keeps that store filled without a separate export.

Kick off incident handling

Your n8n setup pages the on-call engineer for certain keywords. Passing each new ticket's subject and description lets n8n run that check on every request.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Freshdesk New Ticket
Starts a run each time someone opens a Freshdesk ticket, whether by email, portal or an agent. The ticket's details are passed on so you can choose which of them to send to n8n.io.
Step 2Action
n8n.io Submit Data
Submits the mapped Freshdesk ticket data to n8n.io. Point it at the webhook your n8n workflow listens on, and map the ticket fields your n8n nodes need.

What you need

FlowMatticCore
Freshdesk AccountAccount
n8n.io AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Create a ticket in Freshdesk after import, then copy the exact field names from Task History into your n8n workflow so the node references match what FlowMattic sends.
If n8n only needs some tickets, add a Filter after the trigger on a ticket value such as priority or type. Tickets that fail it never reach n8n.
Map the Freshdesk ticket ID into the data you send, so a later node in n8n can refer back to the original ticket.

Questions about this workflow

Do I need anything set up in n8n.io first?

Yes. The n8n side needs a workflow that starts with a Webhook node to receive the data. FlowMattic sends the ticket to that webhook; the steps after it are built in n8n.

Are Freshdesk ticket replies and updates sent to n8n too?

No. The New Ticket trigger fires when a ticket is created. Later replies, status changes or edits to that ticket don't start this workflow.

What if my n8n workflow is turned off when a ticket arrives?

The Submit Data step likely gets an error response from n8n instead of a success, and Task History shows that error for the run. Turn the n8n workflow back on, then check recent runs for tickets that weren't received.

Can n8n send results back to FlowMattic?

Not in this template. FlowMattic has a separate n8n.io Receive Data trigger, so you can build a second workflow that starts when n8n posts data back.