4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, specifically allowing management of opt-in cases for contacts. The "Opt-in-Case" resource with the "Grant" operation enables users to grant an opt-in case to a specific contact. This is useful in scenarios where explicit consent or permission needs to be recorded for marketing communications or data processing compliance.

Practical examples include:

  • Granting a subscription consent to a contact after they sign up on a website.
  • Recording user permission for receiving newsletters or promotional emails.
  • Managing GDPR or other privacy regulation consents by programmatically updating opt-in statuses.

Properties

Name Meaning
Opt-In-Case Select the opt-in case to grant. Can be chosen from a list of existing opt-in cases or specified by ID.
Contact Select the contact to whom the opt-in case will be granted. Can be chosen from a list or specified by ID.
IP (Optional) The end user's IP address responsible for granting this opt-in case. If not provided, system sets it.

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

Output

The node outputs a JSON array containing the results of the grant operation(s). Each element corresponds to the response from granting the opt-in case to a contact. The exact structure depends on the 4leads API response but typically includes confirmation details about the granted opt-in case.

No binary data output is indicated.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node relies on internal handlers to interact with the 4leads service endpoints.
  • Proper permissions and valid IDs for opt-in cases and contacts must be available in the 4leads account.

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 the ID is numeric.
  • Contact Not Found: Selecting a contact that does not exist or is invalid will cause errors. Use the search list mode to pick valid contacts.
  • API Authentication Errors: Missing or incorrect API credentials will prevent successful execution. Verify the API key configuration.
  • Network Issues: Connectivity problems with the 4leads API endpoint may cause timeouts or failures.
  • Permission Denied: Insufficient permissions on the 4leads side to modify opt-in cases will result in errors.

To resolve these issues:

  • Double-check all IDs and selections.
  • Confirm API credentials are correct and have necessary scopes.
  • Test connectivity to the 4leads API.
  • Review 4leads account permissions.

Links and References

Discussion