Skip to content

chatfuel-lab/wizard / content/modules/flow-builder/skill

Chatfuel Flow Builder

The visual flow editor surface: flows, canvas blocks, strongly-typed plugin cards, buttons/handles, connections. No JSON configs, no flow-builder subscriptions — reconcile from mutation results. Not to be confused with Automations (per-scope AI behaviour — the chatfuel-automations skill).

Before writing code read ../chatfuel-core/SKILL.md: required inputs (base URL, token, botID), the mandatory CORS proxy, and the working rules.

Quickstart: minimal flow builder

1. flows  = FlowsList                        -> sidebar               (examples/operations.graphql)
2. canvas = FlowStructure                    -> blocks + connections; render EVERY __typename
3. move   = MoveBlock / MoveBlocksBulk       -> on drag-end (Int coords)
4. create = <plugin>CreateWithBlock[AndConnection] -> no createBlock exists
5. edit   = per-field setters (SetWhatsAppText, ...) -> reconcile from returned block; re-read errors
6. wire   = ConnectBlocks / ConnectComponent -> handles = button/row/condition ids
7. test   = FlowTestStart + FlowTest* sends/clicks   -> references/test-panel.md

Files

FileWhat's inside
references/guide.mdMental model, plugin catalog, creation/editing/wiring, TemplateStr, validation-as-state, uploads, broadcasts, AI-agent block
examples/operations.graphqlValidated operations; its FlowStructure fragments cover every block/element type — copy them wholesale
references/test-panel.mdThe Test panel: session lifecycle, clicks, restart-as-watermark, what the preview API cannot do
../chatfuel-core/references/gotchas.mdRead before writing any operation
../chatfuel-core/references/possible-types.jsonAuthoritative Block / BlockElement type lists for the generic canvas fallback
../chatfuel-core/references/misc.mdBroadcast UTC/weekday scheduling algorithm, keyword rules

Rules

  • Validate every operation with ../chatfuel-core/scripts/validate-operations.mjs against ../chatfuel-core/references/schema.graphql before running it live.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall