Keap n8n integrationAutomate Keap with n8n.

Adds a company record to Keap, the object you attach contacts and orders to when you sell to organizations rather than individuals.

• Company Name: the only required field, typically {{ $json.company }} coming off a form submission.
• Addresses, Phones and Faxes: separate collections, each one added line by line rather than typed into a single box.
• Additional Fields: holds Email, Website, Notes and Opt In Reason, plus the address details such as Country Code in ISO Alpha-3 form.

Pulls the company list out of Keap, either whole or filtered, and returns one item per company for the next node to work through.

• Return All: on, n8n keeps requesting pages until the API has none left; off, it stops at Limit.
• Company Name: narrows the query to companies matching that name.
• Order and Order Direction: sort by datecreated, id or name, ascending or descending.
• Fields: a comma-separated list of properties to add back to the response, since notes, fax number and custom fields are left out by default.

One call that creates the contact, or updates the record already sitting in Keap. This is the workhorse of most Keap workflows, because it removes the duplicate problem instead of managing it.

• Duplicate Option: required. Email matches on the address alone, Email And Name needs both to line up before Keap treats it as the same person.
• Emails, Phones, Addresses and Social Accounts: collections, each entry typed by Field or Type.
• Additional Fields: 17 of them, including Given Name, Family Name, Job Title, Owner Name or ID, Company ID and Source Type.

Removes a contact from Keap. There is no confirmation step inside the node, so whatever reaches it gets deleted.

• Contact ID: required, the Keap identifier and not the email address. It usually comes from a preceding lookup as {{ $json.id }}.

Fetches a single contact by identifier and returns its properties as one item, ready to be read by expressions further down.

• Contact ID: required, the numeric Keap ID of the person.
• Fields: a comma-separated list of properties to include, because lead source ID, custom fields and job title are not returned by default.

Reads your contact base, page after page, with filters that make the result usable instead of enormous.

• Return All: on for a full export, off to cap the result at Limit.
• Since and Until: a date window applied to the last update, which is how you get an incremental sync rather than a full reload.
• Email, Given Name, Family Name: filters to find a specific person.
• Order and Order Direction: sort by date, email, id or name.

Writes a note on a contact's history, the trace a salesperson reads before picking up the phone.

• Contact ID: who the note belongs to.
• User Name or ID: the Infusionsoft user the note is created on behalf of, chosen from the list or set by expression.
• Additional Fields: Title, Body, and Type among appointment, call, email, fax, letter and other.

Takes a note off the record permanently. Nothing else on the contact is affected.

• Note ID: required, the identifier of the note itself, which is not the contact ID. Fetch it with contactNote.getAll if you only know who the note belongs to.

Returns one note with its content, so a workflow can read what was written before deciding what to do next.

• Note ID: required, and the only input this operation takes.

Lists notes across contacts, or narrows down to one person's history when you give it a filter.

• Return All: on to walk every page, off to stop at Limit.
• Contact ID: keeps only the notes attached to that contact.
• User Name or ID: keeps only the notes created on behalf of that user.

Edits a note that already exists rather than adding a second one next to it. Only the fields you fill in are changed.

• Note ID: required, the note to rewrite.
• Additional Fields: Title, Body, Type, Contact ID to move the note to another person, and User Name or ID.

Applies one or several tags to a contact in a single call. Tags drive segmentation in Keap, so this is often the last step of a capture workflow.

• Contact ID: required, the person being tagged.
• Tag Names or IDs: required, a multi-select that lets you apply several tags at once, or an expression when the IDs are computed upstream.

Removes a tag from a contact without touching the contact itself or the tag definition.

• Contact ID: required.
• Tag IDs: required, and here it is a plain text field rather than the picker used when adding tags.

Answers a question every routing workflow ends up asking: what is this contact tagged with right now?

• Contact ID: required, since tags are always read per contact.
• Return All: on to get the full set, off to stop at Limit.

Records an order in Keap, with its lines and its delivery address, so revenue and lifecycle live next to each other.

