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

# Sequence import: Preview a sequence from another tool

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

## Preview a sequence from another tool

`POST /v1/sequence-imports/previews` - operationId `sequence-imports.preview`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 240 requests a minute per API key |

Reads `text` (required, 1 to 50,000 characters) into proposed Kenso steps, in send order. Example:
`{ "text": "Step 1 - LinkedIn connection request\n\nStep 2 - Email - 1 day later\nSubject: quick question\nHey {{firstName}}, ...", "source": "origami" }`.
`source` is optional: `origami`, `lemlist`, `instantly`, `la_growth_machine` or
`other`.

How the text is read (`parser`): JSON (lemlist's sequences response, an Instantly campaign, or any array of
step objects with a type or channel, a delay or wait, a subject and a body or message) and CSV with a header row
that names those columns are read in code (`structured`). Anything else is free text, read by one model call
(`ai`) that returns only the steps' structure and the lines that hold each subject and body; the copy is cut
from your text, so it comes back exactly as written. Only placeholders change: `{{firstName}}`,
`{{first_name}}` and the like become Kenso's variables for the step's channel (`{company}` on email,
`{companyName}` on LinkedIn).

Each step has `channel`, `stepType`, `waitDays` (days after the previous step, 0 to 30),
`condition` (`none`, `accepted` or `not_accepted`), `waitFromCondition` ("1 day after
connecting" is `accepted` with `waitFromCondition` and `waitDays` 1), `subject` and
`body`. "If no reply" needs no condition: Kenso stops every channel when the lead replies. A follow-up email
that replies in the same thread has no subject.

`warnings` say what changed, each with a `code`, a `message` and the `stepIndex` it is about
(null for a dropped step): steps Kenso cannot run (calls, manual tasks, SMS, WhatsApp) are dropped
(`unsupported_step`) and their wait moves to the next step; an InMail becomes a `message`
(`in_mail`); "if not accepted after N days" names N (`not_accepted_days`), which in Kenso is the
campaign's `notAcceptedAfterDays` LinkedIn setting; a placeholder with no Kenso variable stays as written
(`unknown_variable`). Waits round up to whole days and clamp to 0-30, and steps past 30 are dropped.

JSON and CSV cost nothing. Free text counts on the workspace's `sequenceImportPreviews` quota (30 an hour,
200 a day; past it, `429 quota_exceeded` with `Retry-After`).

Errors:

- `400 validation_failed`: `text` is blank or over 50,000 characters, or `source` is not one of
the values above.
- `422 no_steps_found`: the text holds no step Kenso can run.
- `429 quota_exceeded`: the free-text quota is used up.
- `503 provider_unavailable`: the model that reads free text failed; try again, or paste CSV.

Requires Campaigns edit.

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

### 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.

The sequence and the tool it comes from.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `text` | string | yes | The sequence as pasted or uploaded: free text, CSV with a header row, or the tool's JSON export or API response. Required, 1 to 50,000 characters. |
| `source` | string | no | The tool it comes from: `origami`, `lemlist`, `instantly`, `la_growth_machine` or `other`. Optional; it only helps read free text. |

### Response 200

`data` is a `SequenceImportPreview`.

| Field | Type | Description |
| --- | --- | --- |
| `steps` | array of SequenceImportStep | The proposed steps, in send order, at most 30. |
| `warnings` | array of SequenceImportWarning | What Kenso changed, dropped or could not map, to show next to the steps. |
| `parser` | string | How the text was read: `structured` (JSON or CSV, read in code) or `ai` (free text, read by a model that returned only structure; the copy is cut from the text). |

### Request

```bash
curl -X POST "https://api.ken.so/v1/sequence-imports/previews" \
  -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 '{
  "text": "string",
  "source": "origami"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "steps": [
      {
        "channel": "email",
        "stepType": "connection_request",
        "waitDays": 1,
        "condition": "string",
        "waitFromCondition": true,
        "subject": "string",
        "body": "string"
      }
    ],
    "warnings": [
      {
        "code": "unsupported_step",
        "message": "string",
        "stepIndex": 1
      }
    ],
    "parser": "string"
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### SequenceImportStep

One proposed step.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `channel` | string | no | `email` or `linkedin`. |
| `stepType` | string | no | `email`, or a LinkedIn step: `connection_request`, `message`, `profile_visit`, `follow`, `like_post`, `endorse_skill`, `comment_post` or `voice_note`. |
| `waitDays` | integer (int32) | no | Days after the previous step, 0 to 30. With waitFromCondition, days after the condition came true. |
| `condition` | string | no | `none`, `accepted` (runs once the lead accepted the connection request) or `not_accepted` (runs if the lead did not accept within the campaign's `notAcceptedAfterDays`). Only on a LinkedIn step after a `connection_request`. |
| `waitFromCondition` | boolean | no | True when waitDays count from the condition ("1 day after connecting"). |
| `subject` | string | no | The email's subject, or a message's InMail subject, as written in the source. Null for a follow-up email that replies in the previous thread and for steps without one. |
| `body` | string | no | The step's text as written in the source, with only its placeholders rewritten to Kenso variables for the channel: the email or message, the connection note, the voice note's text or the comment guidance. Null when the step has none. |

### SequenceImportWarning

Something the reader changed, dropped or could not map.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | Stable code: `unsupported_step`, `in_mail`, `not_accepted_days`, `unknown_variable`, `wait_clamped`, `wait_rounded`, `condition_dropped`, `too_many_steps`, `variants_dropped`, `body_dropped`, `missing_body`, `missing_subject`, `body_too_long`, `unsupported_syntax` or `copy_not_found`. Clients tolerate new codes. |
| `message` | string | no | What happened, for people. |
| `stepIndex` | integer (int32) | no | The 0-based index in `steps` of the step it is about; null for a step that was dropped. |
