Reference
A concise technical reference for the workflow action output and trigger payload.
Workflow Action Output
| Property | Description |
|---|---|
success | Whether the form was generated successfully |
form_url | The secure public form link |
form_id | Identifier for the generated form |
form_reference | The business-purpose reference set on the action |
object_key | The selected object |
record_id | Can be null when a form is generated in creation mode |
expires_at | When the generated link expires |
Form Submitted Trigger
| Property | Description |
|---|---|
object_key | The object the form was configured for |
record_id | The CRM record that was updated or created |
contactId | On a Contact form, the same value as record_id. On any other object, the Contact from the workflow context that generated the form, if one was present – otherwise omitted |
form_id | Identifier for the generated form |
form_reference | The business-purpose reference set on the action |
submitted_at | When the submission was saved |
created | See below |
changed_fields | Array of the fields actually written back on this submission |
opportunity_signature_url | Opportunity submissions only – the URL of the first Signature-type field that's been signed, or null if the object isn't Opportunity, has no Signature field, or none has been signed yet. Only the first Signature field is ever included if the object has more than one. |
created = true means this submission created the CRM record. created = false means this submission updated an existing or previously created record. See Form Submission Trigger for when the trigger fires.
Supported Objects
- Contact
- Business
- Opportunity
- Any HighLevel Custom Object
Every Custom Object type is supported – there is no allow-list of specific Custom Objects. Individual field types within any object can still be unsupported; unsupported field types are omitted from the form rather than guessed at.
Submission Behaviour
- Successful saves fire the Form Submitted trigger
- Zero-change successful submissions still fire the trigger
- Multiple submissions can be enabled or disabled
- Single-submit forms reject later submissions
- Changed fields are updated individually
- If the record changed after the form was opened, submission is blocked (not silently overwritten or merged) – see Troubleshooting