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 "Delete Contact" operation in the Teamleader node allows users to remove a specific contact from their Teamleader account by specifying the contact's unique ID. This is useful for maintaining an up-to-date contact list, removing obsolete or incorrect entries, and automating cleanup processes within CRM workflows.
Typical scenarios include:
- Automatically deleting contacts that unsubscribe or opt out.
- Removing duplicate or test contacts after data import.
- Cleaning contacts as part of a larger workflow triggered by external events.
Example: A workflow could trigger when a contact is marked inactive in another system, then use this node operation to delete that contact from Teamleader automatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the contact to delete. This is required to specify which contact will be removed. |
Output
The output JSON contains the response data returned by the Teamleader API after attempting to delete the contact. Typically, this will confirm the deletion or provide relevant status information. If no data is returned but the request was successful, a message indicating this is included.
The node does not output binary data.
Dependencies
- Requires an active OAuth2 API credential configured for Teamleader with appropriate permissions to delete contacts.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euwith the operation path set to"contacts.delete".
Troubleshooting
Common issues:
- Providing an invalid or non-existent contact ID will likely result in an error from the API.
- Insufficient permissions on the API credential can cause authorization errors.
- Network or connectivity issues may prevent the API call from succeeding.
Error messages:
"No data got returned": Indicates the API response did not contain expected data; verify the contact ID and API availability.- API errors related to authentication or authorization suggest checking the OAuth2 credentials and scopes.
- Other errors are passed through and should be reviewed for details on the failure cause.
Links and References
- Teamleader API Documentation - Official documentation for all API endpoints and operations.