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 retrieve a list of business types. It is useful when you want to fetch and work with different categories or classifications of businesses defined in your Teamleader account. For example, you might use this node to populate dropdowns in workflows, filter companies by their business type, or synchronize business type data with other systems.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of results to return (default 50) |
The "Limit" property controls how many business type records are fetched from the API in one request.
Output
The node outputs an array of JSON objects representing business types. Each object corresponds to a single business type as returned by the Teamleader API. The exact fields depend on the API response but typically include identifiers and descriptive information about each business type.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential for Teamleader with appropriate permissions.
- Makes POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The node expects the API to respond with a JSON body containing a
datafield with the list of business types.
Troubleshooting
- No data returned but request was successful: This message indicates that the API call succeeded but returned no business types. Verify that your Teamleader account has business types defined.
- No data got returned: An error thrown if the API response does not contain expected data. Check API credentials and network connectivity.
- API errors: If the API returns an error, it will be surfaced by the node. Common causes include invalid credentials, insufficient permissions, or incorrect API endpoint usage.
- To handle intermittent failures, enable "Continue On Fail" in the node settings to allow workflow execution to proceed despite errors.