Form Trigger

Overview

The Form Trigger creates a custom web form that starts your workflow when submitted. It’s perfect for collecting information from users - whether they’re internal team members or external customers - and automatically processing that data.

Best for: Intake forms, data collection, customer requests, feedback gathering, and application submissions.

When to Use Form Trigger

Perfect for:

Customer feedback or support request forms
Internal request forms (IT tickets, access requests)
Application or registration forms
Survey responses that need processing
Data collection from non-technical users

Not ideal for:

System-to-system integrations (use Webhook Trigger)
Scheduled recurring tasks (use Scheduled Trigger)
Processing existing data (use Manual Trigger)

Configuration

Basic Setup

Form Title: Give your form a descriptive name
Description: Optional subtitle or instructions
Thank You Message: Message shown after successful submission

Field Types

Add fields to collect specific data:

Field Type	Description	Use Case
Text	Single-line text input	Name, email, title
Long Text	Multi-line text area	Feedback, descriptions, comments
Number	Numeric input	Quantity, amount, rating
Email	Email with validation	Contact information
Phone	Phone number input	Contact information
Date	Date picker	Due dates, event dates
Dropdown	Select from predefined options	Category, priority, department
Checkbox	True/false selection	Agreements, preferences
File Upload	Attachment upload	Documents, images, PDFs

Field Configuration

For each field, configure:

Field Name: Internal identifier (use snake_case: customer_name)
Label: Display text shown to users
Description: Optional help text
Required: Whether the field must be filled

How It Works

Form URL is generated automatically
User fills out the form fields
Form validates all required fields and formats
On submission, workflow starts with form data
User sees the thank you message
Form data is available in the workflow via {{form.field_name}}

Example Use Cases

Customer Feedback Form

Form Trigger
  - name (text, required)
  - email (email, required)
  - feedback (long text, required)
  - product (dropdown: App, Web, API)

→ Agent: Analyze sentiment and categorize
→ Condition: Check priority
  → High: Notify product team
  → Low: Store in database
→ Action: Create ticket in support system

IT Support Request

Form Trigger
  - requester_name (text, required)
  - department (dropdown)
  - issue_type (dropdown: Hardware, Software, Access)
  - description (long text, required)
  - urgency (dropdown: Low, Medium, High)

→ Agent: Classify issue and suggest solution
→ Action: Create JIRA ticket
→ Notification: Alert IT team

Job Application

Form Trigger
  - applicant_name (text, required)
  - email (email, required)
  - position (dropdown)
  - resume (file upload, required)
  - cover_letter (long text)

→ Agent: Extract candidate info from resume
→ Agent: Screen against job requirements
→ Condition: Check fit score
  → Strong: Schedule interview
  → Moderate: Add to review queue
  → Weak: Send polite rejection

Accessing Form Data

Use the trigger variable to access submitted data:

Customer Name:
{{form1.output.name}}
Email:
{{form.output.email}}
Feedback:
{{form.output.feedback}}
Selected Product:
{{form.output.product}}

File Uploads

For file upload fields, access the file metadata:

File name:
{{form.output.metadata.filename}}
Mime-Type URL:
{{form.output.metadata.mimeType}}
File size:
{{form.output.metadata.size}}

Copy Form URL

Click on the Form Trigger node
Click “Copy URL” in the node toolbar
Share the URL via email, chat, or embed on your website
The URL is publicly available when it was configured like that

Embedding Options

Direct Link

<a href="https://app.langdock.com/workflows/forms/abc123">Submit Feedback</a>

iFrame Embed

<iframe
  src="https://app.langdock.com/workflows/forms/abc123"
  width="100%"
  height="600"
  frameborder="0"
>
</iframe>

Best Practices

Keep Forms Short

Only ask for essential information. Long forms have higher abandonment rates. You can always collect additional details later in the workflow.

Use Clear Labels

Field labels should clearly indicate what information is needed. Add description text for fields that might be confusing.

Set Appropriate Defaults

Pre-fill fields with sensible defaults when possible to reduce user effort.

Test the User Experience

Submit test forms yourself to ensure the experience is smooth and instructions are clear.

Add Thank You Context

Your thank you message should set expectations: “We’ll review your request within 24 hours” or “Check your email for next steps.”

Next Steps

Webhook Trigger

Receive HTTP POST requests from external systems

Agent Node

Process form submissions with AI

Getting Started

Step-by-step tutorial with form example

Field Modes

Learn about configuring form fields

Getting started

Chat

Assistants

Integrations

Workflows

Overview

When to Use Form Trigger

Configuration

Basic Setup

Field Types

Field Configuration

How It Works

Example Use Cases

Customer Feedback Form

IT Support Request

Job Application

Accessing Form Data

File Uploads

Copy Form URL

Embedding Options

Best Practices

Next Steps

Webhook Trigger

Agent Node

Getting Started

Field Modes

Getting started

Chat

Assistants

Integrations

Workflows

​Overview

​When to Use Form Trigger

​Configuration

​Basic Setup

​Field Types

​Field Configuration

​How It Works

​Example Use Cases

​Customer Feedback Form

​IT Support Request

​Job Application

​Accessing Form Data

​File Uploads

​Sharing Your Form

​Copy Form URL

​Embedding Options

​Best Practices

​Next Steps

Webhook Trigger

Agent Node

Getting Started

Field Modes

Overview

When to Use Form Trigger

Configuration

Basic Setup

Field Types

Field Configuration

How It Works

Example Use Cases

Customer Feedback Form

IT Support Request

Job Application

Accessing Form Data

File Uploads

Sharing Your Form

Copy Form URL

Embedding Options

Best Practices

Next Steps