SacNews - Relacionamento

Overview

This node interacts with a customer service platform focused on managing protocols and their related messages. Specifically, the "Protocolo - Mensagem - Listar" operation retrieves all messages associated with a given service protocol number. This is useful in scenarios where you want to fetch the conversation history or message log tied to a particular customer support ticket or protocol.

Practical examples include:

• Automatically fetching all messages linked to a support ticket for analysis or reporting.
• Integrating message histories into CRM systems to provide agents with full context.
• Triggering workflows based on the content or presence of messages within a protocol.

Properties

Output

The node outputs an array of message objects related to the specified protocol. Each item in the output's json field represents a message associated with that protocol, typically including details such as message content, sender, timestamp, and other metadata relevant to the communication.

If the platform supports binary data (e.g., attachments or media in messages), those would be included accordingly, but this specific operation focuses on listing textual messages.

Dependencies

• Requires an API key credential to authenticate with the external customer service platform.
• The node depends on the platform's API endpoints to retrieve protocol messages.
• Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

• Missing or invalid protocol ID: If the "ID Do Protocolo" property is empty or incorrect, the node will fail to retrieve messages. Ensure the protocol number is valid and provided.
• Authentication errors: If the API key or authentication token is missing or invalid, the node will throw authorization errors. Verify that the API credentials are correctly set up in n8n.
• No messages found: If the protocol exists but has no messages, the output may be an empty array. Confirm that the protocol number corresponds to active conversations.
• API rate limits or downtime: External service issues can cause failures. Check the platform status and consider retry mechanisms if needed.

Links and References

• Refer to the customer service platform's official API documentation for detailed information about protocol and message management endpoints.
• Consult n8n documentation on how to configure API credentials securely.