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 "Unlink from company" operation for the Contacts resource in this node allows you to remove the association between a contact and a company within the Teamleader system. This is useful when a contact no longer works with or is related to a specific company, and you want to update your CRM data accordingly.
Common scenarios include:
- Cleaning up outdated or incorrect contact-company relationships.
- Reflecting organizational changes where contacts move between companies or become independent.
- Maintaining accurate CRM records by unlinking contacts from companies they are no longer associated with.
For example, if a contact previously linked to Company A leaves that company, you can use this operation to unlink the contact from Company A without deleting the contact itself.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company from which the contact should be unlinked. |
| ID | The unique identifier of the contact to operate on (i.e., the contact to unlink). |
Output
The output JSON contains the response data returned by the Teamleader API after attempting to unlink the contact from the specified company. Typically, this will confirm the success of the unlinking operation or provide relevant status information.
If the API returns multiple items (unlikely for this operation), they will be output as an array; otherwise, a single object is returned.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Teamleader API using OAuth2 authentication.
- The node expects a valid API token configured via n8n credentials to authorize requests.
- The base URL used for API calls is
https://api.focus.teamleader.eu. - The operation uses HTTP POST requests to perform actions.
Troubleshooting
- Missing or invalid IDs: Ensure both the Contact ID and Company ID are correctly provided and correspond to existing entities in Teamleader.
- API errors: If the API returns an error, it may be due to insufficient permissions, invalid tokens, or network issues. Verify your API credentials and connectivity.
- No data returned: If the API call succeeds but returns no data, the node outputs a message indicating this. Check if the contact was already unlinked or if the IDs are correct.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output.
Links and References
- Teamleader API Documentation - Official documentation for understanding API endpoints and usage.