Skip to Content

Form Templates

A Form Template turns a visual workflow into an interactive, standalone form. Non-technical colleagues, clients, or external partners simply fill in the defined input fields and click Run.

The runner never sees the underlying canvas, intermediate logic steps, or sensitive connected credentials. Use a Form Template whenever an automation should be operated by people who need the result without having to learn or modify the workflow.


Comparing Deployment Interfaces

FeatureForm Template (Form Interface)Chat Interface (Chat Trigger)Step Template (Canvas Fork)
User InteractionStructured web form submissionInteractive multi-turn chatFull visual canvas editor
Best ForData intake, HR requests, report generationSupport bots, documentation Q&A, Slack helpersReusable workflow patterns & blueprints
Canvas VisibilityCompletely hiddenCompletely hiddenFull canvas visible & editable
CredentialsUses builderโ€™s secure workspace connectionsUses builderโ€™s secure workspace connectionsRequires forker to connect own accounts
Entry PointForm link or workspace DeploymentHosted chat page or Slack botMarketplace or workspace template library

How to Build a Form Interface

You build the automation on the multiplayer canvas as normal, then choose which fields across your steps should be exposed on the public form:

Open the Form Interface Drawer

On your workflow canvas, click More (โ‹ฎ) in the top-right toolbar and select Form interface (or click the Interfaces icon in the bottom-right dock).

Select Fields from Canvas Steps

Click Add fields. The drawer displays all steps on your canvas. Click any step to inspect its configurable parameters, then check the fields you want the form runner to provide.

Configure Labels, Descriptions & Validation

For each exposed field, customize the presentation:

  • Field Label: Give the field a clear, non-technical title (e.g. Customer Email Address instead of cust_email).
  • Placeholder & Helper Note: Add instructions or format hints (e.g. e.g. [email protected]).
  • Required toggle: Mark whether the field is mandatory before the runner can submit the form.

Enable Pre-filled Default Values (Optional)

Toggle on Default values to populate the form with initial values derived from your current canvas step configuration. This lets runners submit standard requests with a single click while still allowing customization when needed.

Preview and Test

Test the form directly inside the drawer preview. Enter sample inputs and confirm that values map correctly into your canvas steps before deploying.


Supported Form Field Types

Glow automatically renders the appropriate UI control based on the underlying step parameter type:

Field TypeForm ControlExamples & Use Cases
Short TextSingle-line text inputCustomer names, email addresses, order IDs
Long Text / MarkdownMulti-line textareaSupport ticket descriptions, feedback comments
NumericNumber input with increment controlsInvoice amounts, item quantities, threshold caps
Single SelectDropdown selection menuPriority tiers (Low, Medium, High), department choices
Date & TimeCalendar date/time pickerAppointment dates, report start/end dates
File UploadDrag-and-drop file uploaderPDF invoices, CSV datasets, image receipts

Deploying and Sharing the Form

Once your form interface is configured, you have several ways to distribute it:

Generate a standalone hosted web URL:

  1. Switch your workflow from Draft to Live in the top navigation bar.
  2. In the canvas header, click Share โ†’ Form Link.
  3. Choose access permissions:
    • Public: Anyone holding the link can submit the form.
    • Workspace Members Only: Requires signing in with an authenticated workspace account.

Runner Experience and Result Delivery

When an end-user opens your Form Template link:

  1. Clean Branded View: They see a clean, distraction-free interface displaying only your configured input fields, descriptions, and a prominent Run button.
  2. Real-Time Validation: Required fields and format constraints (e.g. valid email syntax or file upload size limits) are validated client-side before submission.
  3. Execution Delivery:
    • Synchronous Workflows: If the workflow produces an immediate output (such as a generated summary or calculated score), the result displays directly on the completion screen.
    • Asynchronous Workflows: For background automations (such as updating Salesforce records or sending Slack notifications), the runner receives a confirmation receipt while work completes in the background.

Real-World Use Case Patterns

Template PatternCanvas WorkflowRunner Experience
Client Onboarding IntakeForm Intake โ†’ Create HubSpot Contact โ†’ Generate Google Drive Folder โ†’ Alert SlackClient account manager enters customer details and uploads contract PDF.
AI Expense Receipt ProcessorForm Intake (File Upload) โ†’ AI Prompt (Extract JSON) โ†’ Validate โ†’ Quickbooks WriteEmployee uploads photo of receipt; total amount and category are extracted and submitted.
Custom Data Query GeneratorForm Intake (Date Range & Filters) โ†’ Database Query โ†’ Format CSV โ†’ Email AttachmentOperations team selects date range and receives automated CSV export in their inbox.

Whatโ€™s Next?