Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
Overview
This node integrates with the Teamleader API to perform various operations on different resources. Specifically, for the Products resource with the Delete operation, it allows users to delete a product by specifying its ID. This is useful in scenarios where you need to programmatically remove obsolete or incorrect product entries from your Teamleader account.
Practical examples include:
- Automating cleanup of discontinued products.
- Removing test or placeholder products after import.
- Integrating product lifecycle management workflows where products are deleted based on certain triggers.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the product to delete. This is required to specify which product should be removed. |
Output
The node outputs a JSON array containing the response data from the Teamleader API after attempting the deletion. Typically, this will include confirmation of the deletion or relevant status information. If the API returns no data but the request was successful, the output will contain a message indicating that no data was returned.
No binary data output is involved in this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to delete products.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the path corresponding to the operation (in this case,"products.delete"). - Proper API authentication and authorization are necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent product ID will likely result in an error from the API.
- Insufficient permissions in the API credentials can cause authorization errors.
- Network or connectivity issues may prevent the API call from succeeding.
Error messages:
"No data got returned": Indicates the API response did not include expected data; verify the product ID and API status.- API errors related to authentication or authorization suggest checking the OAuth2 credentials and their scopes.
- General request failures will throw errors captured by the node; enabling "Continue On Fail" can help handle these gracefully.
Links and References
- Teamleader API Documentation – Official documentation for all available endpoints and operations.