Overview
This node integrates with the Clientes Online API (referred to as "Alertrack") and provides three main operations: user login, fetching all contacts, and retrieving a specific contact's profile. The operation "Buscar Perfil Contato" (Search Contact Profile) allows users to obtain detailed information about a single contact by specifying its ID.
Common scenarios for this node include:
- Authenticating with the Clientes Online system to gain access to protected resources.
- Retrieving a list of all contacts for further processing or analysis.
- Fetching detailed profile information of a particular contact, useful for customer support, marketing personalization, or data synchronization tasks.
For example, a marketing automation workflow might use the "Buscar Perfil Contato" operation to pull up a contact’s profile before sending a personalized campaign message.
Properties
| Name | Meaning |
|---|---|
| Operation | Choose the action to perform: - Login - Buscar Todos Contatos (Get All Contacts) - Buscar Perfil Contato (Get Contact Profile) |
| Scopes | (Only for Login) Select one or more permission scopes to request during login, such as access to campaigns, contacts, notifications, etc. |
| Page | (Only for Get All Contacts) Specify the page number to retrieve when fetching contacts. |
| ID | (Only for Buscar Perfil Contato) The numeric ID of the contact whose profile you want to retrieve. |
Output
The node outputs an array containing JSON objects representing the result of the selected operation:
For Buscar Perfil Contato, the output JSON contains the detailed profile data of the specified contact. This typically includes fields like name, contact details, status, and other relevant attributes as provided by the Clientes Online API.
For Login and Buscar Todos Contatos, the output JSON corresponds respectively to authentication results or lists of contacts.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Clientes Online API.
- The node depends on the Clientes Online API being accessible and properly configured with the necessary permissions/scopes.
- No additional external services are required beyond the API itself.
Troubleshooting
- Invalid or missing API credentials: Ensure that the API key or authentication token is correctly set up in n8n credentials for this node.
- Permission errors: If the requested scopes during login do not include access to contacts or profiles, the API may reject requests. Verify that appropriate scopes are selected.
- Invalid contact ID: Providing a non-existent or incorrect contact ID will likely result in an error or empty response. Double-check the ID value.
- Network or API downtime: Connectivity issues or API service interruptions can cause failures; verify network access and API status.
- Unexpected response format: If the API changes its response structure, the node’s output may not match expectations. Review API documentation for updates.
Links and References
- Clientes Online API Documentation (example placeholder link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes