Skip to content
Last updated

Agent Playbooks

An Agent Playbook is a reusable instruction set (an SOP) that steers how a customer-facing Agent handles a specific task. A playbook bundles instructions plus optional tools, record types, custom tools, and connected-account configs. You then assign it to one or more agents so they can execute it at runtime.

These are not Max Playbooks, which steer the user's personal Max assistant.

All playbook endpoints require a USER API key.

Identity

FieldTypeNotes
idnumberUse as playbookId.
namestring1–100 characters.
descriptionstringWhen to use this playbook. 10–750 characters.
instructionsstringThe SOP the agent follows. 10–10,000 characters.
isActivebooleanDefault true. Inactive playbooks stay assigned but are not used at runtime.
visibilityenumACCOUNT (shared with the whole account) · PRIVATE (only the creator). Default ACCOUNT.
toolsarraySystem tool names the playbook may use (max 20).
selectedRecordTypesarray?Record-type tool settings.
selectedCustomToolsarray?Custom-tool settings.
playbookConnectedAccountsarray?Connected-account tool configs (connectedAccountId, useAllTools, selectedToolSlugs).
createdByUserIdnumber?Creator. Only the creator (or an OWNER/ADMIN) can update; only the creator can delete.
createdAtstringISO timestamp.
updatedAtstringISO timestamp.

Assigning playbooks to an agent

Playbooks are account-scoped resources. Assigning them to an agent is a separate step:

  • GET /agents/{agentId}/playbooks — which playbooks that agent currently has.
  • PUT /agents/{agentId}/playbooks — replaces the full assignment set. Send { "playbookIds": [1, 2] } to set it, or { "playbookIds": [] } to unassign all.

You also wire playbooks through PUT /agents/{agentId}/agent-setting (the agent's brain). The dedicated assign endpoint is the one to use when you only want to change which playbooks are attached.

Operations

VerbPathPurpose
GET/public/v1/playbooksList (filters: filterText, visibility, isActive)
POST/public/v1/playbooksCreate (USER key)
GET/public/v1/playbooks/{playbookId}Detail
PUT/public/v1/playbooks/{playbookId}Update (creator or OWNER/ADMIN)
DELETE/public/v1/playbooks/{playbookId}Delete (creator only)
GET/public/v1/agents/{agentId}/playbooksList assigned to an agent
PUT/public/v1/agents/{agentId}/playbooksReplace the assignment set

Full list in the API Reference under the Agent Playbooks tag.

CLI

frontline playbooks list --table
frontline playbooks create \
  --name "Refund flow" \
  --description "How to process a customer refund request" \
  --instructions "1. Verify the order number. 2. Confirm the refund window. 3. ..."
frontline playbooks assign --agent-id <agentId> --playbook-ids '[1,2]'
frontline playbooks assigned --agent-id <agentId> --table