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 Deal Phases resource with the List operation, it retrieves a list of all deal phases configured in the Teamleader system.
This functionality is useful when you want to fetch and work with the stages or phases that deals go through in your sales pipeline. For example, you might use this node to:
- Display all deal phases in a dashboard.
- Automate workflows based on deal phase changes.
- Synchronize deal phases with other systems.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of results to return. This controls how many deal phases are fetched at once. |
Output
The node outputs an array of JSON objects representing deal phases. Each object corresponds to a single deal phase as returned by the Teamleader API. The exact structure depends on the API response but typically includes identifiers, names, and possibly order or status of each deal phase.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential for authenticating with the Teamleader API.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the/dealPhases.listpath. - Proper configuration of the OAuth2 credentials within n8n is necessary for successful API calls.
Troubleshooting
- No data returned but request was successful: This message indicates the API call succeeded but no deal phases were returned. Verify that deal phases exist in your Teamleader account.
- No data got returned: This error occurs if the API response does not contain expected data. Check API permissions and ensure the OAuth2 token is valid.
- API errors: If the node throws errors related to authentication or request failures, verify the OAuth2 credentials and network connectivity.
- Limit property issues: Setting the limit too high may cause performance issues or API rate limiting. Adjust the limit according to your needs.