list_flow_templates
Returns actual template keys, names, descriptions and full example definitions..
On this page
Purpose
Ready-made flows (welcome, trial nudge, dunning, dormant-paid, win-back, recovery, high-MRR alert, onboarding series, upgrade nudge) with their complete definitions — use them as worked examples of the definition schema, or pass templateKey to create_flow.
Credentials and scope
Owner workspace credential. The credential determines tool visibility. For tools with appId, use the HeyCrust app UUID from list_apps; the dashboard app selector does not supply MCP arguments for you.
Inputs
This tool accepts an empty argument object.
Example request
The identifiers and merchant are fictional. Replace them with records returned for your own workspace; this example is schema-checked, not a promise that the fictional record exists.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_flow_templates",
"arguments": {}
}
}
POST this JSON to https://heycrust.com/api/mcp with Content-Type: application/json and Authorization: Bearer <YOUR_CREDENTIAL>. The tool result normally contains JSON encoded as text in result.content; inspect JSON-RPC errors and result.isError before using it.
Result
Returns actual template keys, names, descriptions and full example definitions.
Effects and verification
Reads existing records or definitions. It does not create a payment or send a message. Verify the returned app/merchant identity and source coverage before interpreting the result.
Troubleshooting
A missing tool can mean that the credential lacks its catalog or required scopes. Invalid arguments are different from unavailable source data or a record outside the workspace. A handler can return a business error even when the argument schema is valid. Read MCP overview and Help.