Freshworks CRM n8n integrationAutomate Freshworks CRM with n8n.

Adds an account to Freshworks CRM. Only the name is mandatory, so a short web form is enough to open a clean record that the sales team can enrich later.

• Name: name of the account, the one required field, usually mapped from the incoming item with an expression such as {{ $json.field }}.
• Additional Fields: an optional collection of 17 entries, among them Website, Industry Type Name or ID, Number of Employees and Owner Name or ID, the user the account is assigned to.

Removes one account from Freshworks CRM. The node works from the record identifier and not from the company name, so the id has to arrive from a lookup or from an earlier step of the workflow.

• Account ID: ID of the account to delete. Take it from a previous node with {{ $json.field }} rather than typing it by hand, so the workflow stays reusable.

Reads a single account back out of Freshworks CRM. This is the usual way to give a workflow the context the triggering system never had, since a form or a payment webhook rarely knows who owns the account.

• Account ID: ID of the account to retrieve, the only field the operation needs.

Pulls a list of accounts, scoped by a view. Views are the saved lists configured inside Freshworks CRM, and the node asks for one before it returns anything.

• View Name or ID: required. Pick the view from the list, or pass its ID with an expression.
• Return All: switched on, n8n chains the API pages until the whole view has come back; switched off, Limit caps how many accounts the node returns.

Changes fields on an account that already exists. Nothing is mandatory beyond the identifier, so a workflow can touch a single field and leave the rest of the record alone.

• Account ID: ID of the account to update.
• Update Fields: a collection of 18 entries, including Name, Annual Revenue, Territory Name or ID and Parent Sales Account ID, which points at the parent account of the record.

Books an appointment in Freshworks CRM straight from a workflow. Three fields carry the meeting: a title and two timestamps.

• Title, Start Date and End Date: the title plus the timestamps that denote the start and the end of the appointment. On an all-day appointment they hold the start date and the end date.
• Additional Fields: 9 entries, including Is All-Day, Location, Time Zone, plus Target Type and Target ID, the record the appointment is created against.

Drops one appointment from Freshworks CRM. Useful when the cancellation happens somewhere else than the CRM, which is what usually goes wrong with meetings booked through an external page.

• Appointment ID: ID of the appointment to delete. It comes from the item that created the meeting, kept in a spreadsheet row or in a database alongside the booking reference.

Fetches one appointment by its identifier. Handy in the middle of a workflow, when a later step needs the details of the meeting rather than just its reference.

• Appointment ID: ID of the appointment to retrieve, the single field the operation requires.

Lists appointments, with two filters that make the result usable instead of overwhelming. No field is required, so the operation runs as soon as it is dropped in a workflow.

• Time: upcoming or past, the filter that decides which side of today you are reading.
• Include: pulls related data along with each appointment, either appointment_attendees, creater or targetable.
• Return All: on, every page is chained; off, Limit caps the number of appointments returned.

Edits an appointment already in the calendar, from its identifier. Everything else is optional, which is what makes rescheduling cheap to automate.

• Appointment ID: ID of the appointment to update.
• Update Fields: 13 entries, including Start Date, End Date, Location, Attendees and Outcome Name or ID, the outcome of the Appointment sales activity type.

Files a new person in Freshworks CRM. Three fields are required, and they are the three a lead form collects anyway.

• First Name, Last Name and Email Address: the identity of the contact, typically mapped from the form payload with {{ $json.field }}.
• Additional Fields: 24 optional entries, among them Job Title, Mobile Number, Lifecycle Stage Name or ID, Medium and Sales Account Names or IDs, the accounts the contact belongs to.

Erases a contact record from Freshworks CRM. The identifier is the only thing standing between the workflow and the deletion, so this one is worth guarding with an IF node upstream.

• Contact ID: ID of the contact to delete, read from a lookup or carried along by the item that started the run.

Looks up one contact and brings the record into the workflow. The step that turns an identifier into something a message or a report can actually use.

• Contact ID: ID of the contact to retrieve.

Returns contacts in bulk. Nothing is required here, and the view is optional, which makes this the operation to reach for when you want a whole segment rather than one person.

• View Name or ID: optional. Point at a saved list, or leave it empty to read more broadly.
• Return All: on, n8n chains the API pages to the end of the list; off, Limit sets the maximum number of contacts returned.

Rewrites fields on an existing contact. The widest update surface in the node, and the one that keeps a CRM honest between two manual reviews.

• Contact ID: ID of the contact to update, the only required field.
• Update Fields: 26 entries, including Contact Status Name or ID, Owner Name or ID, Subscription Status Name or ID, Job Title and Territory Name or ID.

Opens a deal in the pipeline. Two required fields, a name and an amount, and the opportunity exists where the forecast is read.

• Name and Amount: the label of the deal and its value, both required.
• Additional Fields: 14 entries, including Deal Pipeline Name or ID, Deal Stage Name or ID, Sales Account Name or ID, Currency Name or ID and Probability, a number between 0 and 100.

