SurenseInstall

Overview

This node integrates with the Surense API to perform various operations on different resources. Specifically, for the "Contact" resource and the "Delete Contacts" operation, it allows users to delete one or more contacts by specifying their unique identifiers (UUIDs). This is useful in scenarios where you need to clean up outdated or irrelevant contact records from your Surense database automatically as part of a workflow.

Practical examples include:

• Automatically removing contacts who have unsubscribed or requested deletion.
• Cleaning up test or duplicate contacts after data import.
• Managing contact lifecycle by deleting contacts that no longer meet certain criteria.

Properties

The property "אנשי קשר למחיקה" (translated: "Contacts to Delete") is a fixed collection allowing multiple entries. Each entry requires the "מזהה איש קשר" ("Contact ID"), which is a string representing the UUID of the contact to be deleted.

Output

The node outputs an array where each element corresponds to the result of the operation performed on each input item. The output JSON typically contains the response from the Surense API regarding the deletion status of each contact.

If an error occurs during deletion and the node is configured to continue on failure, the output will include an object with an error field describing the issue for the specific item.

No binary data output is indicated for this operation.

Dependencies

• Requires an active connection to the Surense API via an OAuth2 API credential.
• The node depends on the Surense API being accessible and the credentials having sufficient permissions to delete contacts.
• No additional environment variables or external services are explicitly required beyond the API authentication.

Troubleshooting

• Common issues:

  • Invalid or malformed Contact IDs (not in UUID format) will likely cause API errors.
  • Insufficient permissions or expired API tokens may result in authorization errors.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • Errors returned from the Surense API will be propagated. For example, "Contact not found" if the ID does not exist.
  • If the node is set to stop on failure, any error will halt execution; otherwise, errors are included in the output per item.

• Resolutions:

  • Verify that all Contact IDs are correct and in UUID format.
  • Ensure the API credentials are valid and have the necessary scopes.
  • Check network connectivity and Surense API status.

Links and References

• Surense API Documentation (hypothetical link)
• n8n documentation on OAuth2 API Credentials
• General best practices for managing contacts in CRM systems