SacNews - Relacionamento icon

SacNews - Relacionamento

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

Actions59

Overview

The node "SacNews - Relacionamento" integrates with a customer relationship platform via WhatsApp, enabling various operations related to contacts, protocols, messages, groups, marketing campaigns, and more. Specifically, the operation "Contato - Listar Protocolos" (Contact - List Protocols) retrieves the list of protocols associated with a given contact ID, supporting pagination.

This node is beneficial in scenarios where users need to programmatically access communication or service protocols linked to specific contacts within the SacNews platform. For example, a support team could use this node to fetch all open or historical protocols for a customer to review their case history before responding.

Properties

Name Meaning
ID Do Contato The unique identifier of the contact whose associated protocols you want to retrieve.
Página The page number for paginated results; minimum value is 1. Controls which subset of data is returned.

Output

The node outputs JSON data containing the list of protocols associated with the specified contact. Each item in the output array represents a protocol record with its details as provided by the SacNews platform API.

If the node supports binary data output in other operations, it is not relevant here since this operation deals with listing protocol metadata only.

Dependencies

  • Requires an API key credential for authenticating with the SacNews platform.
  • The node depends on internal action methods that handle API requests to the SacNews service.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid contact ID: Ensure the "ID Do Contato" property is correctly set and corresponds to an existing contact in the platform.
  • Pagination errors: The "Página" parameter must be a positive integer starting at 1. Providing invalid values may cause errors or empty results.
  • Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
  • API rate limits or connectivity issues: Network problems or API throttling can cause request failures; check network status and API usage quotas.
  • Unexpected empty results: Confirm that the contact actually has associated protocols; otherwise, the response will be empty.

Links and References

Discussion