Teamleader icon

Teamleader

Consume Teamleader API

Actions60

Overview

This node integrates with the Teamleader API to perform various operations on different resources such as users, companies, deals, tickets, contacts, and more. Specifically for the Companies - Info operation, it retrieves detailed information about a single company by its ID.

Common scenarios where this node is beneficial include:

  • Fetching company details to enrich CRM data.
  • Automating workflows that require company-specific information.
  • Integrating company data into other systems or reports.

For example, you might use this node to get the full profile of a company before creating a deal or sending a personalized email.

Properties

Name Meaning
ID The unique identifier of the company to retrieve information for. This is required to specify which company's details to fetch.

Output

The node outputs JSON data representing the detailed information of the requested company. The structure corresponds to the company object returned by the Teamleader API and typically includes fields such as company name, business type, VAT number, emails, addresses, telephones, website, IBAN, BIC, language, remarks, tags, marketing consent, preferred currency, and other relevant company details.

No binary data output is produced by this operation.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate requests against the Teamleader API.
  • The node makes HTTP POST requests to the Teamleader API endpoint https://api.focus.teamleader.eu with the specific operation path (e.g., companies.info).
  • Proper API permissions are needed to access company information.

Troubleshooting

  • No data returned but request was successful: This message indicates the API call succeeded but no company data was found or returned. Verify the provided company ID is correct.
  • No data got returned: This error occurs if the API response does not contain expected data. Check if the company ID exists and the API credentials have sufficient permissions.
  • API authentication errors: Ensure the OAuth2 credentials are valid and properly set up in n8n.
  • Invalid or missing ID parameter: The company ID is required; ensure it is provided and correctly formatted.

Links and References

Discussion