Overview
This node integrates with a telephony or contact management service to perform operations on contacts. Specifically, the Delete Contact operation allows users to remove one or more contacts identified by their phone numbers. This is useful in scenarios where you want to clean up your contact list, remove outdated or incorrect entries, or automate contact management workflows.
For example, you might use this node to delete contacts who have unsubscribed from a service or to synchronize your contact database by removing entries that no longer exist in an external system.
Properties
| Name | Meaning |
|---|---|
| Phone Numbers | A collection of phone numbers representing the contacts to delete. Each number must include the country code (e.g., +1 for USA). You can add multiple phone numbers to delete multiple contacts at once. |
The "Phone Numbers" property is a fixed collection allowing multiple values. Each entry requires a single phone number string.
Output
The node outputs an array of JSON objects corresponding to each input item processed. For each successfully deleted contact, the output JSON contains the response from the deletion operation (structure depends on the external API's response).
If an error occurs during processing and the node is set to continue on failure, the output JSON for that item will contain an error field with the error message.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the external telephony/contact service.
- The node depends on the external service's API to perform contact deletions.
- Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing phone numbers: Ensure all phone numbers include the correct country code and are formatted properly.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Check connectivity and service status of the external API.
Error Messages:
- Errors thrown by the external API will be surfaced as error messages in the node output if "Continue On Fail" is enabled.
- Typical errors may include "Contact not found," "Invalid phone number format," or authentication failures.
Resolution Tips:
- Double-check phone number formats.
- Confirm API credentials and permissions.
- Use the node’s error output to identify problematic items and adjust inputs accordingly.
Links and References
- Refer to the external telephony/contact service API documentation for details on contact deletion endpoints and expected request/response formats.
- n8n documentation on creating custom nodes for further customization guidance.