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 Tasks resource with the List operation, it retrieves a list of tasks from the Teamleader system. This is useful for workflows that need to fetch and process task data, such as project management automation, reporting, or syncing tasks with other systems.
For example, you might use this node to:
- Retrieve all open tasks assigned to a user.
- Fetch tasks due within a certain timeframe.
- Aggregate task data for dashboard visualization.
The node supports pagination and allows limiting the number of results returned.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of task results to return. This controls how many tasks are fetched per execution. Default is 50. |
Output
The node outputs an array of JSON objects representing tasks retrieved from Teamleader. Each object corresponds to a single task and contains the fields as provided by the Teamleader API under the data property of the response.
- If multiple tasks are returned, each task is an element in the output array.
- If only one task is returned, it is output as a single object in the array.
- If no data is returned but the request was successful, the output will contain an object with a message indicating no data was returned.
- Errors during the API call result in error messages unless the node is configured to continue on failure.
The node does not output binary data.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader authentication.
- Makes HTTP POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The node expects the OAuth2 token to be valid and authorized to access the requested resource.
Troubleshooting
- No data returned but request was successful: This means the API call succeeded but returned no tasks. Check if the query parameters (like filters) are correct or if there are actually tasks available.
- No data got returned: Indicates the API response did not include expected data. Verify API credentials and permissions.
- API errors: If the API returns an error (e.g., invalid token, rate limits), the node throws an error unless "Continue On Fail" is enabled.
- Ensure the OAuth2 credentials are correctly set up and tested before running the node.
- The limit parameter should be a positive integer; setting it too high may cause performance issues or API throttling.