HighLevel n8n integrationAutomate HighLevel with n8n.

One call handles both cases: if the person is already in HighLevel, the record is updated instead of duplicated.

• Email: the address that identifies the person (name@email.com). Email or Phone is required to create the contact.
• Phone: same role, in phone form. It has to start with a valid country code led by a plus sign, as in +491234567890.
• Additional Fields: 14 optional fields, among them First Name, Last Name, Source, Tags as a comma separated list, and Custom Fields.

Removes the record from HighLevel. The node wants the identifier, not the name and not the email address.

• Contact ID: the HighLevel identifier of the record to remove. It usually arrives from an earlier node, picked up with an expression such as {{ $json.field }}, which reads a field of the incoming item.

Reads a single contact and hands its data to the next node, which saves a manual lookup in the HighLevel interface.

• Contact ID: the record to read. Chain it after a list operation when all you have is a name or an email address.

Returns a list of contacts, with filters that narrow it before the data reaches the rest of the workflow.

• Return All: on, n8n chains the API pages until every matching contact is in. Off, Limit sets the maximum number of contacts returned.
• Query: free text search, run on Name, Phone, Email, Tags and Company Name.
• Sort By and Order: sort on date_added or date_updated, ascending (asc) or descending (desc).

Changes only the fields you list on an existing record and leaves the rest as it was.

• Contact ID: which record gets rewritten.
• Update Fields: 14 fields to pick from, among them Email, Phone, Tags, Timezone and Do Not Disturb, where true means no outbound message is permitted.

Opens a deal attached to a contact, with its name, its status and its place in a pipeline.

• Contact Email or ID: pick from the list or pass an ID with an expression. The node points out that there can only be one opportunity for each contact.
• Status: one of open, won, lost or abandoned.
• Pipeline Name or ID: chosen from the list, or given as an ID.
• Monetary Value: the monetary value of the lead opportunity, inside Additional Fields next to Tags and Assigned To.

Erases a deal. This is the operation you reach for when records created while testing a workflow have to disappear before anyone reads the numbers.

• Opportunity ID: the deal to remove, most often carried over from the node that created or listed it.

Pulls one deal and its data, so a later node can branch on what came back instead of assuming.

• Opportunity ID: the deal to read.

Lists deals with 8 filters, which is what you want when a report has to be built without touching the interface.

• Return All: on, every matching deal comes back page after page; off, Limit caps how many are returned.
• Pipeline Name or ID and Stage Name or ID: narrow to one pipeline, then to one stage. The node asks for the pipeline first, otherwise the stages do not show up.
• Start Date and End Date: a date range on the deals.
• Status: open, won, lost or abandoned.

Moves a deal along: another stage, another status, another value, or a different owner.

• Opportunity ID: the deal to change. The node warns that an opportunity's pipeline ID cannot be updated.
• Update Fields: 6 fields, among them Status, Stage Name or ID, Monetary Value, Assigned To and Name.

Attaches a to-do to a contact, with a deadline. Four fields are required here, more than on most operations of this node.

• Contact Email or ID: the contact the task belongs to, from the list or as an ID.
• Title: what has to be done.
• Due Date: the deadline, as a date and time.
• Completed: a required boolean, so n8n asks for its value even on a task that has just been opened.
• Body: the detail, inside Additional Fields next to Assigned To.

Clears a task that has lost its reason to exist. Two identifiers are needed, because tasks hang off a contact.

• Contact Email or ID: the contact the task belongs to.
• Task ID: which task on that contact goes away.

Fetches one task from a contact and passes what it finds down the workflow.

• Contact Email or ID: the contact holding the task.
• Task ID: the task to read.

The tasks of one contact come back as a list. The contact is required here, so the result is always scoped to a single person.

• Contact Email or ID: required, the contact whose tasks are returned.
• Return All: on, every task of that contact comes back; off, Limit sets how many.

Rewrites a task in place: a new deadline, a new owner, or the flag that closes it.

• Contact Email or ID and Task ID: the pair that points at the task.
• Update Fields: 5 fields, Completed, Title, Body, Due Date and Assigned To.

Books a slot in a HighLevel calendar for a contact, without anyone opening a booking page.

• Calendar ID: which calendar receives the appointment.
• Location ID: the location identifier the node asks for alongside it.
• Contact ID: who the appointment is for.
• Start Time: a string carrying the date, the time and the offset, in the shape 2021-06-23T03:30:00+05:30. End Time follows the same shape inside Additional Fields.
• Appointment Status: optional, with allowed values new, confirmed, cancelled, showed, noshow and invalid.

Asks a calendar which slots are still open across a window you define, which is the step that comes before offering times to anyone.

• Calendar ID: the calendar to inspect.
• Start Date and End Date: the bounds of the window, as numbers. The node gives 1548898600000 and 1601490599999 as examples.
• Timezone: the timezone used for the returned slots, America/Chihuahua for instance, inside Additional Fields next to User ID.