4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, specifically allowing users to retrieve information about "Opt-in-Cases." The "Get" operation for the Opt-in-Case resource enables fetching either a single opt-in-case by its ID or multiple opt-in-cases based on search criteria and pagination.

Common scenarios include:

  • Retrieving details of a specific opt-in-case to verify subscription or consent status.
  • Searching through multiple opt-in-cases to analyze user consent trends or manage marketing campaigns.
  • Paginating through large sets of opt-in-cases to process or display them in batches.

Practical example:

  • A marketing automation workflow that fetches an opt-in-case by ID to confirm if a contact has given consent before sending promotional emails.
  • A data synchronization task that retrieves all opt-in-cases matching a search string (e.g., email domain) to update CRM records accordingly.

Properties

Name Meaning
Opt-In-Case Select a specific opt-in-case either from a searchable list or by entering its numeric ID.
Search for multiple results (boolean) Choose whether to return a single opt-in-case object (false) or a list of opt-in-cases (true).
Additional Fields (only when returning multiple results) Optional parameters to refine the search and pagination:
• Search String: Text to filter opt-in-cases by name fields (e.g., partial email).
• Page Size: Number of results per page (e.g., 5, 10, 20, 50, 200).
• Page Number: Which page of results to retrieve (1-based index).

Output

The node outputs JSON data representing the retrieved opt-in-case(s):

  • When fetching a single opt-in-case by ID, the output is a JSON object containing detailed information about that opt-in-case.
  • When retrieving multiple opt-in-cases, the output is a JSON array of objects, each representing an opt-in-case matching the search criteria and pagination settings.

The exact structure of each opt-in-case object depends on the 4leads API response but typically includes identifiers, names, and related metadata about the opt-in consent case.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the 4leads platform via an API key credential configured in n8n.
  • The node depends on internal handlers that interact with the 4leads API endpoints for opt-in-cases.
  • Proper API permissions are necessary to perform read operations on opt-in-case data.

Troubleshooting

  • Invalid Opt-In-Case ID: If the ID provided does not match the expected numeric format, the node will reject it due to regex validation. Ensure only digits are entered.
  • No Results Found: When searching with filters or pagination, if no opt-in-cases match, the output will be empty. Verify search strings and paging parameters.
  • API Authentication Errors: If the API key is missing, invalid, or lacks required permissions, the node will throw authentication errors. Confirm credentials are correctly set up.
  • Rate Limits or Network Issues: The 4leads API may enforce rate limits or experience downtime. Retry logic or error handling should be implemented in workflows using this node.

Links and References

Discussion