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

# Campaigns: Replace a campaign's AI workflows

> **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 [Campaigns](/docs/api/campaigns.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Replace a campaign's AI workflows

`PUT /v1/campaigns/{campaignId}/ai-workflows` - operationId `campaigns.replace-ai-workflows`

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

Sets the AI workflows the campaign runs and returns them. Send every workflow id the campaign should run in
`aiWorkflowIds`: ids you leave out are detached, and `[]` detaches all of them. To add one workflow,
read the current set first. No other campaign field changes.

Ids: 1 qualification, 2 personalization, 3 rewriting, 4 segmentation, 6 scoring, 8 line check. Rewriting runs
only when the campaign has rewriting prompts. Line check grades personalization lines before they are saved and
holds a contact whose lines fail. A campaign gets it with personalization by default, and this call does not add
it: keep 8 in the list to keep it on.

While the campaign is scheduled, launching or sending, 1, 2 and 4 must stay as they are and 3 can only be added,
because they decide which contacts may send. Pause the campaign first to change them. 6 and 8 can change at any
time.

Errors:

- `400 validation_failed`: `aiWorkflowIds` is missing or holds an unknown id.
- `404 not_found`: the campaign does not exist in this workspace.
- `409 invalid_state`: the change touches 1, 2, 3 or 4 in a way that is not allowed while the campaign is
scheduled, launching or sending.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/campaigns/PUT/v1/campaigns/%7BcampaignId%7D/ai-workflows)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | path | integer (int64) | yes | Id of the campaign. |
| `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 |
| --- | --- | --- | --- |
| `aiWorkflowIds` | array of integer (int64) | yes | Every workflow id to attach: 1 qualification, 2 personalization, 3 rewriting, 4 segmentation, 6 scoring or 8 line check. Required. `[]` detaches every workflow. |

### Response 200

`data` is a list of `CampaignAiWorkflow`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | Workflow id: 1 qualification, 2 personalization, 3 rewriting, 4 segmentation, 6 scoring or 8 line check. |
| `flow` | string | Workflow name: `qualification`, `personalization`, `rewriting`, `segmentation`, `scoring` or `line_check`. |

### Request

```bash
curl -X PUT "https://api.ken.so/v1/campaigns/812/ai-workflows" \
  -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 '{
  "aiWorkflowIds": [
    1,
    2,
    6
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": [
    {
      "id": 2,
      "flow": "personalization"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```
