Relacio - WhatsApp icon

Relacio - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - Relacio

Actions58

Overview

This node integrates with a customer relationship platform via WhatsApp, enabling various operations related to contacts, protocols, messages, groups, and more. Specifically, the "Protocolo - Observações - Adicionar" operation allows users to add an observation (note) to an existing protocol by specifying the protocol number and the observation text.

Common scenarios for this node include:

  • Adding internal notes or comments to support tickets or service protocols.
  • Enhancing protocol records with additional information during customer service workflows.
  • Automating updates to protocol observations based on external triggers or data flows.

Example: A customer support team can use this node to automatically append follow-up remarks to a protocol after a call or chat interaction, ensuring all relevant details are logged in the system.

Properties

Name Meaning
Protocolo The protocol number to which the observation will be added.
Observação The observation text to be added to the specified protocol.

Output

The node outputs JSON data representing the result of the add observation action. This typically includes confirmation of the observation being added, possibly with updated protocol details or status. The exact structure depends on the API response but generally confirms success or failure of the operation.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the external customer relationship platform.
  • The node depends on the platform's API endpoints to perform actions such as adding observations to protocols.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing protocol number: Ensure the "Protocolo" property is correctly set to an existing protocol identifier.
    • Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
    • Network or API errors: Check connectivity and API availability.
  • Error Messages:

    • Errors related to invalid protocol numbers usually indicate the specified protocol does not exist or is inaccessible.
    • Authentication errors suggest issues with the provided API key or credential setup.
    • Timeout or connection errors may require retrying or checking network settings.

Resolving these typically involves verifying input values, credential correctness, and network/API status.

Links and References

  • No direct external links were found in the source code. For further details, consult the documentation of the integrated customer relationship platform or its API reference.

Discussion