Overview
This node handles various operations related to managing contacts in the Autocust system. Specifically, for the Delete Contact operation, it allows users to remove a contact by specifying its unique ID. This is useful in scenarios where you need to clean up your contact database by removing outdated or incorrect entries.
Practical examples include:
- Automatically deleting contacts who have unsubscribed or requested removal.
- Cleaning up test or duplicate contacts from your list.
- Integrating with other workflows that require contact deletion as part of data management.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The ID of the contact to delete |
The "Contact ID" property is required and must be a number representing the unique identifier of the contact to be deleted.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the contact was successfully deleted or provide details about the deletion status.
If the node supports binary data output (not indicated here), it would generally relate to any files or attachments associated with the contact, but this operation focuses on deletion and thus primarily outputs JSON confirmation.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- The node depends on the Autocust API endpoint responsible for contact deletion.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will likely cause the operation to fail.
- Missing or incorrect API authentication credentials will prevent the node from connecting to the Autocust service.
- Network connectivity problems can also cause failures.
Error messages:
"The operation 'deleteContact' is not known!"— This indicates an unsupported operation was selected; ensure "Delete Contact" is chosen.- Errors related to authorization typically mean the API key is missing, expired, or incorrect.
- If the contact ID does not exist, the API may return a "not found" error; verify the ID before attempting deletion.
To resolve these issues:
- Double-check the Contact ID value.
- Verify API credentials are correctly set up and valid.
- Ensure network access to the Autocust API is available.
Links and References
- Autocust API Documentation (hypothetical link)
- n8n Expressions Guide
- n8n Credential Setup