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
The "Link to company" operation under the Contacts resource in this node allows you to associate a contact with a specific company within the Teamleader system. This is useful for managing relationships between contacts and companies, such as linking a sales lead or client contact to their respective organization.
Common scenarios include:
- Associating a new or existing contact with a company to maintain accurate CRM data.
- Updating the relationship details like the contact's position or decision-making status within the linked company.
- Organizing contacts by their companies for better segmentation and communication.
For example, you might use this operation to link a newly added contact to a company they work for, specifying their job title and whether they are a decision maker, which can help sales teams prioritize outreach.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company to which the contact will be linked. (Required) |
| Position | The job position or role of the contact within the linked company. (Optional) |
| Decision Maker | A boolean flag indicating if the contact is a decision maker at the company. (Optional) |
| ID | The unique identifier of the contact to operate on. (Required) |
Output
The output of this operation is a JSON object representing the result of the API call to link the contact to the company. It typically contains the updated contact information including the new company linkage details.
- The
jsonoutput field includes the response data from the Teamleader API after linking the contact. - No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Teamleader API using OAuth2 authentication.
- The node depends on having valid API credentials configured in n8n to authenticate requests.
- The base URL for API requests is
https://api.focus.teamleader.eu. - The operation uses HTTP POST requests to perform the linking action.
Troubleshooting
- Missing or invalid Company ID or Contact ID: Ensure that both IDs are provided and correctly correspond to existing entities in Teamleader.
- API Authentication Errors: Verify that the OAuth2 credentials are valid and have not expired.
- No data returned but request was successful: This may indicate that the API accepted the request but did not return any content; check if the contact was linked successfully in the Teamleader UI.
- Error messages from the API: These will be surfaced as node errors. Common issues include permission problems or invalid parameters. Review the error message and confirm all required fields are correct.
Links and References
- Teamleader API Documentation - Official documentation for understanding API endpoints and payloads.