Actions67
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Ticket Status 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
- Notes Actions
Deals → Move
AI-generatedOverview
This node operation moves a deal to a different phase within the Teamleader CRM system. It is useful for automating the progression of deals through various sales stages, such as moving a deal from 'Negotiation' to 'Closed Won' or 'Closed Lost'. For example, when a deal reaches a certain milestone, this node can update its phase automatically to reflect its current status.
Use Case Examples
- Automatically move a deal to the next phase after a successful client meeting.
- Update the deal phase when a contract is signed to mark it as 'Won'.
- Shift deals to a 'Lost' phase if they are marked as unsuccessful.
Properties
| Name | Meaning |
|---|---|
| Deal Phase ID | The ID of the phase to move the deal to. This is required to specify the target phase for the deal. |
| ID | The ID of the deal to operate on. This identifies which deal will be moved to the new phase. |
Output
JSON
id- The unique identifier of the deal that was moved.phase_id- The ID of the new phase the deal was moved to.otherProperties- Additional properties returned by the API about the deal after moving it.
Dependencies
- Requires an OAuth2 API credential for Teamleader to authenticate requests.
Troubleshooting
- Ensure the deal ID and phase ID are valid and exist in the Teamleader system to avoid errors.
- If the API returns no data, check the API credentials and permissions.
- Handle API errors gracefully by enabling 'Continue On Fail' to avoid workflow interruption.
Links
- Teamleader API Documentation - Official documentation for the Teamleader API, useful for understanding deal phases and API request details.