BackOffice ERP icon

BackOffice ERP

BackOffice ERP API with Google-style smart search. IMPORTANT FOR AI: Use customer/project names instead of IDs (e.g., "VIGACA" not customer ID 123). Supports AI auto-fill from conversation context. Handles case-insensitive search across all business entities.

Tickets → Update

AI-generated

Summary

Update an existing support ticket by specifying its Ticket Id and new ticket details such as subject, department, contact, user, priority, and optionally project association, message, service, assignment, and tags.

Inputs

  • Ticket Id (required) — Specify the exact Ticket Id or use a name, email, or keyword to perform a smart search to identify the ticket to update.
  • Subject (required) — Set the new subject or name of the ticket.
  • Department (required) — Set the ticket's department.
  • Contactid (required) — Specify the contact associated with the ticket; supports smart search by name, email, or keyword instead of numeric ID.
  • Userid (required) — Specify the user associated with the ticket; supports smart search by name, email, or keyword instead of numeric ID.
  • Priority (required) — Set the ticket priority.
  • Project id — Optionally specify the associated project; supports smart search by name, email, or keyword instead of numeric ID.
  • Message — Optionally provide a message for the ticket.
  • Service — Optionally specify a service linked to the ticket.
  • Assigned — Optionally assign the ticket to a user.
  • Tags — Optionally set tags for the ticket.

Output shape

a single JSON object representing the updated ticket record or an object indicating multiple matches if smart search results in ambiguous ticket identification.

If the Ticket Id input uses a name or keyword instead of an exact ID, the node attempts smart search; if multiple tickets match, the output indicates multiple matches for the user to refine the search. The update requires JSON payload fields as per the provided inputs. Errors due to missing fields or ambiguous matches are returned unless 'Continue On Fail' is enabled.

Examples

Example 1: Update ticket by exact ID

Set 'Ticket Id' to the exact ID number and provide required fields such as Subject, Department, Contactid, Userid, and Priority. Optionally update project, message, service, assigned, and tags.

Discussion