Forms & triggers

Triggers — how a workflow starts

Every workflow starts in one of these ways:

• Form submitted — someone fills in an intake form (the most common way to start a customer-facing process).
• Manual — a team member starts a run from inside your workspace.
• Scheduled — the workflow runs on a recurring schedule.
• Webhook — another system sends data in to start a run.
• Record created / updated — a run starts when a record changes.

A workflow can have more than one trigger.

Caution

Scheduled and webhook runs have no form submitter, so they don’t automatically carry form data. If a step needs information a person would normally type in, make sure that information is captured on a form (or provided by the incoming webhook).

Forms

A form is how a workflow captures information. Forms are made of fields, and you can share a form’s link so customers or staff can submit it.

Field types

Fields can be, among others:

• Text / long text — names, notes, descriptions.
• Email / phone — used to send email and SMS to the right recipient.
• Number — amounts, scores, quantities (used for value-based decisions).
• Date — deadlines, event dates.
• Select / multi-select / radio / checkboxes — choices that can drive decisions.
• File — uploads and attachments.

Dependent (cascading) dropdowns

A child dropdown’s options can depend on a parent’s selection — for example, Make → Model or Country → City.

Next

• Tasks & approvals →
• Writing effective prompts →