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 Move operation, it allows users to move a deal to a different phase or stage within their sales pipeline. This is useful in scenarios where deals progress through multiple phases (e.g., prospecting, negotiation, closed won/lost), and you want to update the deal's current phase programmatically.
Practical examples include:
- Automatically moving deals to the next phase after certain triggers or conditions are met.
- Integrating with other systems to synchronize deal stages.
- Bulk updating deal phases based on external events.
Properties
| Name | Meaning |
|---|---|
| Deal Phase ID | The ID of the phase to move the deal to. |
| ID | The ID of the deal to operate on (i.e., the deal that will be moved). |
Output
The output of this node is a JSON array containing the response data from the Teamleader API after moving the deal. The structure typically includes details about the updated deal, reflecting its new phase. If multiple items are processed, each result is included as an element in the output array.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the/deals.moveoperation path. - Proper API authentication token must be provided via n8n credentials.
Troubleshooting
Common issues:
- Invalid or missing Deal ID or Deal Phase ID parameters will cause the API request to fail.
- Insufficient permissions or expired OAuth2 tokens can lead to authentication errors.
- Network connectivity issues may prevent successful API calls.
Error messages:
"No data got returned": Indicates the API responded without expected data; verify the deal and phase IDs are correct.- Authentication errors: Check that the OAuth2 credentials are valid and have not expired.
- API rate limits or quota exceeded: May require waiting or adjusting usage patterns.
To resolve errors, ensure all required parameters are correctly set, credentials are valid, and the target deal and phase exist in Teamleader.
Links and References
- Teamleader API Documentation
- Teamleader Deals API Reference (general reference for deal operations)