Mailtrap

Overview

This node is designed to delete a contact from an account in a service that manages contacts (likely Mailtrap based on the icon reference). It allows users to specify which contact to delete by providing either the contact's ID or email address along with the account ID. This operation is useful for maintaining clean contact lists by removing outdated or unwanted contacts.

Practical examples:

• Removing a user who unsubscribed from a mailing list.
• Deleting test contacts after a campaign has ended.
• Cleaning up duplicate or invalid contacts from an account.

Properties

Output

The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of deletion or any error messages returned by the API. There is no indication that binary data is output by this node.

Dependencies

• Requires an API key or bearer token for authentication.
• Needs the account ID and contact identifier (ID or email) to perform the deletion.
• Depends on an external API endpoint to process the delete request (implied by the router call).

Troubleshooting

• Invalid Credentials: If authentication fails, ensure the provided API token or bearer token is valid and has sufficient permissions.
• Contact Not Found: If the contact ID or email does not exist in the specified account, the API may return an error indicating the contact was not found.
• Missing Required Fields: Ensure both Account ID and Contact ID or Email are provided; otherwise, the node will not execute properly.
• Network Issues: Connectivity problems can cause failures; verify network access to the API endpoint.

Links and References

• Refer to the service’s official API documentation for details on deleting contacts.
• Consult n8n documentation on how to configure API credentials and handle authentication tokens.