Kit (ConvertKit)

undefined

Detail	Value
Category	Marketing
Base URL	https://api.convertkit.com/v4
Authentication	Bearer Token
Endpoints	5
Connector key	convertkit

Using Kit (ConvertKit) in a workflow

1. Go to Connections and click New Connection.
2. Pick Kit (ConvertKit) from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Subscribers
GET	Forms
GET	Sequences
GET	Tags
GET	Broadcasts

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Subscribers

Detail	Value
Operation ID	subscribers_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Kit (ConvertKit) connection from the Connection dropdown.
3. In the Operation dropdown, select subscribers_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kit (ConvertKit) API reference.

GET

Forms

Detail	Value
Operation ID	forms_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Kit (ConvertKit) connection from the Connection dropdown.
3. In the Operation dropdown, select forms_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kit (ConvertKit) API reference.

GET

Sequences

Detail	Value
Operation ID	sequences_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Kit (ConvertKit) connection from the Connection dropdown.
3. In the Operation dropdown, select sequences_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kit (ConvertKit) API reference.

GET

Tags

Detail	Value
Operation ID	tags_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Kit (ConvertKit) connection from the Connection dropdown.
3. In the Operation dropdown, select tags_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kit (ConvertKit) API reference.

GET

Broadcasts

Detail	Value
Operation ID	broadcasts_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Kit (ConvertKit) connection from the Connection dropdown.
3. In the Operation dropdown, select broadcasts_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Kit (ConvertKit) API reference.