Actions13
- Customers Actions
- Documents Actions
- PDF-Templates Actions
- Attachments Actions
- Document-Payments Actions
Overview
This node integrates with the Easybill API to manage various resources such as customers, documents, PDF templates, attachments, and document payments. Specifically, for the Delete Customer operation, it allows users to remove a customer record from Easybill by specifying the customer ID or selecting from a list of existing customers.
Common scenarios where this node is beneficial include:
- Automating cleanup of customer data in Easybill when customers are no longer active.
- Integrating with other workflows that require removing customer records after certain conditions are met (e.g., subscription cancellation).
- Managing customer lifecycle programmatically without manual intervention in the Easybill dashboard.
Example use case:
- A business uses n8n to automate their billing system. When a customer unsubscribes, the workflow triggers this node to delete the corresponding customer from Easybill automatically.
Properties
Name | Meaning |
---|---|
Customer | Select the customer to delete. You can either: - Choose from a searchable list of existing customers. - Provide the customer ID directly (must be numeric). |
Output
The node outputs a JSON array containing the response(s) from the Easybill API after attempting to delete the specified customer(s). The exact structure depends on the API's response but typically includes confirmation of deletion or error details if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an active Easybill API credential configured in n8n to authenticate requests.
- Depends on Easybill's REST API being accessible and the provided credentials having permission to delete customers.
- Utilizes internal helper methods to fetch customer lists for selection and to handle API requests.
Troubleshooting
- Invalid Customer ID: If the customer ID provided is not numeric, the node will reject it due to validation rules. Ensure the ID consists only of digits.
- Customer Not Found: Attempting to delete a non-existent customer may result in an error from the Easybill API. Verify the customer exists before deletion.
- Authentication Errors: If the API key or credentials are invalid or expired, the node will fail to authenticate. Check and update your Easybill credentials in n8n.
- API Rate Limits: Frequent deletions might hit API rate limits imposed by Easybill. Implement retry logic or limit request frequency accordingly.
- Network Issues: Connectivity problems can cause request failures. Ensure stable internet access and Easybill API availability.
Links and References
- Easybill API Documentation — Official API docs for detailed endpoint information.
- n8n Documentation — For general guidance on using and configuring nodes and credentials.