Reference
Save a nurture playbook
Create or update a nurture playbook definition.
View MarkdownThis page is generated from the source code on every release.
Create or update a nurture playbook definition.
Overview
| Name | Value |
|---|---|
| Code | playbooks.save |
| Scope needed | nurture.write |
| Risk | Write |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager |
| In the app | Account nurture → Playbooks |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
id |
uuid |
No | |
name |
text |
Yes | |
description |
text |
No | |
definition |
object |
Yes | |
basedOn |
text |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/playbooks.save \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"…","definition":"…"}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
id |
text |
Yes |
Example answer
{
"data": {
"ok": true,
"id": "00000000-0000-4000-8000-000000000000"
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "playbooks.save". Tool name when listed: playbooks_save.