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 Deals resource and the Delete operation, it allows users to delete a deal by specifying its unique ID. This is useful in scenarios where deals are no longer relevant or were created by mistake and need to be removed from the system.
Practical examples include:
- Automatically cleaning up outdated or lost deals.
- Removing test or duplicate deals during data synchronization.
- Managing deal lifecycle by deleting deals that have been cancelled.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the deal to delete. This is a required string input. |
Output
The node outputs a JSON array containing the response data from the Teamleader API after attempting to delete the deal. Typically, this will include confirmation of deletion or any relevant metadata returned by the API.
If the API returns no data but the request was successful, the output will contain an object with a message indicating "No data returned but request was successful".
In case of errors, the output may contain error messages if the node is configured to continue on failure.
The node does not output binary data.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to manage deals.
- The node makes HTTP POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The user must configure the node with valid credentials and ensure the API token has rights to delete deals.
Troubleshooting
Common issues:
- Invalid or missing deal ID: The operation requires a valid deal ID; providing an empty or incorrect ID will cause errors.
- Insufficient permissions: The OAuth2 token must have delete permissions for deals.
- Network or API downtime: Connectivity issues or Teamleader API outages can cause request failures.
Error messages:
"No data got returned": Indicates the API response did not include expected data; verify the deal ID and API status.- API error messages returned by Teamleader (e.g., "Deal not found" or "Unauthorized") should be checked and resolved by verifying inputs and credentials.
Links and References
- Teamleader API Documentation
- n8n OAuth2 Credential Setup Guide (generic reference)