ConvertKit n8n integrationAutomate ConvertKit with n8n.

Custom fields hold the data ConvertKit does not keep by default, such as a plan name or an acquisition source. This operation creates one in the account so that subscriber operations have somewhere to write.

• Label: the label of the custom field, the wording you will see in ConvertKit and in the Add Custom Field picker of the subscriber operations.

Fields pile up faster than anyone expects, and a field nobody fills makes the account harder to read. This operation removes one field from ConvertKit.

• Field ID: the ID of your custom field, not its label. Get many custom fields is the operation that hands you that identifier when you only know the wording.

Lists the custom fields defined in the account, each with its label and its identifier. It is the operation that turns a field name you know into the ID that the update and delete operations expect.

• Return All: on, n8n walks the API pages and brings back every field in the account; off, Limit caps how many fields come back.

Changes the label of a field that already exists in ConvertKit. Handy when the wording chosen in a hurry stops matching what the field actually contains.

• Field ID: the ID of your custom field, the field being renamed.
• Label: the new label of the custom field, which is what appears in ConvertKit afterwards.

Puts an email address into a ConvertKit form, which is how somebody joins the list from outside ConvertKit. The form you choose decides what happens next on the ConvertKit side.

• Form Name or ID: the target form, picked from the list n8n loads or supplied as an ID through an expression.
• Email: the subscriber's email address, in the shape name@email.com.
• First Name and Custom Fields, in Additional Fields: key and value pairs that travel with the subscriber. The custom field has to exist before you can use it here.

Returns the forms that exist in the account. Useful when a workflow has to choose a form by name at runtime rather than having one hard-wired into the node.

• Return All: on for a full inventory of the account's forms; off, Limit sets the maximum number of forms returned.

Lists the subscriptions to one form, including the subscriber data attached to each of them. This is the acquisition view: who came in through this particular form.

• Form Name or ID: the form whose subscriptions you want to read.
• Subscriber State, in Additional Fields: active or cancelled, to separate the people still on the list from those who left.
• Return All: on for the whole history of the form; off, Limit stops the run earlier.

Drops someone straight into a sequence, so the emails start arriving in the order you set up in ConvertKit. Unlike the form route, this targets the automated series itself.

• Sequence Name or ID: the sequence to enroll the person into.
• Email: the subscriber's email address, in the shape name@email.com.
• Tag Names or IDs, First Name and Custom Fields, in Additional Fields: tags and values applied at the same time, which saves a second operation later.

Reads back the sequences configured in the account, with the identifier of each one. It is the check you run before a workflow tries to enrol anybody, so a renamed sequence does not break the rest.

• Return All: on to list every sequence; off, Limit decides how many come back.

Returns everyone subscribed to a given sequence, subscriber data included. Where the form version answers how people arrived, this one answers who is currently going through the series.

• Sequence Name or ID: the sequence being read.
• Subscriber State, in Additional Fields: keep active for people still in the flow, or cancelled to study the drop-offs.
• Return All: on to page through the entire sequence; off, Limit caps the result.

Adds a tag to the ConvertKit account so that subscribers can carry it afterwards. Creating the tag and applying it are two separate steps here.

• Name: the tag name. Several tags can be created in one go by separating the names with a comma.

Brings back the tags that exist in the account. Most teams reach for it to avoid a near-duplicate, since ConvertKit accounts tend to accumulate three spellings of the same idea.

• Return All: on to pull the complete tag list; off, Limit fixes the maximum number returned.

Applies an existing tag to one person, identified by their email address. This is the segmentation workhorse: most ConvertKit logic downstream keys off tags.

• Tag Name or ID: the tag being applied, from the loaded list or through an expression.
• Email: the subscriber email address, in the shape name@email.com.
• First Name and Custom Fields, in Additional Fields: values written on the subscriber at the same time, with the custom field created beforehand.

Every subscriber carrying one given tag comes back here, subscriber data included. In practice this is how a segment becomes a concrete list of people you can act on outside ConvertKit.

• Tag Name or ID: the tag whose subscribers you want.
• Subscriber State, in Additional Fields: active or cancelled, depending on whether the segment is for sending or for analysis.
• Return All: on for the full segment; off, Limit trims it.

Takes a tag off one subscriber without touching the tag itself, which stays available for everybody else in the account.

• Tag Name or ID: the tag to remove from this person.
• Email: the subscriber email address, in the shape name@email.com.