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 list projects. It fetches a list of projects from the Teamleader system, allowing users to retrieve project data in bulk or limited quantities. This is useful for workflows that need to synchronize project information, generate reports, or trigger actions based on project data.
Common scenarios include:
- Automatically retrieving all active projects for reporting or dashboarding.
- Fetching a limited number of recent projects for review or processing.
- Integrating project data into other systems or automations.
Example: A user wants to get the latest 50 projects created in Teamleader to update their internal project management tool.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of project results to return. Controls how many projects are fetched per call. |
Output
The node outputs an array of JSON objects representing projects retrieved from Teamleader. Each object corresponds to a single project and contains its details as provided by the Teamleader API.
- The output field
jsoncontains the project data. - If multiple projects are returned, each project is an element in the output array.
- No binary data is output by this node.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node makes POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The operation uses the OAuth2 token to authenticate API calls.
Troubleshooting
- No data returned but request was successful: This message indicates the API call succeeded but no project data was returned. Check if there are any projects available or adjust the query parameters.
- No data got returned: An error thrown when the API response does not contain expected data. Verify API credentials and permissions.
- API errors: If the API returns errors (e.g., authentication failure, rate limits), the node will throw an error unless "Continue On Fail" is enabled, in which case it logs the error message in the output.
- Ensure the "Limit" property is set to a reasonable number to avoid large payloads or timeouts.