ActiveCampaign n8n integrationAutomate ActiveCampaign with n8n.

Adds a company record in ActiveCampaign and returns it, so a contact can later be attached to a named organization rather than floating alone.

• Name: the account's name, required. Usually the company name coming from the previous node, for example {{ $json.company }}.
• Account URL: the account's website, stored in Additional Fields.
• Fields: adds custom fields, so values you defined yourself get set at creation time.

Removes an account from ActiveCampaign for good. The record disappears, so run it on a filtered branch rather than on an unchecked list of items.

• Account ID: the numeric ID of the account to delete, required. It is the ID, not the company name, so take it from an earlier lookup with an expression such as {{ $json.id }}.

Pulls one account and returns its stored data, which is how a workflow checks what ActiveCampaign currently holds before writing anything new.

• Account ID: the numeric ID of the account to get, required. Feed it from a previous node with {{ $json.account }} rather than typing it by hand.

Lists the accounts stored in ActiveCampaign, one item per company, which is the starting point for any report or bulk cleanup.

• Return All: on, n8n walks every page of accounts; off, Limit caps how many come back.
• Search: searches by name, in the Filters collection, to narrow the export to one part of the book.
• Simplify: returns a lighter response instead of the raw data.

Edits an account already in ActiveCampaign. Only the fields you fill are touched, so the rest of the record survives the run untouched.

• Account ID: the numeric ID of the account to update, required.
• Name and Account URL: the company name and website, in Update Fields.
• Fields: sets custom fields that were not predefined.

Links a contact to an account, creating the association that tells ActiveCampaign this person works at that company.

• Account ID: the numeric ID of the company, required.
• Contact ID: the numeric ID of the person, required. Both usually come from the two create steps that ran just before.
• Job Title: the job title of the contact at the account, in Additional Fields.

Breaks the tie between a person and a company without deleting either one. The contact stays in ActiveCampaign, the association does not.

• Account Contact ID: the numeric ID of the account contact to delete, required. Note that it identifies the link itself, not the contact and not the account.

Changes what an existing association says, so the link between a person and a company stays accurate as their role moves.

• Account Contact ID: the numeric ID of the association, required.
• Job Title: the job title of the contact at the account, in Update Fields. It is the field most teams end up maintaining here.

Registers an external service in ActiveCampaign, the object that later lets orders and e-commerce customers be attributed to the store they came from.

• Service and External Account ID: the name of the service and the ID of the account in it, both required.
• Account Name: the name used in the external service, often a company name, required.
• Logo URL and Link URL: the logo image and the page where the integration is managed on the third party site, both required.

Drops a connection from ActiveCampaign. The store stops being a recognized source for the records that referenced it, so check what depends on it first.

• Connection ID: the numeric ID of the connection to delete, required. Fetch it from a listing step rather than trusting a value noted weeks earlier.

Reads back a single connection and returns its data, which is the quickest way to confirm a store is still registered the way you set it up.

• Connection ID: the numeric ID of the connection to get, required.

Returns every external service registered on the account, one item per connection, which is how you see all the stores feeding ActiveCampaign in one pass.

• Return All: on, n8n pages through all the connections; off, Limit sets how many are returned.
• Simplify: returns a simplified response instead of the raw data, easier to map in the next node.

Rewrites the details of an existing connection, including the two status values that say whether the store is healthy and whether a sync is running.

• Connection ID: the numeric ID of the connection to update, required.
• Status: 0 for error, 1 for connected.
• Syncronisation Status: 0 when the sync is stopped, 1 when it is running.
• Service, External Account ID, Account Name, Logo URL, Link URL: the descriptive fields, in Update Fields.

Writes a new person into ActiveCampaign and returns the created contact, with the email as the one value the operation refuses to run without.

• Email: the email of the contact to create, required, typically {{ $json.email }} from the form or trigger.
• Update if Exists: on, an existing contact is updated instead of raising an error.
• First Name, Last Name, Phone, Custom Fields: the rest of the profile, in Additional Fields.

Erases a contact from ActiveCampaign. The person leaves the database entirely, which is a different outcome from unsubscribing them.

• Contact ID: the numeric ID of the contact to delete, required. An email address will not work here, so look the ID up first.

Fetches one contact and returns the stored profile, including the custom field values other operations will need further down the workflow.

• Contact ID: the numeric ID of the contact to get, required.

Exports contacts in bulk, with the widest filter set of the node: 17 optional fields narrow the list before a single item leaves ActiveCampaign.

• Return All: on, n8n follows every page of contacts; off, Limit caps the batch.
• List ID, Tag ID, Segment ID, Form ID: filter on where the contact came from or sits.
• Status: 1 active, 0 unconfirmed, 2 unsubscribed, 3 bounced.
• Created After, Updated After: date windows for incremental runs.

