> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/triggers/openapi.json](/docs/api/triggers/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Triggers: Create a trigger

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Triggers](/docs/api/triggers.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Create a trigger

`POST /v1/triggers` - operationId `triggers.create`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 4,800 requests a minute per API key |

Creates a trigger that watches one signal type for a campaign. The trigger starts as `active`.

`campaignId` and `signalType` are required. The campaign must be in trigger mode. To use a batch
campaign, send `switchCampaignToTrigger: true`, and Kenso switches the campaign to trigger mode in the same
step, so a failed create leaves the campaign as it was. The LinkedIn signal types,
`linkedin_post_engagement` and `linkedin_profile_view`, take a campaign that is not in trigger mode
and need the `linkedin_signals` feature. A `linkedin_post_engagement` trigger on pasted posts takes
posts no older than 30 days, and a workspace has at most 10 such posts active.

`parameters` is a JSON string with the keys `GET /v1/trigger-schemas` lists for the signal type.
Omitted fields take these defaults: `cooldownMinutes` 10080 (7 days), `maxAgeMinutes` 1440 (1 day),
`priority` 50 and `stopSourceSequence` true. `cooldownMinutes` is at least 1, and
`maxAgeMinutes` is from 1 to 10080. `tier` is deprecated and has no effect: every trigger is processed
at the same speed.

A campaign has at most one active `lead_uploaded` trigger and one active `webhook_lead_received`
trigger. Both types need email enrichment and email verification set up on the campaign, and Kenso creates a
staging campaign for them, returned as `stagingCampaignId`.

Errors:

- `400 validation_failed`: a field is missing or invalid, the parameters or audience filter do not fit
the signal type, the campaign has the wrong mode, or a `lead_uploaded` or `webhook_lead_received`
trigger already exists or lacks email enrichment and verification.
- `402 plan_required`: the workspace's plan does not include the feature the signal type reads:
`funding_signals` for `fundraising`, `job_post_search` for `open_roles`. `error.refusal`
carries the code `PLAN_FEATURE_NOT_AVAILABLE` and the feature.
- `404 not_found`: the campaign is not in the workspace.
- `409 conflict`: an active trigger of this type already exists for this campaign.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/POST/v1/triggers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `campaignId` | integer (int64) | yes | Required. The campaign the trigger adds contacts to. |
| `signalType` | string | yes | Required. The signal type to watch, such as `link_clicked`, `reply_received` or `job_change`. |
| `tier` | string | no | Deprecated: no effect, so leave it out. Every trigger is processed at the same speed whatever its tier. Still accepted: `minutes`, `hours` or `same_day`. Default `minutes`. |
| `parameters` | string | no | The signal type's parameters as a JSON string, with the keys `GET /v1/trigger-schemas` lists. Omitted: `{}`, which a signal type with required parameters refuses. |
| `audienceFilter` | string | no | The campaigns whose contacts to watch, as a JSON string `{"sourceCampaignIds":[1,2]}`. The list cannot be empty, and every campaign must be in the workspace. Omitted: every campaign in the workspace. A `job_change` trigger requires it. |
| `cooldownMinutes` | integer (int32) | no | Minutes before the trigger can fire again for the same contact, at least 1. Default 10080 (7 days). |
| `maxAgeMinutes` | integer (int32) | no | Minutes a firing may wait to be processed before Kenso drops it, from 1 to 10080. Default 1440 (1 day). |
| `priority` | integer (int32) | no | When several triggers fire for the same person at once, the highest priority wins. Default 50. |
| `stopSourceSequence` | boolean | no | True stops the contact's sequence in its current campaign when the trigger adds it. Default true. |
| `switchCampaignToTrigger` | boolean | no | True switches a batch campaign to trigger mode as part of the create, so a failed create leaves the campaign as it was. Default false. Ignored for the LinkedIn signal types. |

### Response 201

`data` is a `Trigger`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The trigger's id. |
| `campaignId` | integer (int64) | The campaign the trigger adds contacts to. |
| `stagingCampaignId` | integer (int64) | For a `lead_uploaded` or `webhook_lead_received` trigger, the staging campaign where new leads wait for email enrichment and verification before the trigger adds them. Null for the other signal types. |
| `signalType` | string | The signal type the trigger watches, such as `link_clicked`, `reply_received` or `fundraising`. |
| `tier` | string | Deprecated: no effect. Every trigger is processed at the same speed whatever its tier, and `maxAgeMinutes` bounds how long a firing may wait. Still returned and accepted: `minutes`, `hours` or `same_day`. |
| `parameters` | string | The signal type's parameters as a JSON string, such as `{"count":3,"windowMinutes":10}`. |
| `audienceFilter` | string | The campaigns whose contacts the trigger watches, as a JSON string such as `{"sourceCampaignIds":[1,2]}`. Null watches every campaign in the workspace. |
| `cooldownMinutes` | integer (int32) | How long, in minutes, the trigger waits before it fires again for the same contact. |
| `maxAgeMinutes` | integer (int32) | How long, in minutes, a firing may wait to be processed. An older firing is suppressed as `expired`. |
| `priority` | integer (int32) | When several triggers fire for the same person at once, only the highest priority one acts. The others are suppressed as `lost_arbitration`. |
| `stopSourceSequence` | boolean | True when Kenso stops the contact's sequence in its current campaign as the trigger adds it to this one. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `createdAt` | string (date-time) | When the trigger was created, in UTC. |
| `updatedAt` | string (date-time) | When the trigger last changed, in UTC. |
| `listeningIdleReason` | string | Why a `linkedin_post_engagement` trigger that lists topics or watched profiles finds nothing now. `no_opted_in_seat`: no LinkedIn account in the workspace has research reads turned on, and only such an account reads topics and watched profiles. Returned when you get or list triggers; left out when the trigger can be read, and for every other trigger. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/triggers" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "campaignId": 812,
  "signalType": "link_clicked",
  "tier": "minutes",
  "parameters": "string",
  "audienceFilter": "string",
  "cooldownMinutes": 1,
  "maxAgeMinutes": 1,
  "priority": 1,
  "stopSourceSequence": true,
  "switchCampaignToTrigger": true
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "campaignId": 812,
    "stagingCampaignId": 812,
    "signalType": "link_clicked",
    "tier": "minutes",
    "parameters": "{\"count\":3,\"windowMinutes\":10}",
    "audienceFilter": "{\"sourceCampaignIds\":[1,2]}",
    "cooldownMinutes": 1,
    "maxAgeMinutes": 1,
    "priority": 1,
    "stopSourceSequence": true,
    "status": "active",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z",
    "listeningIdleReason": "string"
  }
}
```
