Requires the Personas permission. Tools in this group are hidden from
tools/list and refused on call when your plan does not grant it.persona_create
Write Define an ideal customer profile. Returns apersonaId — a QUALIFIER step needs one, and the flow save is rejected without it, so create the persona before calling flow_set. This defines the filter only; it does not add a QUALIFIER step to any sequence. Note QUALIFIER also needs the Personas permission on top of Pro. Requires a Pro or Agency plan.
Parameters
string
required
Persona name, e.g. “Series B RevOps leaders”.
string
Longer explanatory text.
object
required
Qualification rules. Unrecognised keys are stripped server-side.
persona_get
Read-only Full qualification criteria for one persona — job titles, seniority, industries, size, locations and keyword rules — as a QUALIFIER step will apply them. Read this to explain why a lead did or did not qualify. It does not say which leads qualified: for that read the step withsequence_leads_at_step. Requires a Pro or Agency plan.
Parameters
string
required
Persona id, from
persona_list.persona_list
Read-only Ideal-customer definitions used by QUALIFIER steps.usageCount shows how many flows reference each one. A persona describes WHO a lead must be to pass a QUALIFIER step. It is not an AI agent (agent_list, which writes replies) and not a lead tag (tag_list, which classifies replies after the fact). Requires a Pro or Agency plan.
No parameters.
persona_update
Write Destructive Change a persona’s criteria. Live QUALIFIER steps pick this up on their next evaluation — leads already past the step are not re-scored, so editing a persona never revisits a decision already made. CheckusageCount in persona_list first: a persona shared by several flows changes all of them at once. Requires a Pro or Agency plan.
Parameters
string
required
Persona id, from
persona_list.string
Short label.
string
Longer explanatory text.
object
Qualification rules. Unrecognised keys are stripped server-side.