Changes the stored details of a contact that already exists. Blank fields keep their current value. That makes a partial update safe to run on a whole batch, even when only one column changed upstream.

• Contact ID: the numeric ID of the contact to update, required.
• Email, First Name, Last Name, Phone: the profile fields, in Update Fields.
• Custom Fields: sets values you defined yourself, such as a plan or a score.

Subscribes a contact to one list, which is what actually makes the person eligible for the campaigns sent to it.

• List ID: the numeric ID of the list, required.
• Contact ID: the numeric ID of the person, required. Both are IDs, so a list name typed as text will fail.

Takes a contact off a list without deleting the person. They stay in ActiveCampaign and keep every other subscription they have.

• List ID: the numeric ID of the list to leave, required.
• Contact ID: the numeric ID of the contact, required.

Attaches a tag to a contact, the lightest way to mark behavior in ActiveCampaign and the usual hook for segments and automations.

• Tag Name or ID: choose the tag from the list n8n loads from your account, or pass an ID with an expression.
• Contact ID: the numeric ID of the contact, required.

Detaches a tag that no longer describes the person. Without it, old tags pile up and segments slowly stop meaning anything.

• Contact Tag ID: the numeric ID of the contact tag to delete, required. It identifies the tag on that specific contact, not the tag itself, which stays available for everyone else.

Pushes a new opportunity into an ActiveCampaign pipeline and returns the deal ID that later steps reuse.

• Title: the label sales people read in the pipeline, often built from the company name carried by the previous node.
• Deal's Contact ID: the numeric ID of the contact, not an email address, typically {{ $json.id }} after a contact lookup.
• Deal Value: the amount in cents, so a 2 000 euro deal is written 200000.
• Currency: the 3-character ISO code picked from the list, eur or usd.

Attaches a written note to a deal that already exists, so the context of a call lives in the CRM instead of a private inbox.

• Deal ID: the numeric identifier of the deal the note is filed under.
• Deal Note: the text itself. An expression builds it from earlier data, for instance {{ $json.summary }} coming from a transcript step.

Removes a deal from the CRM for good. Nothing comes back apart from the confirmation, so anything worth keeping should be read and stored before this node runs.

• Deal ID: the numeric ID of the deal to delete. A deal title is not accepted, and fetching the ID first is the only way in when all you have is a name.

Reads one deal and hands back its stored fields. Useful when an earlier step only carries an identifier and the rest of the workflow needs the amount, the stage or the title.

• Deal ID: the numeric ID of the deal to read, most often {{ $json.id }} taken from the item that came in.

Lists deals from the account, one n8n item per deal, ready to be filtered, counted or written to a spreadsheet.

• Return All: switched on, n8n keeps requesting the next page until every deal has been collected. Switched off, it stops at Limit.
• Limit: the maximum number of deals a single run brings back, which is enough when only the freshest ones matter.
• Simplify: returns a trimmed version of each deal rather than the raw API response, so field mapping stays short.

Edits a deal already in the pipeline. Only what sits under Update Fields is sent, so anything left blank keeps its current value.

• Deal ID: which deal gets edited.
• Title, Deal Value, Currency: the same meaning as at creation, value still in cents.
• Deal Stage ID: moves the deal to another stage, which is how a pipeline advances without anyone dragging a card.
• Deal Status and Deal Percentage: numeric fields that record where the opportunity stands.

Rewrites the content of a note already filed on a deal. Two identifiers are needed, because a note only exists inside its deal.

• Deal ID: the deal that holds the note.
• Deal Note ID: the numeric ID of the note itself, usually kept from the step that created it.
• Deal Note: the new text. Leave it out and nothing changes.

Registers a shopper as an e-commerce customer inside ActiveCampaign and ties that record to a connection, which is what lets orders be attached to a buyer later on.

• Service ID: the ID of the connection object for the service the customer originates from.
• Customer ID: the identifier the shopper carries in that external service, not the one ActiveCampaign will assign.
• Customer Email: the address, in the name@email.com form.
• Accepts Marketing: records whether the shopper opted in to marketing communications.

Wipes an e-commerce customer record. The node returns no copy of what it removed, so a read step belongs before it whenever a trace has to be kept somewhere else.

• Customer ID: the numeric ActiveCampaign ID of the e-commerce customer to delete, which is not the ID the same buyer carries in the store.

Fetches a single e-commerce customer record so a workflow can check what ActiveCampaign already holds before deciding to write anything.

• Customer ID: the numeric ID of the e-commerce customer to read.

Walks through the e-commerce customers of the account and outputs them one by one, which is the starting point of any audit of the shopping side.

• Return All: on, every page of customers is collected before the workflow moves on. Off, the run stops at Limit.
• Limit: caps how many customer records a run returns, handy while a workflow is still being tested.
• Simplify: keeps a condensed version of each record instead of the full API payload.

