Freshdesk n8n integrationAutomate Freshdesk with n8n.

Adds a person to your Freshdesk contact list and returns the created record with its ID, ready for the next node.

• Name: the only required field, the display name of the contact, often {{ $json.name }} from a form or CRM step.
• Email: the primary address. Extra addresses belong in Other Emails instead of this field.
• Additional Fields: 17 optional attributes, including Phone, Company ID, Tags and Unique External ID, useful to carry the identifier your own database already uses.

When someone asks to be removed from your helpdesk records, this operation deletes their contact in Freshdesk.

• Contact ID: the Freshdesk identifier of the person to remove, not their name or email. Pull it from a previous Get many contacts step with an expression such as {{ $json.id }}, which reads a field from the incoming item.

Fetches one contact and returns the full record, so later nodes can read the fields instead of guessing them.

• Contact ID: the identifier of the contact to read. A required field blocks the node when it is empty, so make sure the previous step really produced an ID.

Lists contacts in bulk, with filters that narrow the batch before it reaches the rest of the workflow.

• Filters: 6 optional criteria, Company ID, Email, Mobile, Phone, State and Updated Since.
• State: one of verified, unverified, blocked or deleted, the fastest way to isolate accounts that never confirmed their address.
• Updated Since: a date that keeps a scheduled run from reprocessing the whole list every time.

People change jobs, numbers and companies. This operation writes those changes onto an existing Freshdesk contact without creating a duplicate.

• Contact ID: the record to modify, typically carried over from an earlier lookup.
• Additional Fields: the same 17 attributes as on creation. Only what you fill gets written, so a run can set Job Title alone and leave the rest untouched.
• View All Tickets: lets the contact see every ticket from their company, handy for a named account manager.

Opens a ticket in Freshdesk from whatever the workflow just received, and returns the created ticket for the rest of the run.

• Requester Identification and Value: how Freshdesk recognizes the person, by email, phone, requesterId, twitterId, facebookId or uniqueExternalId. With an unknown email, Freshdesk creates the contact for you.
• Status, Priority, Source: all three are required. Source records the channel, from chat to portal.
• Options: 13 extras, among them Subject, Description in HTML, Due By and Agent Name or ID.

Some tickets should never have reached the queue. Spam, a duplicate from a retried workflow, a test run left behind. This removes one of them.

• Ticket ID: the identifier of the ticket to delete. Feed it from the ticket you just created, {{ $json.id }}, when a branch decides the ticket was a mistake.

Reads one ticket and hands back its current state. That is what you need before a workflow decides anything about it, because the status may have moved since the ticket was created.

• Ticket ID: the ticket to read. Store it when you create a ticket, then reuse it later in the same workflow or in a follow-up one.

Pulls a batch of tickets out of Freshdesk, which is the starting point of every report and every survey built on this node.

• Return All: enabled, n8n walks the API pages and brings back every matching ticket; disabled, Limit caps how many come through.
• Options: 7 refinements, including Updated Since, Requester Email, Order By and Include to attach requester, company, description or stats to each ticket.

Most support automation ends here: the ticket exists, and something about it has to change without an agent opening it.

• Ticket ID: the ticket to modify, the only required value.
• Update Fields: 16 attributes, including Status, Priority, Agent Name or ID, Group Name or ID, Tags and Type (Incident, Problem, Question, Feature Request, Refund).
• Due By and FR Due By: the resolution deadline and the first response deadline, if your process recalculates them.