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
The "Lose" operation on the "Deals" resource in this Teamleader node marks a specific deal as lost. This is useful in sales and CRM workflows where deals progress through various stages, and some deals do not close successfully. By marking a deal as lost, users can keep their sales pipeline accurate and trigger follow-up actions such as notifications or reporting.
Common scenarios:
- Automatically updating deal status when a sales opportunity is no longer viable.
- Integrating with other systems to reflect lost deals for analytics or customer communication.
- Triggering internal workflows like sending feedback requests or reallocating resources.
Example:
You have a list of active deals in your CRM. When a sales representative determines that a deal will not be won, you use this node operation to mark that deal as lost by providing its ID. This updates the deal status in Teamleader accordingly.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the deal to mark as lost. This property is required. |
Output
The node outputs JSON data representing the response from the Teamleader API after marking the deal as lost. The structure typically contains details about the updated deal status or confirmation of the operation.
- The output is an array of JSON objects.
- Each object corresponds to the API response for the processed deal.
- No binary data output is involved.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node communicates with the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The operation uses HTTP POST requests authenticated via OAuth2 Bearer tokens.
Troubleshooting
- No data returned but request was successful: This may indicate the API call succeeded but did not return expected data. Verify the deal ID is correct and the deal exists.
- No data got returned: The API response lacks the expected data field. Check API permissions and if the deal ID is valid.
- Error messages from API: Could be due to invalid or missing deal ID, expired credentials, or insufficient permissions. Ensure the provided deal ID is correct and the OAuth2 token is valid.
- Continue on fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.
Links and References
- Teamleader API Documentation
- Teamleader Deals API Reference (general reference; specific endpoints for losing deals)