Actions8
- Customer Actions
- Lawsuit Actions
- Task Actions
- Movement Actions
Overview
This node integrates with the ADVBOX API to manage and retrieve data related to various resources such as customers, lawsuits, tasks, movements, and settings. Specifically, for the Customer resource with the Get by id operation, it fetches detailed information about a single customer using their unique Customer ID.
Common scenarios where this node is beneficial include:
- Retrieving customer details for CRM or support workflows.
- Enriching customer records in automation pipelines.
- Fetching specific customer data to trigger downstream processes based on customer attributes.
For example, you might use this node to get a customer's full profile by their ID before sending them a personalized email or updating their record in another system.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the customer object retrieved from the ADVBOX API. The structure typically includes all available customer fields as returned by the API, such as name, phone, identification, birthdate, and other relevant customer details.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ADVBOX API.
- The node expects the ADVBOX API base URL and token to be configured in the credentials.
- Network access to the ADVBOX API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Customer ID will cause the request to fail.
- Incorrect or expired API token will result in authentication errors.
- Network connectivity problems can cause request timeouts or failures.
Error messages:
- Errors from the API (e.g., "Customer not found") are propagated and can be seen in the node's error output.
- Authentication errors indicate issues with the API token; verify and update credentials accordingly.
- If the node throws a generic request error, check network connectivity and API availability.
Links and References
- ADVBOX API Documentation (example link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls in n8n nodes