Form Trigger

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

1

Form Title

Give your form a descriptive name.

2

Description

Optional subtitle or instructions.

3

Thank You Message

Message shown after successful submission.

Form Trigger

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

Form Fields

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

1

Form URL is generated automatically.

2

User fills out the form fields.

3

Form validates all required fields and formats.

4

On submission, workflow starts with form data.

5

User sees the thank you message.

6

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

Form Fields Output

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}}

Sharing Your Form

Copy Form URL

1

Click on the Form Trigger node.

2

Click “Copy URL” in the node toolbar.

3

Share the URL via email, chat, or embed on your website.

4

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.

• Use clear labels. Add description text for fields that might be confusing.

• Set appropriate defaults. Pre-fill fields when possible to reduce user effort.

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

Next Steps

Related pages

• 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

Form Trigger

Form Trigger

Form Fields

Form Fields Output