Form — Examples

{
  "assigned_to": "{{ $var.new_employee_id }}",
  "form_schema": "form:employee-onboarding-v4",
  "title": "Welcome to {{ $var.company_name }} — Please Complete Your Onboarding Form",
  "description": "Hi {{ $var.first_name }}, welcome aboard! Please complete this form within 3 days to set up your accounts, payroll, and equipment. Fields marked * are required. Contact HR at hr@company.com if you need assistance.",
  "due_at": "{{ $now.AddHours(72) }}",
  "prefill": {
    "first_name": "{{ $var.first_name }}",
    "last_name": "{{ $var.last_name }}",
    "work_email": "{{ $var.work_email }}",
    "department": "{{ $var.department }}",
    "start_date": "{{ $var.start_date }}"
  }
}

Outcome: On submission, form_data fields (bank_account, tax_id, equipment_preference, emergency_contact, etc.) flow directly into account provisioning, payroll setup, and equipment request workflows running in parallel.

{
  "assigned_to": "{{ $var.customer_user_id }}",
  "form_schema": "form:kyc-standard-v3",
  "title": "Account Verification Required",
  "description": "To comply with financial regulations, we need to verify your identity. Please upload clear photos of your ID and provide the required information. All data is encrypted and processed in accordance with our Privacy Policy. This must be completed within 48 hours to activate your account.",
  "due_at": "{{ $now.AddHours(48) }}",
  "prefill": {
    "full_name": "{{ $var.customer_name }}",
    "email": "{{ $var.customer_email }}"
  }
}

Outcome: Submitted form_data (id_document URL, proof_of_address URL, tax_id, declaration) is passed to the Approval node for compliance officer review. Approval activates the account; rejection sends the customer a notification requesting resubmission with specific corrections.

{
  "assigned_to": "{{ $var.ticket_requester_id }}",
  "form_schema": {
    "fields": [
      {"id": "issue_description", "type": "textarea", "label": "Describe the issue in detail", "required": true, "rows": 5},
      {"id": "first_occurred", "type": "date", "label": "When did this first occur?", "required": true},
      {"id": "affected_system", "type": "select", "label": "Affected system", "required": true,
       "options": ["Laptop/Desktop", "Email", "VPN", "Printer", "Business Application", "Phone", "Other"]},
      {"id": "error_screenshot", "type": "file", "label": "Attach screenshot (optional)", "required": false, "accept": "image/*"},
      {"id": "priority", "type": "select", "label": "Business impact", "required": true,
       "options": ["Low — minor inconvenience", "Medium — work is impacted", "High — cannot work at all"]}
    ]
  },
  "title": "IT Support — Additional Information Required for Ticket #{{ $var.ticket_id }}",
  "description": "Please provide more details about your issue so we can assign it to the right technician and resolve it faster.",
  "due_at": "{{ $now.AddHours(4) }}"
}

Outcome: Submitted form_data populates the ticket record with detailed diagnostics. The priority field is used by a Switch node to route to the appropriate SLA queue (P1 < 1hr, P2 < 4hr, P3 < 24hr). The screenshot URL is attached to the ticket for the technician.

{
  "assigned_to": "{{ $var.supplier_contact_user_id }}",
  "form_schema": "form:supplier-registration-v2",
  "title": "Supplier Registration — {{ $var.company_name }}",
  "description": "Thank you for your interest in becoming a registered supplier with {{ $var.buyer_company }}. Please complete all sections of this registration form. You will need your company registration number, bank account details, and insurance certificates. Submission typically takes 20–30 minutes.",
  "due_at": "{{ $now.AddDays(7) }}",
  "prefill": {
    "company_name": "{{ $var.company_name }}",
    "contact_name": "{{ $var.contact_name }}",
    "contact_email": "{{ $var.contact_email }}"
  }
}

Outcome: Submitted data (company_registration, vat_number, bank_details, insurance_expiry, certifications) flows into: (1) ERP vendor master creation node, (2) Approval node for procurement team review, and (3) a notification to the internal supplier manager confirming registration receipt.

{
  "assigned_to": "{{ $var.employee_id }}",
  "form_schema": "form:performance-self-assessment-v1",
  "title": "{{ $var.review_year }} Annual Performance Self-Assessment",
  "description": "Please reflect on your achievements, challenges, and development goals for {{ $var.review_year }}. Be specific and provide examples where possible. Your self-assessment will be reviewed alongside your manager's evaluation. Deadline: {{ $var.review_deadline_display }}.",
  "due_at": "{{ $var.review_deadline_iso }}",
  "prefill": {
    "employee_name": "{{ $var.employee_name }}",
    "role_title": "{{ $var.role_title }}",
    "department": "{{ $var.department }}",
    "review_period": "{{ $var.review_year }}"
  }
}

Outcome: Both the employee self-assessment and manager review form_data outputs are collected by a Parallel Join node. The joined data is passed to an AI Summarise node that generates a consolidated performance summary, which is then routed to HR for final sign-off.