Actions103
- Calendar Actions
- Common Data Actions
- Contacts Actions
- Contracts Actions
- Credit Notes Actions
- Customers Actions
- Custom Fields Actions
- Estimates Actions
- Expenses Actions
- Invoices Actions
- Items Actions
- API Keys Actions
- Leads Actions
- Milestones Actions
- Payments Actions
- Projects Actions
- Property Actions
- Proposals Actions
- Staff Actions
- Subscriptions Actions
- Tasks Actions
- Tickets Actions
- Timesheets Actions
Tickets → Create
AI-generatedSummary
Create a new support ticket in the BackOffice ERP system by specifying details such as subject, department, contact, user, and optionally project, message, service, assignment, CC, priority, and tags.
Inputs
- Subject (required) — Ticket name.
- Department (required) — Ticket Department.
- Contactid (required) — Ticket Contact. Supports smart search—enter name, email, or keyword instead of numeric ID.
- Userid (required) — Ticket user. Supports smart search—enter name, email, or keyword instead of numeric ID.
- Project id — Ticket Project. Supports smart search—enter name, email, or keyword instead of numeric ID.
- Message — Ticket message.
- Service — Ticket Service.
- Assigned — Assign ticket to a user or team.
- Cc — Ticket CC recipients.
- Priority — Ticket priority level.
- Tags — Ticket tags for categorization.
Output shape
a single JSON object representing the created ticket.
If a smart search field (like Contactid or Userid) is ambiguous, multiple matches are returned requiring precise input. On success, the output includes the created ticket data returned by the BackOffice ERP API. Errors or multiple match prompts are returned as JSON messages with appropriate indicators.
Examples
Example 1: Create a new ticket with mandatory fields subject, department, contact, and user, optionally including message and priority.
Subject="Issue with login", Department="Technical Support", Contactid="john.doe@example.com", Userid="agent1", Message="Cannot login to the portal.", Priority="High"