FormTrigger NodeTypeCode: form-trigger

When to Use

• Employee leave request: An employee fills in a leave request form (leave type, start/end dates, notes). On submission, the workflow routes to the manager for approval, checks leave balance in the HRMS, and creates the calendar block — all triggered by form submission with no manual handoff.
• Expense claim submission: Finance distributes an expense claim form to employees. The form captures expense type, amount, date, cost center, and receipt upload. Submission triggers the approval routing workflow based on amount thresholds and policy rules.
• IT access request: A new employee submits an IT access request form listing systems they need access to and the business justification. Submission creates the IT ticket, routes for manager approval, and triggers provisioning steps once approved.
• Customer feedback form: After service delivery, the workflow sends a customer a satisfaction survey form. Submission triggers sentiment analysis, routes negative responses to the support team, and logs results in the CRM.
• Vendor onboarding form: A new vendor is sent a structured onboarding form to capture business details, compliance declarations, and banking information. Submission triggers the vendor verification and ERP setup workflow.

Two-Phase Execution

Configuration

Output Ports

Output Fields

These fields are available on the success port after the form is submitted:

Sample Configuration

{
  "nodeType": "form-trigger",
  "settings": {
    "form_schema": 10045,
    "assigned_to": "user:{{ $output.hrLookup.employeeUserId }}",
    "title": "Annual Leave Request — {{ $output.hrLookup.employeeFullName }}",
    "description": "Please complete your leave request form. Your manager will be notified automatically on submission."
  }
}

Sample Output

Success Port — Form Submitted

{
  "formId": 13005,
  "submissionId": "sub_xyz123",
  "submittedBy": {
    "userId": "usr_emp_007",
    "name": "Michael Torres",
    "email": "m.torres@company.com"
  },
  "submittedAt": "2025-03-15T10:45:00Z",
  "data": {
    "requestType": "Equipment Purchase",
    "itemDescription": "Standing desk — ergonomic model",
    "estimatedCost": 650.00,
    "currency": "USD",
    "businessJustification": "Improving ergonomics for remote work setup",
    "urgency": "medium",
    "managerApproved": true
  },
  "formVersion": "1.2",
  "workflowTriggered": "expense-approval-workflow"
}

Expression Reference

Node Policies & GuardRails

Pattern Examples

Pattern 1 — Employee Leave Request Workflow

A triggered workflow (from ManualTrigger or a scheduled email prompt) sends each employee a leave request form. On submission, the manager is notified and the approval chain begins.

// FormTrigger settings — dynamically assign to the requesting employee
{
  "form_schema": 10045,
  "assigned_to": "user:{{ $var.requestingEmployeeId }}",
  "title": "Leave Request Form",
  "description": "Please fill in your leave details. Your line manager will receive a notification on submission."
}

// Downstream on 'success' port — extract leave period
{
  "Mappings": [
    { "SourceField": "form_data.leaveType",  "TargetField": "leaveType" },
    { "SourceField": "form_data.startDate",  "TargetField": "leaveStart" },
    { "SourceField": "form_data.endDate",    "TargetField": "leaveEnd" },
    { "SourceField": "form_data.reason",     "TargetField": "reason" }
  ]
}
// Downstream: Approval node assigned to manager

Pattern 2 — IT Access Request with Role Assignment

Any employee in the "staff" role can submit an IT access request form. Submission creates a Jira ticket and routes for manager approval.

// FormTrigger settings — assign to role, not specific user
{
  "form_schema": 11200,
  "assigned_to": "role:staff",
  "title": "IT System Access Request",
  "description": "List the systems you need access to and provide business justification. Your manager and IT team will be notified."
}

// Downstream on 'success' port — CodeExecute to build Jira payload
var form = formData;
result = {
  summary: "Access Request: " + form.requestedSystems.join(", "),
  description: form.justification,
  requestedBy: submitted_by,
  priority: form.urgency === "high" ? "P1" : "P3"
};