flow-builder

Builds and validates Frontline assistant conversation flows via CLI commands.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill flow-builder-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-builder
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/flow-builder
Command: npx skills add https://github.com/api-evangelist/frontline --skill flow-builder-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Frontline assistant flows by hand is error-prone: invalid node types, missing required fields, bad references, and broken edges all return 400 errors or fail silently. This Skill encodes the exact rules, payloads, and validation steps needed to construct working flow graphs through the Frontline CLI. ## Core Features & Use Cases - Flow graph construction: Create flows, add nodes (START, TRIGGER_INTENT, SAY_AI, RESPONSE_AI, TOOLS_AI, API, CONDITIONAL_ROUTING, CREATE_RECORD_ACTIVITY), and connect them with edges using the correct handles. - Variable and intent management: Create agent variables and intents, capture values into variables from AI or API nodes, and wire intent-based or agentic routing triggers. - Validation guidance: Avoid 400 errors by pre-checking referenced resources (ai-models, custom tools, intents, record types) and respecting rules like required captureVariables, exitNodeWhen, and API node success/fail handles. - Use Case: Build a customer support flow that greets the user, captures their email into a Person record, calls an external API to look up an order, and routes the conversation based on the result. ## Quick Start Ask the assistant to create a new Frontline flow for your agent with a greeting node connected to an intent-triggered response, then inspect the graph to verify the structure.

Frequently Asked Questions about flow-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Frontline assistant flow from the CLI?▼

Select the agent with frontline agents use, create a flow with frontline agents flows create, then add nodes with frontline agents flows nodes create and connect them with edges add. Inspect the result anytime with frontline agents flows graph --table.

How do I capture user input into variables in a Frontline flow?▼

Create the variable first with frontline agents variables create, then reference it in captureVariables on TOOLS_AI or RESPONSE_AI nodes, or in the variables array on an API node using a property path into the JSON response. Using the wrong field is silently ignored.

Which node types are allowed in Frontline flows versus automations?▼

Flows support START, TRIGGER_INTENT, SAY_AI, RESPONSE_AI, TOOLS_AI, API, CONDITIONAL_ROUTING, and CREATE_RECORD_ACTIVITY. Automation-only nodes like TRIGGER, WEBHOOK, SEND_MESSAGE, and DYNAMIC_TABLES are rejected with a 400 error if added to a flow.

Why does my Frontline node creation return a 400 not_found error?▼

Every referenced ID in a node's data, such as customToolIds, intentIds, aiModelId, or recordTypeId, is validated against the database before saving. Look up the resources first with commands like frontline ai-models list or frontline agents intents list, then retry with valid IDs.

Can a Frontline flow have more than one START node?▼

No. A flow uses exactly one initial node, either START or TRIGGER_INTENT, and a START node is only allowed in the agent's default Start flow. Non-default flows must begin with a TRIGGER_INTENT node configured with intents or agentic routing.