<!-- BusyBot node reference — https://busybot.net/tools/convertkit-trigger/ -->

> Node: ConvertKit Trigger (`convertkit_trigger`) · Webhook trigger · v1
> Category: Marketing · Credentials: ConvertKit API (`convertKitApi`)
> Updated: 2026-08-16

# ConvertKit Trigger

> Start workflow from ConvertKit events

## Overview

Starts a workflow when ConvertKit sends a webhook notification for subscriber events such as form subscriptions, tag changes, link clicks, sequence completions, product purchases, and subscriber state changes. Receives POST requests from ConvertKit's automation hooks and normalizes the payload for downstream processing.

**Category:** Marketing  
**Tool Name:** `convertkit_trigger`  
**Version:** 1

**Appearance:** Icon: `lucide-Mail` | Color: `#FB6970`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

This tool requires **ConvertKit API** credentials.
See the [Credentials Guide](https://busybot.net/credentials/convert-kit-api/) for setup instructions.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Event | `options` | Yes | — | The ConvertKit event that triggers the workflow. |
| | | | | Options: `formSubscribe`, `linkClick`, `productPurchase`, `purchaseCreate`, `courseComplete` (Sequence Complete), `courseSubscribe` (Sequence Subscribe), `subscriberActivate`, `subscriberUnsubscribe`, `tagAdd`, `tagRemove` |
| Form ID | `string` | Yes | — | The ID of the form to monitor for subscriptions. _(shown when Event is `formSubscribe`)_ |
| Sequence ID | `string` | Yes | — | The ID of the sequence (course) to monitor. _(shown when Event is `courseSubscribe`, `courseComplete`)_ |
| Initiating Link | `string` | Yes | — | The URL of the link to monitor for clicks. _(shown when Event is `linkClick`)_ |
| Product ID | `string` | Yes | — | The ID of the product to monitor for purchases. _(shown when Event is `productPurchase`)_ |
| Tag ID | `string` | Yes | — | The ID of the tag to monitor for additions or removals. _(shown when Event is `tagAdd`, `tagRemove`)_ |

The `Purchase Created`, `Subscriber Activated`, and `Subscriber Unsubscribe` events need no extra parameter — selecting the event is enough.

## Output Data

Each delivery from ConvertKit produces one output item. The webhook payload is copied onto the item unchanged, and three fields are added:

- `_trigger` — always `convertkit_webhook`
- `_timestamp` — ISO 8601 timestamp of when the request arrived
- `_webhookEvent` — the event name reported by ConvertKit, taken from the payload's `event` field

Subscriber events carry a `subscriber` object with `id`, `first_name`, `email_address`, `state`, `created_at`, and a `fields` object holding the subscriber's custom fields.

Reference the payload downstream by expression, e.g. `{{ $json.subscriber.email_address }}`.

## Usage Examples

- trigger workflow when someone subscribes to a ConvertKit form
- start workflow when a subscriber clicks a link
- run automation when a ConvertKit tag is added to a subscriber
- process ConvertKit purchase events in real time
- react when a subscriber completes a ConvertKit sequence

## Example Configuration

Fire when someone subscribes through a specific form:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Form Subscribe",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "formSubscribe",
    "formId": "123456"
  }
}
```

Fire when a subscriber finishes a sequence:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Course Complete",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "courseComplete",
    "courseId": "789012"
  }
}
```

Fire when a subscriber clicks a tracked link:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Link Click",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "linkClick",
    "link": "https://example.com/special-offer"
  }
}
```

Fire when a specific product is purchased:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Product Purchase",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "productPurchase",
    "productId": "345678"
  }
}
```

Fire when a tag is added to a subscriber:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Tag Add",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "tagAdd",
    "tagId": "901234"
  }
}
```

Fire on subscriber activation — no extra parameter needed:

```json
{
  "id": "convertkit-trigger",
  "name": "ConvertKit Subscriber Activate",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "subscriberActivate"
  }
}
```

Track unsubscribes for list management:

```json
{
  "id": "subscriber-unsubscribe-trigger",
  "name": "Subscriber Unsubscribed",
  "type": "convertkit_trigger",
  "parameters": {
    "event": "subscriberUnsubscribe"
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

Entry point that fires when ConvertKit sends an automation hook event. Configure which event to listen for (form subscribe, tag add/remove, link click, purchase, sequence complete/subscribe, subscriber activate/unsubscribe) and optionally filter by a specific form, tag, sequence, product, or link. Outputs the subscriber and event data for downstream processing.