Shapes

Every shape in the builder.
When to use it, and how.

Flows are built from shapes. A trigger starts the flow, work shapes handle the records, and connector steps reach your systems. Each one has its own page with when to reach for it, an example and every setting.

Start a flow

One trigger decides when a flow runs: a call from a system, a form, the clock, a change or a stream.

5 shapes 02

Work in a flow

Shapes filter, reshape, convert, wait, decide and bring in people, AI and code.

42 shapes 03

Connect to systems

Connector steps and HTTP request read from and write to the systems you use.

Every connector, plus HTTP request

01 · Start a flow

Which trigger do I need?

Every automated flow begins with one trigger. Pick the one that matches how the work arrives: a call from another system, a person filling in a form, the clock, a change in a system, or a live stream of events.

“Another system can tell you when something happens”Webhook“A person submits a request or answers questions”Form (starts flow)“It should run at set times”Schedule“You need what changed in a system that cannot send notifications”Poll for changes“Events arrive continuously on a queue or stream”Live stream

No trigger at all? The flow runs when you press Run, or when another flow, an app, an AI agent or the API starts it. How flows start

02 · Work in a flow

Shapes that do the work

Grouped by what you want to achieve. Each card shows where to find the shape in the builder's node library.

Filter and organize records

Decide which records continue, in what order and in what grouping: filter, sort, remove duplicates, split lists apart or pack records together.

FilterKeeps only the records that match a condition and drops the rest.Nodes › Logic SortOrders records by a field, ascending or descending.Nodes › Logic Keep first NPasses on only the first records, up to the number you set.Nodes › Logic Remove duplicatesRemoves repeated records, or tags them for review, using exact, fuzzy or phonetic matching.Nodes › Logic SplitTurns one record that holds a list into one record per list item.Nodes › Logic Group into batchesPacks records into groups of a fixed size, so one call can carry many records.Nodes › Logic Merge by keyCombines records that share a key into a single record.Nodes › Logic AggregateCollapses all records into one record with a list and a count.Nodes › Logic Group & summarizeGroups records by a field and calculates a count, sum, average, minimum or maximum per group.Nodes › Logic

Reshape and enrich records

Give records the shape the next system expects: map and rename fields, add values, enrich from earlier steps and keep data in built-in tables.

Convert and format values

Turn values into the format a destination needs: dates, JSON, CSV and XML text, hashes and signatures, HTML and compressed payloads.

Hash valueCreates a SHA-256 or SHA-512 fingerprint of a field, or a signature with your key.Nodes › Data Format dateReformats a date or time into the pattern a system expects.Nodes › Data Convert JSONConverts between records and JSON, CSV or XML text.Nodes › Data Compress (zip)Compresses a text field with gzip and encodes it for transport.Nodes › Data Scrape websiteExtracts values from HTML with CSS selectors.Nodes › Data Render markdownTurns Markdown into safe HTML.Nodes › Data

Files and EDI

Create and read files, and exchange EDI documents with trading partners.

Create ExcelBuilds an Excel workbook from all records, ready to attach or upload.Nodes › Files Create fileBuilds one CSV, JSON or text file from all records.Nodes › Files Read fileReads a CSV, JSON or text file carried on a record back into records.Nodes › Files Read EDIReads ANSI X12 or UN/EDIFACT documents into a structure you can map.Nodes › Files Build EDIBuilds EDI text from a structure, ready to send to a partner.Nodes › Files Validate EDIChecks an EDI document's envelope and required business segments.Nodes › Files Acknowledge EDIBuilds the functional acknowledgment (997, 999 or CONTRL) to send back to the partner.Nodes › Files

Control the run

Repeat steps, reuse flows, wait for time or events, keep values for later, and stop a run deliberately when something is wrong.

LoopRepeats a group of steps for each record, a set number of times, or while or until a condition holds.Nodes › Logic Run another flowRuns another flow as a reusable sub-flow and continues with its result.Nodes › Logic WaitPauses for a set time before passing records on.Nodes › Logic Wait for eventPauses the run until a matching event arrives, then continues with its data.Nodes › Logic Set valueSaves a named value that later steps in the same run can read.Nodes › Logic Assert Data QualityChecks the batch against your rules and stops with precise details when one fails.Nodes › Logic Validate RecordsChecks each record against a JSON Schema and tags it valid or invalid.Nodes › Logic ErrorStops the run on purpose with your own message.Nodes › Logic Pass throughPasses records through unchanged, as a labelled join point or placeholder.Nodes › Logic

People, AI and code

Bring in a person for review and approval, an AI agent for judgement, or a script for logic no other shape covers.

Wait for formPauses the run and gives a person a form to review, correct or approve.Nodes › Logic AI agentLets an AI agent reason over each record and use the tools you allow.Nodes › AI CodeRuns a Rhai script for logic the other shapes do not cover.Nodes › Code

03 · Connect to systems

Reach every system you use

Read from and write to the systems you use. Connector steps cover the built-in connectors; HTTP request reaches any other API.

Connector stepRuns an operation in a connected system: read, create, update, query and more.Nodes › adapters HTTP requestCalls any HTTP or HTTPS endpoint, with pagination and sign-in from a connection.Nodes › Logic

ConnectionsSave the sign-in for a system once and reuse it in every flow.Connector directoryEvery built-in connector with its operations and triggers.On-Prem WorkersReach systems inside your own network.Custom integrationsAdd any API from its specification.

Putting shapes together

How shapes work together

Lines carry recordsConnect shapes from output to input. Add conditions to a line to send records down different paths.Every step can recoverRetries, error routing and rollback are settings on each step.Values come from anywhereMap fields from earlier steps, variables, flow values or expressions.Test as you buildRun the flow and click any step to see what it received and produced.

Every shape in the builder.When to use it, and how.

Three kinds of shapes