WhatMaster icon

WhatMaster

Integração com a API WhatMaster para envio de mensagens

Overview

This node integrates with the WhatMaster API to update ticket information in a WhatsApp-based support or messaging system. Specifically, the "Atualizar Informações do Ticket" (Update Ticket Information) operation allows users to modify details of an existing support ticket identified by its ID.

Typical use cases include:

  • Updating the status or metadata of a customer support ticket after receiving new information.
  • Synchronizing ticket data between WhatsApp conversations and external CRM or helpdesk systems.
  • Automating ticket updates based on workflow triggers in n8n.

For example, when a customer sends a message via WhatsApp, this node can update the corresponding ticket's information automatically, ensuring that the support team has the latest context.

Properties

Name Meaning
Número do WhatsApp The WhatsApp number in international format (e.g., 5511999999999). Required.
External Key An optional external key for correlating messages or tickets with external systems.
ID do Ticket The unique identifier of the ticket to be updated. Required for ticket operations.

Output

The node outputs an array of JSON objects, each representing the response from the WhatMaster API for the executed operation. For the ticket update operation, the JSON typically contains confirmation or details about the updated ticket.

No binary data output is indicated for this operation.

Example output structure (simplified):

{
  "ticketId": "12345",
  "status": "updated",
  "message": "Ticket information updated successfully"
}

Dependencies

  • Requires configuration of WhatMaster API credentials, including:
    • A Bearer token for authorization.
    • An external code identifier used in the API URL path.
  • The node makes HTTP requests to the WhatMaster API endpoint:
    https://back.whatmaster.com.br/v1/api/external/{externalCode}

Troubleshooting

  • Missing Credentials:
    Error: "No credentials found. Please configure the WhatMaster API credentials."
    Resolution: Ensure the API credentials are properly set up in n8n before running the node.

  • Missing Bearer Token or External Code:
    Errors indicating these are required mean the credentials lack necessary fields.
    Resolution: Verify that both the token and external code are provided in the credential configuration.

  • Required Parameters Missing:
    For example, if the WhatsApp number or ticket ID is empty, the node throws errors like:

    • "Número do WhatsApp é obrigatório."
    • "ID do ticket" must be provided for ticket operations.
      Resolution: Provide all required input parameters.
  • Operation Not Implemented:
    The source code shows that ticket operations are not yet implemented (handleTicketOperation throws an error). This means the actual update logic is missing and will cause an error if invoked.
    Resolution: Implementation of ticket operations is needed in the node code to enable this functionality.

Links and References


Note: The current bundled source code does not implement the ticket update operation logic; it throws a "not implemented" error. To use this operation, the node's code must be extended to handle ticket updates properly.

Discussion