---
title: "Attach a playbook to the sequence"
method: PUT
path: "/v3/sequences/ai-sdr/{sequence_id}/playbook"
tags: ["AI SDR Sequences"]
---

# Attach a playbook to the sequence

`PUT /v3/sequences/ai-sdr/{sequence_id}/playbook`

<Warning>
  **Coming soon.** This endpoint will be available by early July 2026.
</Warning>

<small>_Requires the `ai-sdr:operate` scope (or a broader one that includes it)._</small>

Attaches a playbook to the sequence by composite id. Replaces any previously-attached playbook.

Requires the AI SDR feature on the caller's team.

## Path parameters

- `sequence_id` integer, required

## Request body

- object — Attaches a playbook to the sequence by composite id. Replaces any previously-attached playbook.
  - `playbookId` string, required — Composite playbook id (`{prefix}-{numericId}`) where the prefix encodes the playbook scope: `g` for global, `o` for organization, `t` for team (e.g. `g-1`, `o-42`, `t-7`).

## Response `204`

Playbook attached

## Other responses

- `400` — Validation failure, invalid playbook id format, referenced playbook not found, or sequence is not an AI SDR sequence.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — AI SDR feature is not available for the caller's team, or the caller does not have access to this sequence.
- `404` — Sequence not found.
- `502` — Upstream AI SDR service failure.

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/versions/1c3d32eaf95e/schema)