Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node interacts with the Scoro API to perform various operations on different resources, including invoices. Specifically, for the Invoice resource, it supports a "Delete" operation that allows users to delete an existing invoice by specifying its ID. This is useful in scenarios where invoices need to be removed from the system due to errors, cancellations, or data cleanup.
Practical example: A user automates their billing workflow and wants to remove invoices that were created by mistake or are no longer valid. By using this node's Delete operation on the Invoice resource, they can programmatically delete those invoices based on their IDs.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The ID of the invoice to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any relevant response from the Scoro API indicating success or failure. The output does not include binary data.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API key credential and company account ID configured in n8n credentials for authentication.
- The base URL for the Scoro API must be set in the credentials.
Troubleshooting
Common issues:
- Invalid or missing Invoice ID: The node requires a valid invoice ID to delete; ensure the ID exists and is correctly provided.
- Authentication errors: Verify that the API key and company account ID are correct and have sufficient permissions.
- Network or API endpoint issues: Confirm the base URL is correct and the Scoro API is reachable.
Error messages:
"Operation 'delete' for resource 'invoice' is not supported."— This indicates a misconfiguration or unsupported operation; verify the resource and operation names.- API errors returned from Scoro (e.g., 404 Not Found if the invoice ID does not exist) should be checked and handled accordingly.
Links and References
- Scoro API Documentation (for detailed API endpoints and usage)
- n8n documentation on creating custom nodes