Emvion Venabo icon

Emvion Venabo

Interact with the emvion venabo API

Actions37

Ticket → Create

AI-generated

Summary

Create a Venabo ticket

Inputs

  • subject (required) — Subject of the ticket
  • statusId (required) — Status ID of the ticket
  • priorityId (required) — Priority ID of the ticket
  • comment — Comment for the ticket
  • customerId — Customer ID
  • departmentId — Department ID
  • projectId — Project ID
  • ticketTypeId — Ticket type ID
  • serviceContractId — Service contract ID
  • taskId — Task ID
  • receiptId — Receipt ID
  • monitoringDeviceId — Monitoring device ID
  • monitoringSensorId — Monitoring sensor ID
  • contactPerson — Contact person
  • dueDate — The due date of ticket (format: YYYY-MM-DD)
  • dueTime — The due time of ticket (format: HH:MM:SS)
  • resubmissionDate — The resubmission date of ticket (format: YYYY-MM-DD)
  • resubmissionTime — The resubmission time of ticket (format: HH:MM:SS)
  • internal — Internal flag
  • autoSubscribeContactPerson — Auto subscribe contact person
  • notifyContactPerson — Notify contact person
  • assigneeIds — Comma-separated list of assignee IDs (e.g. '1,2,3')
  • objectIds — Comma-separated list of object IDs (e.g. '1,2,3')
  • tagIds — Comma-separated list of tag IDs (e.g. '1,2,3')
  • checklistPatternIds — Comma-separated list of checklist pattern IDs (e.g. '1,2,3')
  • files — Comma-separated list of file IDs (e.g. '1,2,3')
  • subscribers — JSON array of subscriber objects
  • customFields — Custom fields to add to the ticket
  • requestOptions — Request options including batching (batchSize, batchInterval), allowUnauthorizedCerts, proxy, and timeout

Output shape

Returns the created ticket object from Venabo API

Exact return shape not explicitly declared in properties or source; typical n8n node behavior returns the created resource identifier and metadata

Examples

Example 1: Create a ticket with subject and status

Set subject to 'Urgent issue', statusId to '1', and leave other fields at defaults

Links

Discussion