Zendesk

Choose Create Zendesk Ticket under Actions → Support & Tickets. Enter your Zendesk subdomain, an agent email address, and an API token. Map the requester email/name and configure subject, description, priority, optional tags, and custom ticket fields.

Custom field JSON maps numeric Zendesk field IDs to values:

{"12345":"[CATEGORY]","23456":false}

The action creates a public initial comment on behalf of the requester. Zendesk's notification rules determine which emails it sends. Core Forms does not change those rules or disable an existing auto-responder.

Optional attachments must come from selected file-upload fields in a saved submission. The adapter checks the form's file controls, the canonical upload directory, and an exact match to the selected file descriptor in the saved submission. It does not download arbitrary URLs or read arbitrary local paths. Limits are 10 MB per file, 20 MB total, and 20 files. Files that were moved/deleted or belong to a renamed form directory require review before retrying.

Each ticket receives a deterministic external reference. Before creating it, the action looks for that reference so a later retry can recover a ticket that was already accepted. Multiple matching tickets fail for review. Completed upload/ticket steps are checkpointed; upload tokens are renewed on a later date. As with any API without an atomic create-idempotency guarantee, inspect Zendesk after an ambiguous timeout.

The action result includes the ticket ID and an agent link. A created ticket is not proof that Zendesk delivered its notification email.

References: Tickets API, attachment uploads.