4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, specifically allowing users to retrieve data about sign-in forms. The "Get" operation for the "Sign in Form" resource enables fetching either a single sign-in form by its ID or multiple sign-in forms based on search criteria and pagination.

Common scenarios include:

  • Retrieving details of a specific sign-in form to use in workflows that require form metadata.
  • Searching and listing multiple sign-in forms filtered by name or other criteria, useful for bulk processing or reporting.
  • Paginating through large sets of sign-in forms when managing many forms within 4leads.

Practical examples:

  • Fetching a particular sign-in form's configuration to pre-fill data in another system.
  • Listing all sign-in forms containing a certain keyword in their names to analyze usage patterns.
  • Automating export of sign-in form data page by page for integration with external databases.

Properties

Name Meaning
Search for multiple results (bReturnAll) Boolean flag indicating whether to return a single sign-in form object (false) or a list of sign-in form objects (true).
Sign in Form (signInFormId) When bReturnAll is false, this required property lets you select a specific sign-in form either from a searchable list or by entering its numeric ID.
Additional Fields (signInFormQs) When bReturnAll is true, this collection allows specifying optional query parameters:
• Search String: Text to filter sign-in forms by name (e.g., "@muster.de").
• Page Size: Number of results per page (e.g., 5, 10, 20, 50, 200).
• Page Number: Which page of results to retrieve (starting at 1).

Output

The node outputs an array of JSON objects representing sign-in form data retrieved from 4leads.

  • If fetching a single sign-in form, the output contains one object with detailed properties of that form.
  • If fetching multiple sign-in forms, the output is an array of such objects matching the search and pagination criteria.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on internal handlers that interact with 4leads endpoints to fetch sign-in form data.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid Sign in Form ID: Entering a non-numeric or incorrect ID will cause validation errors. Ensure the ID consists only of digits.
  • Empty Results When Returning Multiple: If no sign-in forms match the search string or if the page number exceeds available pages, the output will be empty. Adjust search terms or pagination accordingly.
  • API Authentication Errors: Missing or invalid API credentials will prevent data retrieval. Verify the API key is correctly set up in n8n credentials.
  • Network Issues: Connectivity problems can cause request failures. Check network access to the 4leads API endpoint.

Links and References

Discussion