Form Templates

Expose selected Step fields as a form so users can run an automation without editing its canvas. You choose which inputs runners supply and which Step settings stay fixed.

At a glanceVerified in app · Oct 30, 2026

Use it to: Expose selected Step parameters as a guided input form so workspace members can supply inputs and click Run without editing the canvas
Find it: Canvas → More (⋮) → Form interface (or Left sidebar → Deployment → Interface: Form)
Limits: Requires Admin, Manager, or Member role in the workspace to run (Viewers cannot execute automations)
Output: A guided runner form view backed by the workspace automation's configured connections
Instead: Form Trigger (Tools → Start → Form) when external visitors need a standalone public or password-protected web form URL

Select the Step fields a runner supplies, add guidance and prepare defaults.

Form Interface

Use a Chat trigger when the automation needs conversational input and replies.

Chat Interface

Share the editable automation blueprint with the person who will maintain it.

Step Templates

Before You Start

Build and test the underlying automation first, then choose which Step fields to expose and which values stay fixed. Running any copy uses the destination workspace’s configured connections, and a form view does not change Automation Visibility and Sharing.

For signed-in workspace membersForm Interface (this page)

Lives inside your workspace and presents selected Step fields as a runner form.
Requires an Admin, Manager, or Member role in the workspace to fill in and click Run.
Can be published to the Marketplace as a Form template for other workspaces to copy.

For external visitors & public linksForm Trigger (Tools → Start → Form)

A trigger Step on the canvas that gives the automation its own public or password-protected web form URL.
Anyone with the link can submit the form to start a run without signing in to Glow.
Submitted answers arrive in downstream Steps under {{ 1.formData.<field> }}.

How to Build a Form Interface

Open the Form Interface Drawer

On the canvas, open More (⋮) → Form interface. You can also configure Form mode from the Deployment page.

Select Fields from Steps

Click Add fields, choose the Step fields you want to expose, and confirm the selection. Custom Variables rows are listed by their key name. Expose only the inputs the runner needs, not credentials or internal configuration.

Configure Labels, Help Text, Required State, and Defaults

For each exposed field, customize its Label (up to 120 characters), Help text (up to 500 characters), and Required toggle. A field required by an integration operation’s input schema stays required.

Enable Default values if the form should prefill configured defaults. Recipient email fields (to, cc, bcc, replyTo, from, sender, recipient) and choice pickers cannot share defaults across workspaces, and any literal email address in a default is stripped on copy or install. Exposed Custom Variables rows start blank on installed template copies so runners enter their own values.

Preview the Form

Click Preview to inspect the form layout, exposed fields, and default values. To test execution, open a configured workspace copy, fill in its inputs, and run it against test destinations.

Choose the route that matches your audience:

Audience	Procedure	Accounts used when running
Colleagues in this workspace	Share the automation link with people who have access.	The automation’s configured workspace connections.
Builders or operators acquiring a Marketplace template	Follow Publishing Templates. Recipients follow Forking a Template.	Connections configured in the recipient’s workspace.
Managed client workspaces	Follow the versioned deployment procedure.	Destination workspace connections; review them before activation.

Configuring the form does not publish it. Client deployment creates independent Draft copies; review credential isolation and account rebinding before testing.

Running and Checking Results

Prepare the Workspace Copy

Confirm the automation has the required app connections and that the runner holds an Admin, Manager, or Member role in the workspace (Viewers have read-only access). When an exposed integration Step requires an account, the form displays a Connection picker above that Step’s fields. Runners can select an existing workspace connection or authorize a new one directly from the form. To accept submissions from external visitors without a Glow login, use a Form Trigger instead.

Fill In and Run

Enter the exposed inputs. Picks and yes/no toggles save immediately while text fields save after a short pause. Clicking Run flushes all pending field edits first, checks for empty required fields (<Label> is required), and starts a single run. Running a form can send messages or change records just like running from the canvas.

Verify the Run Outcome

When the run finishes, the form displays Succeeded or Failed, shows the last AI Step’s output text and "Sent with <step>" delivery summary, and provides a View run link to inspect the execution trace. Confirm delivery in the configured destination.

Use Case Patterns

Common patterns you can build with a Form interface:

Pattern	Exposed inputs	Automation and result to verify
Client onboarding	Customer name and email	Create a CRM contact, then notify the onboarding team. Check both destinations.
Invoice review	Extracted invoice text	Extract structured fields, request approval and write approved rows. PDF or image intake needs document extraction first.
Report request	Date range and filters supported by the selected Step	Query records, format the result and send it to a configured destination.

Verify it works

Run: Open More (⋮) → Form interface on the canvas, add a Step field, and click Preview
You should see: The form view displays your exposed input controls, helper notes, and configured default values.

What’s Next?

Form Trigger: start an automation from a standalone hosted web form at a shareable URL.
Publishing Templates: publish a version or deploy it to managed clients.
Chat Trigger: build a conversational entry point.
Step Templates: share editable automation blueprints.