> 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: Update 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).

## Update a trigger

`PATCH /v1/triggers/{triggerId}` - operationId `triggers.update`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 12,000 requests a minute per API key |

Changes the fields you send. Omitted fields keep their values.

The body can hold `status` (`active` or `paused`), `parameters` (a JSON string),
`audienceFilter` (a JSON string, or null to clear the filter), `cooldownMinutes`,
`maxAgeMinutes`, `priority` and `stopSourceSequence`. Their rules are the same as on create.
`tier` (`minutes`, `hours` or `same_day`) is still accepted but deprecated: it has no
effect. `signalType` and `campaignId` cannot change. To archive a trigger, use
`DELETE /v1/triggers/{triggerId}`.

Errors:

- `400 validation_failed`: a field has the wrong type or value, the body changes `signalType` or
`campaignId`, `status` is `archived`, or the trigger is archived.
- `402 plan_required`: the body sends `parameters`, or sets `status` to `active` on a trigger
that is not active, and the workspace's plan does not include the feature the signal type reads (as on create).
Pausing and other edits are not refused.
- `404 not_found`: the workspace has no trigger with this id.
- `409 conflict`: an active trigger of this type already exists for the campaign.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/PATCH/v1/triggers/%7BtriggerId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `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: `object`.

The fields to change.

### Response 200

`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 PATCH "https://api.ken.so/v1/triggers/812" \
  -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 '{}'
```

### 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"
  }
}
```
