WhatsApp API icon

WhatsApp API

Integração com WhatsApp API para envio de mensagens e gerenciamento
Join our community

Actions20

Overview

This node integrates with a WhatsApp API to perform various communication and management tasks related to WhatsApp messaging, contacts, tickets, sessions, and opportunities. Specifically for the Ticket - Create Notes operation, it allows users to add notes to an existing ticket in the system. This is useful in customer support or helpdesk scenarios where agents need to append additional information or updates to ongoing tickets.

Practical examples include:

  • Adding internal comments or observations to a support ticket.
  • Logging follow-up actions or customer feedback within a ticket.
  • Collaborating among team members by sharing notes on ticket progress.

Properties

Name Meaning
Ticket ID The unique identifier of the ticket to which the note will be added.
User ID The identifier of the user creating the note, typically representing the agent or system.

Output

The node outputs a JSON object containing the response from the WhatsApp API after attempting to create the note on the specified ticket. The structure generally includes details about the created note or confirmation of success. If an error occurs, the output JSON will contain an error field describing the issue.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the WhatsApp API service.
  • The node uses the base URL and instance ID configured in the credentials to construct API requests.
  • The WhatsApp API must support endpoints for ticket note creation at /v2/api/external/{instanceId}/createNotes.

Troubleshooting

  • Common issues:

    • Invalid or missing Ticket ID or User ID parameters can cause request failures.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity problems preventing access to the WhatsApp API endpoint.

  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error property.
    • Typical errors might include "Ticket not found", "Unauthorized", or "Invalid parameters".

  • Resolutions:

    • Verify that the Ticket ID and User ID are correct and correspond to existing records.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network settings and API availability.

Links and References

Discussion