Instasent Data Source icon

Instasent Data Source

Send contacts and events to an Instasent Data Source

Actions3

Overview

This node integrates with the Instasent Data Source to manage contacts and events. Specifically, for the Contact - Delete operation, it deletes a contact from the Instasent system using the unique identifier of the contact (User ID). This is useful in scenarios where you want to remove outdated or incorrect contact information from your data source automatically as part of a workflow.

Practical examples include:

  • Automatically deleting contacts who have unsubscribed or requested removal.
  • Cleaning up test or temporary contacts after a campaign.
  • Synchronizing contact deletions from another CRM or database into Instasent.

Properties

Name Meaning
User ID The unique identifier for the contact to delete

Output

The output is a JSON object representing the response from the Instasent API after attempting to delete the contact. Typically, this will confirm the deletion or provide status information. If an error occurs, the output may contain an error message describing what went wrong.

No binary data is output by this operation.

Example output JSON structure:

{
  "json": {
    // API response confirming deletion or error details
  }
}

Dependencies

  • Requires an active connection to the Instasent API via an API key credential configured in n8n.
  • The node uses the Instasent API endpoint /stream/contacts/{userId} with the HTTP DELETE method to perform the deletion.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID: Ensure the User ID provided matches an existing contact in Instasent.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or API downtime: Check connectivity and Instasent service status.

  • Error messages:

    • Errors returned from the API will be passed through. For example, "Contact not found" indicates the User ID does not exist.
    • If the node throws a generic error, enabling "Continue On Fail" can help isolate problematic inputs without stopping the entire workflow.

Links and References

Discussion