Overview
This node allows you to delete a Contact from Intercom by specifying the Contact's unique ID. It is useful in scenarios where you need to automate the removal of contacts (users or leads) from your Intercom workspace, such as cleaning up outdated records, handling GDPR requests, or managing user lifecycle events.
Practical examples:
- Automatically deleting users who have unsubscribed from your service.
- Removing test or duplicate contacts from your Intercom database.
- Integrating with other systems to ensure data consistency by deleting contacts when they are removed elsewhere.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | The Intercom-defined ID representing the Contact to be deleted. This is a required field. |
Output
The output will contain the JSON response from the Intercom API after attempting to delete the contact. Typically, this may include confirmation of deletion or details about the deleted contact. If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.
Example output on success:
{
"type": "contact",
"id": "123456789",
"deleted": true
}
Example output on failure (with Continue On Fail):
{
"error": "Intercom Error: { ... }"
}
Dependencies
- External Service: Requires access to the Intercom API.
- API Credentials: You must configure valid Intercom API credentials (
intercomCredentialsApi) in n8n for this node to function.
Troubleshooting
Common Issues:
- Invalid or missing ID: If the provided ID does not correspond to an existing contact, the API will return an error.
- Authentication errors: If the Intercom credentials are incorrect or missing, the node will fail to connect to the API.
- Insufficient permissions: The API key used must have permission to delete contacts.
Error Messages:
Intercom Error: {...}: Indicates an error returned by the Intercom API. Check the error details for more information (e.g., invalid ID, permission denied).Missing required parameter: id: Ensure that the "ID" property is set and corresponds to a valid contact.
How to resolve:
- Double-check the "ID" value.
- Verify your Intercom API credentials in n8n.
- Ensure your Intercom account has sufficient permissions.