WiizoChat icon

WiizoChat

Integração completa com API Wiizo - Mensagens, contatos, tickets, empresas, tags e agendamentos
Join our community

Actions12

Overview

This node integrates with the Wiizo API to manage various communication and CRM-related tasks such as sending messages, managing contacts, tickets, companies, tags, and scheduling messages. Specifically, the "🎫 Atualizar Ticket" (Update Ticket) operation allows users to update the status, responsible user, or queue of an existing support ticket in the Wiizo system.

Common scenarios for this operation include:

  • Changing the status of a customer support ticket (e.g., from "open" to "closed").
  • Reassigning a ticket to a different support agent.
  • Moving a ticket to another queue for better handling or prioritization.

Practical example:

  • A support automation workflow detects that a ticket has been resolved and uses this node to update the ticket status to "closed" and assign it to a supervisor for review.

Properties

Name Meaning
ID do Ticket The unique numeric identifier of the ticket to be updated.
Novo Status The new status to set for the ticket. Options: "Aberto" (open), "Fechado" (closed), "Pendente" (pending).
Novo Usuário Responsável The numeric ID of the new user responsible for the ticket.
Nova Fila The numeric ID of the new queue to which the ticket should be assigned.

Output

The output is a JSON object representing the response from the Wiizo API after attempting to update the ticket. It typically contains confirmation details about the updated ticket or error information if the update failed.

No binary data output is produced by this operation.

Example structure of the output JSON (based on typical API responses):

{
  "ticketId": 123,
  "status": "closed",
  "userId": 45,
  "queueId": 3,
  "message": "Ticket updated successfully"
}

Dependencies

  • Requires an active connection to the Wiizo API via an API key credential configured in n8n.
  • The node uses HTTP requests authenticated with this credential to communicate with the Wiizo backend.
  • The base URL for the API is obtained from the credential configuration.

Troubleshooting

  • Missing Credentials: If the API credentials are not set or invalid, the node will throw an error indicating credentials were not found. Ensure the API key credential is properly configured.
  • Invalid Ticket ID: Providing a non-existent or incorrect ticket ID may result in an error from the API. Verify the ticket ID before running the node.
  • Invalid User or Queue IDs: Assigning a ticket to a user or queue that does not exist can cause failures. Confirm these IDs are valid within your Wiizo environment.
  • API Errors: Network issues or API downtime can cause request failures. Check connectivity and Wiizo service status.
  • Permission Issues: The API key used must have sufficient permissions to update tickets; otherwise, authorization errors may occur.

Links and References

Discussion