create-workflow

Create deterministic multi-step voice workflows with a visual node editor.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/imalfect/callwrench-ai --skill create-workflow-imalfect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-workflow
Source: https://github.com/imalfect/callwrench-ai/tree/main/.agents/skills/create-workflow
Command: npx skills add https://github.com/imalfect/callwrench-ai --skill create-workflow-imalfect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build deterministic, visual workflows for multi-step voice conversations, reducing reliance on ad-hoc prompts and manual wiring.

Core Features & Use Cases

  • Visual node-based flows for conversation steps, tool execution, conditions, and handoffs.
  • Deterministic branching and state management to ensure predictable interactions.
  • Quick deployment and integration via the Vapi Dashboard and API for phone-number or call-based workflows.

Quick Start

Open the Vapi Dashboard and create a new workflow, then add Conversation, Tool, Condition, and Handoff nodes to model your call flow.

Frequently Asked Questions about create-workflow

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

FAQPage Schema
How do I build deterministic voice workflows with branching and handoffs?

Build deterministic voice workflows by using a visual node editor to map out conversation steps, tool execution, conditions, and handoffs. This approach replaces ad-hoc prompts with predictable, state-managed interactions for complex call-center scenarios.

What is a node-based visual editor for voice assistant flows?

A node-based visual editor for voice assistant flows allows you to design multi-step conversations by connecting different node types. You use Conversation, Tool, Condition, and Handoff nodes to model deterministic call flows and ensure predictable interactions.

How do I set up multi-step voice conversations in the Vapi Dashboard?

Set up multi-step voice conversations in the Vapi Dashboard by creating a new workflow and adding Conversation, Tool, Condition, and Handoff nodes. This models your call flow visually and enables quick deployment for phone-number or call-based workflows.

Do I need a VAPI_API_KEY to deploy call-center voice workflows?

Yes, you need a VAPI_API_KEY and internet access to deploy call-center voice workflows. These requirements allow the system to leverage the Dashboard and API for configuration and deployment of your deterministic voice flows.

Can I use visual workflow nodes for phone-number based voice deployments?

Yes, you can use visual workflow nodes for phone-number based voice deployments. The system leverages the Vapi Dashboard and API for quick deployment, allowing you to configure and deploy deterministic voice workflows to handle call-based scenarios.

Why use deterministic branching for voice assistant conversations instead of ad-hoc prompts?

Use deterministic branching for voice assistant conversations to reduce reliance on ad-hoc prompts and manual wiring. It provides state management and predictable interactions, ensuring multi-step voice flows execute reliably without unexpected deviations.