Skip to content
NewTalk to Basher from your browser — free

Platform · Flow builder

Draw the call. Publish the drawing.

Every shape on the canvas is a step the engine executes — listen, decide, call your API, transfer warm to a human, hang up cleanly. No developer needed: you draw it and publish it yourself, and publishing checks every step against the runtime it will run on.

Illustration — a design studio's tilted drafting screen at night seen close, a flow diagram drawn on its face, a gold line stepping up once at its edge
One call, on the path you drew for it. The branch it didn't take stays visible — nothing about a Basher call happens off the canvas.

The vocabulary of a call

  • 13 NODE TYPES · 11 EXECUTED

    Real, executable nodes

    Eleven node types the engine executes — start, message, listen, condition, set-variable, api-call, transfer, hangup, goto, knowledge-base and wait — plus two the canvas keeps to itself: sub-flow, which groups steps, and comment, which annotates them. A runtime vocabulary, not a drawing palette.

  • LISTEN-NODE

    Listening with expectations

    A listen node declares what it expects — free-form, yes/no, number, date or a choice list — with its own timeout, retry count and a no-input action: re-prompt, continue, transfer or hang up.

  • 12 OPERATORS

    Branching that reads the caller

    Conditions branch on twelve operators — equals, contains, starts-with, greater-than, matches-regex, intent-is and the rest — each branch wired to its own output port, with an explicit default port for everything else.

  • API-CALL

    Your systems, mid-sentence

    It asks your calendar for a free slot and books it while the caller is still talking — and if your system stumbles, it quietly retries and never claims a success that didn't happen. The full anatomy of that call lives on the Integrations page and in the spec sheet below.

  • SIMULATOR

    Test the branches before callers do

    Pin a simulated status and response body on any api-call node and walk every branch in the simulator before publishing. Fixtures never ship to the runtime — the translator ignores them.

Spec sheet — as enforced in code

  • 11 / 2

    Node types — executed / canvas-only

  • 12

    Condition operators

  • backoff 250ms → 2s

    API retries — 429 and 5xx only

  • fail-closed

    Secret resolution

  • draft → published, versioned

    Publishing

Node types and operators are counted from the flow type definitions the builder and the execution engine share.

The platform

The rest of the platform

Draw your first call flow.

Talk to the live agent to hear what a published flow does, then open the canvas and draw your own — node by node.

Talk to Basher liveBook a walkthrough