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 such as users, teams, tickets, deals, companies, and more. Specifically, for the Teams - List operation, it retrieves a list of all teams from the Teamleader system.
This node is useful in scenarios where you want to automate workflows involving team management data, such as syncing team information with other systems, generating reports, or triggering actions based on team data changes.
Example use case:
- Automatically fetch all teams in your organization to update an internal directory or dashboard.
- Use the list of teams to assign tasks or tickets dynamically based on team availability or structure.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of results to return when listing teams. Defaults to 50. |
Output
The output is a JSON array containing the list of teams retrieved from the Teamleader API. Each item in the array represents a team object with its associated properties as returned by the API.
No binary data is output by this node.
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 OAuth2 token. - The node expects the API to respond with a JSON payload containing a
datafield with the requested information.
Troubleshooting
- No data returned but request was successful: This message indicates that the API call succeeded but no team data was returned. Verify that there are teams available in the Teamleader account.
- No data got returned: This error occurs if the API response does not contain the expected
datafield. Check API credentials and permissions. - API errors: If the API returns an error (e.g., authentication failure, rate limiting), the node will throw an error unless "Continue On Fail" is enabled, in which case the error message is included in the output.
- Ensure the OAuth2 credentials are valid and have access to the Teams resource.
- Confirm the limit parameter is set appropriately; very high values might cause performance issues or API limits.