Overview
The node "CO - Alertrack" integrates with the Clientes Online API, providing several operations to interact with this service. The Login operation allows users to authenticate by requesting specific access scopes. This is useful for scenarios where you need to obtain an authenticated session or token with defined permissions before performing further actions on the platform.
Practical examples include:
- Logging in with limited scopes to restrict access only to certain resources like campaigns or contacts.
- Using broader scopes such as "manager" to gain full access to all resources and permissions.
- Automating workflows that require authentication with specific permissions tailored to the task.
Properties
| Name | Meaning |
|---|---|
| Scopes | The access scopes to include in the login request. Options include: Campaign, Channel, Contact, Correios, Coupon, Department, Edit, Group, Import, Inbox, Manager (full access), Monitor, Notification, Operator, Popup, Portable, Product, Protocol, Remove, Schedule, Send, SMSIDEAL, Tag, Wallet Client, Write. Users select one or multiple scopes to define the permissions granted upon login. |
Output
The node outputs a JSON object representing the result of the login action. This typically includes authentication details such as tokens or session information returned by the Clientes Online API after successful login with the requested scopes.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for the Clientes Online API to authenticate requests.
- The node depends on the external Clientes Online API service being available and accessible.
- Proper configuration of the API credential within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Selecting no scopes or invalid scopes may result in errors or insufficient permissions.
- Network connectivity problems can prevent reaching the Clientes Online API.
Error messages and resolutions:
- Authentication errors: Verify that the API key credential is correctly configured and valid.
- Permission denied or insufficient scope errors: Ensure the required scopes are selected in the node properties.
- Timeout or connection errors: Check network settings and API availability.
Links and References
- Clientes Online API Documentation (Replace with actual URL if available)
- n8n documentation on API Credentials
- General OAuth2 and scope management concepts for API authentication