workflow-builder

Builds Frontline automation workflows and agent flows via CLI with triggers, nodes, and edges.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Frontline automation workflows and agent flows through the CLI requires knowing exactly which node types are valid for each graph type, which trigger fields are mandatory, and how variables interpolate — mistakes are rejected with 400 errors or silently never fire. This Skill encodes those rules so workflows are created correctly the first time. ## Core Features & Use Cases - Trigger configuration: Covers CONTACT_CREATED, CONVERSATION_IDLE, INCOMING_WEBHOOK, OBJECT_RECORD_CREATED, COMPOSIO_TRIGGER integration events, and cron-based SCHEDULED_TRIGGER nodes with their required fields. - Node and edge construction: Enforces valid node types per graph (automation vs agent flow), server-assigned nodeId handling, and correct edge handles such as the API node's success/fail outputs. - Data operations: Guides DYNAMIC_TABLES record actions (CREATE, UPDATE, DELETE, SEARCH, CHANGE_RECORD_TYPE) with object schema lookup, plus variable interpolation rules and loop semantics. - Use Case: Create an incoming webhook trigger, pipe the payload through a DATA_TRANSFORMER node to extract contact fields, and write a People record with a DYNAMIC_TABLES node — all wired with correct edges. ## Quick Start Use the workflow-builder skill to create a Frontline automation that triggers on an incoming webhook and creates a People record from the payload.

Frequently Asked Questions about workflow-builder

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

FAQPage Schema
How do I create a Frontline automation workflow from the CLI?▼

Create a workflow with frontline workflows create, add exactly one trigger node (TRIGGER or SCHEDULED_TRIGGER), then add action nodes and connect them with frontline workflows edges add. The workflow must be ACTIVE before any trigger fires.

Why does my conversation trigger never fire in Frontline?▼

CONVERSATION_ENDED, CONVERSATION_IDLE, and FEEDBACK_CAPTURED triggers only run for agents listed in triggeredByAgentIds, so a trigger without that array saves but never fires. For CONVERSATION_IDLE, idle must also be enabled in the agent's channel settings.

Which node types are valid in Frontline agent flows versus automations?▼

Agent flows accept START, TRIGGER_INTENT, SAY_AI, RESPONSE_AI, TOOLS_AI, API, CONDITIONAL_ROUTING, and CREATE_RECORD_ACTIVITY. Automations accept TRIGGER, SCHEDULED_TRIGGER, WEBHOOK, DYNAMIC_TABLES, SEND_MESSAGE, and others; cross-type nodes are rejected with a 400 error.

How do I extract fields from a webhook payload in a Frontline workflow?▼

The full POST body arrives as the {webhook_payload} string variable with no dot-access. Add a DATA_TRANSFORMER or AI_CAPTURE node to parse it into individual workflow variables, then reference those variables in downstream nodes like DYNAMIC_TABLES.

Can I use DYNAMIC_TABLES inside a Frontline agent flow?▼

No, DYNAMIC_TABLES is automation-only and is rejected in flows. Inside a flow, read or write records through a TOOLS_AI node whose agent has table tools granted via selectedRecordTypes permissions.

Why was my Frontline node creation rejected with a 400 error?▼

Common causes include using a node type invalid for that graph type, missing required fields for a DYNAMIC_TABLES actionType, sending nodeId or alias in create payloads, or invalid triggerConfig keys for a COMPOSIO_TRIGGER slug. Run frontline guidance nodes for the authoritative catalog.