n8n payload example

n8n form payload example

A practical example of the structured payload a workflow-ready FormNode form can send to an n8n webhook.

Direct answer

An n8n form payload should include stable field keys, readable labels, selected source-system IDs, submission metadata, organization or tenant context, and an idempotency key. n8n should act on IDs and context, not on display labels alone.

Example final submission payload
{
  "submissionId": "sub_01JZ8P9Q4S0R8W7K6M5N4B3A2C",
  "formId": "frm_user_onboarding",
  "idempotencyKey": "sub_01JZ8P9Q4S0R8W7K6M5N4B3A2C",
  "organization": {
    "id": "org_acme",
    "name": "Acme Manufacturing",
    "mappings": {
      "connectwiseCompanyId": "250",
      "cippTenantId": "acme.onmicrosoft.com"
    }
  },
  "fields": {
    "employee_first_name": { "value": "Jordan" },
    "employee_last_name": { "value": "Lee" },
    "license_sku": {
      "value": "SPB",
      "label": "Microsoft 365 Business Premium"
    },
    "copy_from_user": {
      "value": "9f7c6b2a-1b33-4ed8-8db2-6f05d20b3f34",
      "label": "Taylor Nguyen"
    }
  }
}
Notes
  • Use stable field keys such as employee_first_name instead of labels such as Employee First Name.
  • Preserve source-system IDs for dropdown values so n8n can call Microsoft 365, CIPP, ConnectWise, or the PSA reliably.
  • Include organization mappings when the same form can be used across multiple customers.
  • Use the submission ID or a generated idempotency key to prevent duplicate provisioning after retries.
Common questions

What should an n8n form payload include?

It should include stable field keys, selected values, readable labels, organization context, submission metadata, and an idempotency key when retries are possible.

Should n8n use form labels or IDs?

n8n should use stable IDs and field keys for automation. Labels are useful for ticket descriptions, logs, and human review.

Related pages