4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, specifically allowing management of opt-in cases related to contacts. The "Revoke" operation under the "Opt-in-Case" resource enables users to revoke an existing opt-in case for a specified contact. This is useful in scenarios where a contact withdraws consent or opts out from communications, ensuring compliance with data protection regulations and maintaining accurate subscription statuses.

Practical examples include:

  • Revoking marketing consent when a user unsubscribes.
  • Managing GDPR-related opt-out requests.
  • Updating contact preferences dynamically based on user actions.

Properties

Name Meaning
Opt-In-Case Select the specific opt-in case to revoke. Can be chosen from a list of existing opt-in cases or specified by its numeric ID.
Contact Select the contact associated with the opt-in case. Can be selected from a list or specified by ID.
Additional Fields Optional fields to provide extra information. Currently supports:
- IP The IP address of the end user responsible for granting/revoking the opt-in case. If not provided, it may be set by the system.

Note: There is also a notice indicating that the email of a contact can be used as an alternative identifier, but this is informational only.

Output

The node outputs a JSON array containing the results of the revoke operation. Each item in the output corresponds to the processed input item and typically includes details about the revoked opt-in case status or confirmation of the action.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the 4leads platform.
  • The node depends on internal handlers for managing opt-in cases, which interact with the 4leads API.
  • Proper configuration of the 4leads API credentials within n8n is necessary.

Troubleshooting

  • Invalid Opt-In Case ID: If the provided opt-in case ID does not match the expected numeric format, the node will reject it. Ensure IDs are numeric strings.
  • Contact Not Found: Selecting a contact that does not exist or is not linked to the opt-in case may cause errors. Verify contact selection.
  • API Authentication Errors: Missing or invalid API credentials will prevent successful execution. Confirm that the API key is correctly configured.
  • Network Issues: Connectivity problems with the 4leads API endpoint can cause timeouts or failures. Check network access and API availability.

Links and References

Discussion