Takes a deal out of Freshworks CRM for good. Distinct from marking it lost, which is a stage change and belongs to the update operation.

• Deal ID: ID of the deal to delete.

Retrieves one deal from its identifier, so the rest of the workflow can branch on what the record actually says rather than on what the trigger assumed.

• Deal ID: ID of the deal to retrieve, the single required field.

Walks through a list of deals. This is the reporting workhorse of the node, and the one place where the pagination switch really matters.

• View Name or ID: optional. A saved view narrows the read to the deals you care about.
• Return All: on, every page of the API is chained until the list is complete; off, Limit fixes the maximum number of deals the node hands to the next step.

Moves a deal along, or corrects it. Stage, amount and owner all live in the same optional collection, so one node can handle several kinds of change.

• Deal ID: ID of the deal to update.
• Update Fields: 16 entries, including Amount, Deal Stage Name or ID, Probability and Deal Reason Name or ID, the reason for losing the deal, which can only be set on a deal in the Lost stage.

Attaches a written note to a record. All three fields are required, because a note without a target has nowhere to live.

• Content: the content of the note.
• Target Type: the kind of entity the note belongs to, Contact, Deal or SalesAccount.
• Target ID: the ID of that entity, of the type chosen just above.

Deletes a note from Freshworks CRM. Small operation, real use: automated notes pile up fast, and a workflow that writes them should usually know how to take them back.

• Note ID: ID of the note to delete, kept from the step that created it.

Corrects a note after the fact, or moves it to another record. Three optional fields, one required identifier.

• Note ID: ID of the note to update.
• Update Fields: 3 entries, Content, Target Type and Target ID, which together let a note be rewritten or re-attached to a different entity.

Reading one sales activity means naming it by its identifier, and the node hands that single record to the rest of the workflow.

• Sales Activity ID: the ID of the sales activity to retrieve. Type it in, or pull it from the item coming into the node with an expression, the n8n syntax that reads a value from the previous step, written {{ $json.field }}. Left empty, a required field stops the node before it calls Freshworks CRM.

The list side of the same resource. Rather than one identifier, the node brings back several sales activities in a single execution, each one as its own item for the following steps.

• Return All: switched on, n8n chains the pages of the API until every sales activity has come through.
• Limit: only read when Return All stays off, and it caps how many sales activities land in the workflow.

Search covers several kinds of Freshworks CRM records at once. You give a term, you tick the record types it applies to, and each match arrives as a separate item.

• Search Term: the term used for searching entities, often built from an incoming value with an expression such as {{ $json.field }}.
• Search on Entities: the types the search runs against, among contact, deal, sales_account and user. Several can be ticked together.
• Return All and Limit: every match, or a capped number of them.

Lookup starts from an exact value, not a loose term: pick the field it searches against, give the value, and matching records come back.

• Search Field: email, name, or customField, the last one being allowed only on custom fields of type Text field, Number, Dropdown or Radio button.
• Custom Field Name and Custom Field Value: the custom field targeted and the value looked for.
• Field Value: the value searched for on the selected field.
• Entities, in Options: related entities queried at once, among contact, deal and sales_account. The field has to exist in each, otherwise the API returns an error.

A task is created in Freshworks CRM and attached to the record it concerns, which is why five fields are required.

• Title: the title of the task.
• Due Date: the timestamp that says when the task is due to be completed.
• Owner Name or ID: the user the task is assigned to, chosen in the list or set with an expression.
• Target Type: Contact, Deal or SalesAccount.
• Target ID: the ID of that entity, whose type comes from Target Type.
• Additional Fields: Creator Name or ID, Outcome Name or ID, Task Type ID.

One identifier, and the task leaves the CRM. No other field takes part, so the whole question is where that identifier comes from.

• Task ID: the ID of the task to delete. Coming from a previous step, it reads as an expression like {{ $json.field }}, and a required field left empty blocks the execution.

Before touching a task, many workflows read it first. That single read is what this operation does: one identifier in, one task record out.

• Task ID: the ID of the task to retrieve, typed in the field or resolved from the incoming item.

Filtering is what makes this list genuinely useful rather than a wall of tasks. The node returns tasks as items, and the Filters collection narrows the set before it reaches the next step.

• Status, in Filters: completed, due_today, due_tomorrow, open or overdue.
• Include, in Filters: owner, targetable or users.
• Return All: on, n8n walks the pages until the last task; off, Limit caps the number of tasks returned.

Editing an existing task works on one identifier plus the fields you decide to touch. Everything you leave out of the Update Fields collection stays as it is in Freshworks CRM.

• Task ID: the ID of the task to update, the only required field.
• Update Fields: Title, Due Date, Owner Name or ID, Creator Name or ID, Outcome Name or ID, Task Type ID, Target Type and Target ID. Target Type sets the kind of entity, Target ID names it.