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 Contacts resource with the List operation, it retrieves a list of contacts from the Teamleader system. This is useful in scenarios where you want to fetch and process contact data for CRM purposes, marketing campaigns, or synchronization with other systems.
For example, you might use this node to:
- Retrieve all contacts to export them to another database.
- Fetch contacts to send personalized emails.
- Synchronize contact lists between Teamleader and other tools.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of results to return when listing contacts. Defaults to 50. |
Output
The node outputs an array of JSON objects representing contacts retrieved from Teamleader. Each object corresponds to a contact and contains its details as provided by the Teamleader API.
- The output field
jsoncontains the contact data. - If multiple contacts are returned, each contact is an element in the output array.
- No binary data output is involved in this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader to authenticate requests.
- The node makes HTTP POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The API call uses the
/contacts.listoperation internally (inferred from the operation parameter).
Troubleshooting
- No data returned but request was successful: This message indicates that the API call succeeded but no contacts were found or returned. Verify that there are contacts in your Teamleader account.
- No data got returned: This error occurs if the response does not contain expected data. Check API credentials and permissions.
- API errors: If the API returns an error (e.g., authentication failure, rate limits), 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 sufficient permissions to access contacts.
- The
Limitproperty should be set to a reasonable number to avoid large payloads or timeouts.
Links and References
- Teamleader API Documentation
- Teamleader Contacts API Reference (general reference; specific endpoints may vary)