frontline-workflows

Create, edit, connect, and inspect Frontline automation workflows using the Frontline CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @getfrontline/cli.

What problem does it solve? Building and maintaining Frontline automation workflows through the UI is slow and hard to script. This Skill lets you manage workflows, nodes, edges, variables, and run logs entirely from the Frontline CLI, making workflow automation reproducible and CI-friendly. ## Core Features & Use Cases - Workflow lifecycle management: List, create, update, delete, and select workflows, and manage workflow variables from the command line. - Graph construction: Create trigger, API, loop, WhatsApp, Dynamic Tables, and File Analysis nodes, then connect them with validated edges while inspecting the graph after each change. - Observability: Pull workflow analytics, list run logs, and trace individual node executions to debug failed runs. - Use Case: Build a scheduled workflow that fires on a cron expression, calls an external API, loops over the results, and writes records into a Frontline object table — then audit its runs with frontline workflows logs. ## Quick Start Ask the assistant to list your Frontline workflows as a table and then create a new workflow with a CONTACT_CREATED trigger connected to an API action node.

Frequently Asked Questions about frontline-workflows

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

FAQPage Schema
How do I create a Frontline workflow from the command line?▼

Run frontline workflows create --name "My Workflow" after installing the CLI and authenticating with frontline auth login. The created workflow ID is saved as the active workflow, and you can then add trigger and action nodes with frontline workflows nodes create.

How do I connect nodes in a Frontline workflow graph?▼

Use frontline workflows edges add with --source, --source-handle, --target, and --target-handle flags. The API enforces one outgoing edge per node except for CONDITIONAL_ROUTING, TOOLS_AI, and API nodes, and rejects self-edges and cycles.

Why is my Frontline conversation trigger workflow never running?▼

Conversation triggers like CONVERSATION_ENDED, CONVERSATION_IDLE, and FEEDBACK_CAPTURED require triggeredByAgentIds in the node data. Without it the node saves but the workflow never fires, and CONVERSATION_IDLE also needs enableIdle configured on the agent's channel.

Can I schedule a Frontline workflow to run on a cron expression?▼

Yes, create a SCHEDULED_TRIGGER node with cronExpression, timezone, frequency, and explicit null startTime and endTime fields. The schedule only runs while the workflow status is ACTIVE; setting it back to DRAFT disables the cron job.

How do I debug a failed Frontline workflow run?▼

List runs with frontline workflows logs --status FAILED, inspect one run with logs get to see per-node results, then drill into a single node with logs trace using the log ID and node result ID. Add --debug to any command to see the full HTTP request and response.

What are the limits of Frontline workflow loop nodes?▼

ITERATION nodes process at most 50 items per invocation, and a workflow run allows at most 500 automation execution steps total. Loop item sub-properties like {nodeId.item.id} are not supported, so loop over scalars or extract fields with AI_CAPTURE or DATA_TRANSFORMER nodes.