• Contact ID, Order Date, Order Title and Order Type: all required, with the type either online or offline.
• Order Items: a collection where each line carries Product ID, Quantity, Description and an optional Price that overrides the catalog price.
• Shipping Address and Promo Codes, the latter comma-separated so the matching discount is applied.

Retrieves one order and its detail, which is what you call when a webhook gives you an order reference and nothing else.

• Order ID: required, and the only field to fill.

Erases an order from Keap. Worth treating as a last resort, since the order also carries your revenue history.

• Order ID: required, the identifier of the order to remove.

Sweeps through orders with the filters that matter for follow-up: a date window, payment status, one customer or one product.

• Return All: on to page through everything, off to cap at Limit.
• Since and Until: the period to search in.
• Paid: a boolean that separates settled orders from the rest.
• Contact ID and Product ID: narrow to one customer or one item.

Registers a product in the Keap catalog so orders can reference it by ID afterwards.

• Product Name: the only required field.
• Additional Fields: SKU, Product Price, Product Description and Product Short Desc, plus two booleans, Active for visibility and Subscription Only for items sold on a recurring basis.

Takes a product out of the Keap catalog for good.

• Product ID: required, the catalog identifier rather than the SKU you use in the shop.

Looks up a single product and returns its catalog record, price and description included.

• Product ID: required, the Keap identifier of the item.

Walks the catalog and hands back the products as items, which is how you turn Keap into the reference list for the rest of a workflow.

• Return All: on to retrieve the whole catalog, off to stop at Limit.
• Active: a boolean filter to keep only the products still on sale.

This operation logs an email inside Keap without sending anything. The message left from somewhere else, and the record keeps the contact history complete.

• Sent To Address: the recipient address, required, often {{ $json.email }} coming from the node before it.
• Sent From Address: the address the message was sent from, also required.
• Contact ID: in Additional Fields, the numeric Keap contact the entry attaches to.
• Original Provider: in Additional Fields, one of UNKNOWN, INFUSIONSOFT, MICROSOFT or GOOGLE, paired with Original Provider ID, which Keap autogenerates as a UUID without dashes when left empty.

Reads sent email records back out of Keap and returns one item per message, ready for a report or a follow-up branch.

• Return All: on, n8n walks every page of the Keap API; off, Limit caps how many emails come back.
• Contact ID: in Filters, narrows the result to the emails of one contact.
• Email: in Filters, an address such as name@email.com when the contact identifier is unknown.
• Since Sent Date and Until Sent Date: the date window; Since Sent Date has to be filled whenever the until date is set.

Keap sends the message itself here, on behalf of one of its users, and the send stays attached to that identity.

• User Name or ID: required, the Infusionsoft user the email goes out for; pick it from the list or set an ID through an expression.
• Contact IDs: the recipients, several of them separated by commas.
• Subject: the subject line, alongside HTML Content or Plain Content in Additional Fields, both encoded in Base64.
• Attachments: up to 10 files per copy, 1MB each, filled with File Name and File Data or read from a binary Property.

One file leaves the Keap library for good. The node takes its identifier and returns the outcome, nothing else.

• File ID: required, the identifier of the file to remove, usually {{ $json.id }} passed down from a listing step earlier in the workflow.

Browsing the Keap file library from a workflow starts here. Each file comes back as its own item, filters included.

• Return All: enabled, every page of files is fetched; disabled, Limit decides where the listing stops.
• Name: in Filters, a name search where * before or after the text runs a LIKE query.
• Type: in Filters, the file category, from attachment and image to webform or digitalProduct.
• Permission and Viewable: user, company or both on one side, public, private or both on the other.

A document produced upstream, a signed quote or an invoice PDF, gets stored in Keap and tied to a record.

• Input Binary Field: required, the name of the incoming binary field holding the file; Binary File tells the node to read the data from there.
• File Association: required, company, contact or user, and Contact ID names the record it lands on.
• File Name: required, extension included, since Keap keeps the name as given.
• File Data: required, the content encoded in Base64, with Is Public controlling visibility.