Corrects an existing e-commerce customer record. Fields left out of Update Fields stay as they are, which makes this safe to run on every order.

• Customer ID: the record being edited.
• Customer Email: the new address, still in the name@email.com form.
• Service ID and Customer ID under Update Fields: the connection and the external identifier, to repoint a record that was attached to the wrong store.
• Accepts Marketing: flips the opt-in when a shopper changes preferences.

Records a full order in ActiveCampaign, buyer and basket included, so automations react to real purchases.

• Order Source: 0 stores the order quietly, 1 makes it trigger automations.
• Customer Email: the address of the buyer.
• Total Price: the total in cents, tax and shipping included, never negative, so $456.78 is sent as 45678.
• Order Currency, Connection ID, Customer ID, Creation Date: the currency code, the connection the order came from, the buyer and the date.
• External ID or External Checkout ID: the order or cart reference. One of the two is needed, and a cart reference also expects Abandoning Date.

Drops an order from the e-commerce data of the account. Handy after a test run, less so on live data, since the basket lines attached to that order go with it.

• Order ID: the ID of the e-commerce order, and the only field the operation offers.

Returns a single order with the data ActiveCampaign stored for it, which is how a workflow confirms that a push really landed.

• Order ID: the ID of the e-commerce order to read.

Pulls orders in bulk, one item per order, so revenue data leaves ActiveCampaign towards a sheet, a database or a report.

• Return All: enabled, the node chains the pages of the orders endpoint until it has them all. Disabled, it stops at Limit.
• Limit: how many orders a run brings back at most.
• Simplify: strips the raw payload down to the useful order fields, which shortens the mapping that follows.

Amends an order already stored, without resending the whole basket. Whatever stays out of Update Fields keeps its recorded value.

• Order ID: the order being edited.
• Total Price and Order Currency: the corrected total, still in cents, with its ISO code.
• Shipping Amount, Tax Amount, Discount Amount: the three amounts that explain the total, each in cents.
• Shipping Method and Order Number: the carrier choice and the store reference, which can differ from the external ID.
• Products: the ordered products, when a line has to be corrected too.

Collects the product lines recorded across orders, not the orders themselves. Each item is a bought line, which is the level at which best sellers can be counted.

• Return All: on, every page of product lines comes back, and the volume grows faster than with orders.
• Limit: the ceiling on the number of product lines a run returns.
• Simplify: hands back a lighter version of each line instead of the raw response.

Narrows the product lines down to one product, so a workflow follows a single reference instead of sorting through everything that has been sold.

• Product ID: the ID of the product you want returned.

Answers a simple question: what was in this order? The operation returns the lines attached to one order rather than a single product across orders.

• Order ID: the ID of the order whose products you want returned.

Brings back the lists of the account with their IDs, which are the values other operations expect when a contact has to be subscribed somewhere.

• Return All: on, the node collects every list; off, it stops at Limit, which is usually plenty since accounts rarely hold many lists.
• Limit: the maximum number of lists returned.
• Simplify: returns the condensed form of each list rather than the full API response.

Creating a tag gives the ActiveCampaign account a new label and returns it with the ID that every later tagging step expects.

• Type: contact for a tag you apply to people, template for a tag you apply to a template. The node asks for it before the name.
• Name: the label as it will read inside ActiveCampaign, often built from an upstream item with {{ $json.name }}.
• Description: optional, sitting under Additional Fields. Fill it when several people share the account and need to know what the label stands for.

Deletion is permanent here, and it takes the label off every contact that carried it. Run it on purpose, not as a cleanup reflex.

• Tag ID: a number, not the tag text. ActiveCampaign will not resolve a label you type by hand, so the value normally comes from a Get many tags step as {{ $json.id }}.

One tag, read by its identifier, returned as ActiveCampaign stores it. This is the read step you put in front of a branch, when the workflow has an ID and needs the record behind it.

• Tag ID: the numeric identifier of the tag to read, usually carried over from an earlier node or from the trigger payload.

Listing brings the account's tags into the workflow, one item per tag, which is how you turn a naming convention into something you can actually check.

• Return All: on, n8n walks the API pages until every tag is in. Off, it stops at Limit.
• Limit: the maximum number of tags returned, useful while you are still testing the workflow.
• Simplify: returns a trimmed version of each tag instead of the raw API payload, which keeps the mapping panel readable.

A badly named label gets fixed here, without touching the contacts attached to it. Only the fields you fill are sent, everything else stays as it was.

• Tag ID: the tag to modify, by number.
• Tag: inside Update Fields, the text the label carries after the update. Its n8n hint still reads "Name of the contact", a leftover from the contact resource, so trust the field name over the hint.
• Description: inside Update Fields, the explanation shown next to the tag.