Actions14
- Customer Actions
- Lawsuit Actions
- Task Actions
- Movement Actions
- Transaction Actions
Overview
This node integrates with the Advbox API to manage various resources such as customers, lawsuits, tasks, movements, settings, and transactions. Specifically for the Customer resource with the Get by id operation, it retrieves detailed information about a single customer using their unique ID.
Common scenarios where this node is beneficial include:
- Fetching customer details for CRM or support workflows.
- Integrating customer data retrieval into automated processes.
- Using customer information to trigger other actions or enrich datasets.
Practical example:
- You have a workflow that receives a customer ID from another system and needs to fetch the full customer profile from Advbox to process orders or send personalized communications.
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 customer details stored in Advbox, such as name, contact information, identification numbers, birthdate, occupation, address, notes, and any other fields maintained by the API.
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.
- The node uses HTTP requests to communicate with the Advbox REST API endpoints.
Troubleshooting
- Missing or invalid API token: The node will throw an error if the API token is not provided or invalid. Ensure your credentials are correctly set up with a valid token.
- Invalid Customer ID: If the provided customer ID does not exist or is malformed, the API may return an error or empty response. Verify the ID before running the node.
- Network or API errors: Temporary network issues or Advbox API downtime can cause request failures. The node logs errors and retries some internal calls but user-triggered requests depend on stable connectivity.
- Permission issues: The API token must have sufficient permissions to access customer data; otherwise, authorization errors will occur.
Links and References
- Advbox API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics
- General info on n8n Credentials
If you need summaries for other operations or resources, please provide their names.