instantiate_playbook
Run a playbook: create one content plan per playbook item, in order, as a batch.
Input Schema
{
"type": "object",
"required": [
"playbook_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "Scope the created plans to this project UUID."
},
"anchor_date": {
"type": "string",
"description": "ISO date YYYY-MM-DD. Each item's offset_days is added to it to compute that plan's due date."
},
"assigned_to": {
"type": "integer",
"description": "Assign the created plans to this team member."
},
"category_id": {
"type": "integer",
"description": "Apply this content category to the created plans."
},
"playbook_id": {
"type": "integer",
"description": "ID of the playbook to instantiate."
}
}
}Output Schema
{
"type": "object",
"properties": {
"run": {
"type": "object",
"properties": {
"id": {
"type": "integer"
},
"name": {
"type": "string",
"description": "Auto-named \"<playbook> — <Mon YYYY>\" unless you passed a name."
},
"link_url": {
"type": "string",
"description": "https://app.marcora.ai/runs/{run_id}"
},
"anchor_date": {
"type": [
"string",
"null"
],
"description": "Persisted YYYY-MM-DD reference date, or null."
}
},
"description": "The created cycle."
},
"plans": {
"type": "array",
"items": {
"type": "object",
"properties": {
"link_url": {
"type": "string",
"description": "https://app.marcora.ai/plans/{plan_uuid}"
}
}
},
"description": "The created content plans (same shape as create_plan / get_plan), stage Accepted, source playbook."
},
"run_id": {
"type": "integer",
"description": "ID of the cycle (run) this created — the group the plans belong to."
},
"playbook_id": {
"type": "integer",
"description": "The instantiated playbook."
},
"created_count": {
"type": "integer",
"description": "Number of plans created (one per playbook item)."
}
},
"description": "An object describing the run."
}Instructions
Run a playbook: create one content plan per playbook item, in order, as a batch. Plans land in the Accepted stage with source playbook and inherit the playbook's visibility. Optionally anchor due dates to a date (each item's offset_days is applied to anchor_date) and/or scope the batch to a project. This is a distinct bulk action — it does not create or edit the playbook itself.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
playbook_id |
integer | Yes | ID of the playbook to instantiate |
anchor_date |
string | No | ISO date YYYY-MM-DD. Each item's offset_days is added to it to compute that plan's due date |
project_id |
string (uuid) | No | Scope the created plans to this project |
assigned_to |
integer | No | Assign the created plans to this team member |
category_id |
integer | No | Apply this content category to the created plans |
If anchor_date is omitted, the playbook's persisted anchor_date (if any) is used.
Output: an object describing the run:
| Field | Type | Description |
|---|---|---|
playbook_id |
integer | The instantiated playbook |
run_id |
integer | ID of the cycle (run) this created — the group the plans belong to |
run |
object | The created cycle: id, name (auto-named "<playbook> — <Mon YYYY>" unless you passed a name), anchor_date, and link_url (https://app.marcora.ai/runs/{run_id}) — share it to hand the user their new cycle |
created_count |
integer | Number of plans created (one per playbook item) |
plans |
array | The created content plans (same shape as create_plan / get_plan), each with its own link_url (https://app.marcora.ai/plans/{plan_uuid}). Stage Accepted, source playbook |
Example prompts:
- "Run my launch playbook"
- "Instantiate this template anchored to next Monday"