Actions198
- Agendamentos e Lembretes Actions
- Campanhas Actions
- Canais e Sessões Actions
- Contatos Actions
- CRM - Pipeline Actions
- Dashboard Actions
- Envio em Lote Actions
- Galeria Actions
- Grupos WhatsApp Actions
- Interativo Baileys Actions
- Interativo Instagram Actions
- Interativo Messenger Actions
- Interativo UazAPI Actions
- Interativo Waba Actions
- Kanban / Tags / Motivos / Filas Actions
- Listagens Actions
- Listagens Utilitárias Actions
- Logs de Chamadas Actions
- Mensagens Actions
- Mensagens Avançadas Actions
- Mensagens em Grupo Actions
- Oportunidades Actions
- Templates WABA Actions
- Tickets Actions
- Tickets - Extras Actions
- To-Do List Actions
- Usuários Actions
Tickets → Create Ticket File
AI-generatedSummary
Upload a file as part of creating a new ticket in the Z-PRO system, optionally including associated metadata such as contact number, initial message, and ticket status.
Inputs
- binaryPropertyName (required) — Name of the n8n binary property containing the file to upload (sent as form-data field "media").
- body — Initial text message of the ticket.
- number — WhatsApp contact number in format 5511999999999.
- externalKey — Unique key from your system to identify the ticket creation request.
- userId — ID of the user creating the ticket.
- status — Initial status of the ticket (pending, open, closed).
- kanbanId — Optional Kanban board ID associated with the ticket.
- chatFlowId — Optional chat flow ID linked to the ticket.
- queueId — Optional queue ID for routing the ticket.
- channelId — Optional channel ID; for webmail, provide the webmail channel ID.
- email — For webmail channel, the contact's email (required if channelId is webmail).
- name — Contact's name for webmail tickets (optional).
- validateNumber — Whether to validate/normalize the number format (default true). If false, uses the number exactly as provided (recommended for WABA).
Output shape
a single record containing the created ticket file data
The operation returns the created ticket file's details from the Z-PRO API. Handling is multipart/form-data including the binary file under the 'media' field. Optional fields customize ticket metadata as supported by the API.
