Fider icon

Fider

Interact with Fider API

Actions12

Overview

This node interacts with the Fider API, a platform for collecting and managing user feedback. Specifically, the "User" resource with the "Get" operation retrieves a list of users from the Fider system.

Common scenarios where this node is useful include:

  • Fetching all registered users to analyze community engagement.
  • Integrating user data into other workflows or systems for reporting or notifications.
  • Automating user management tasks by retrieving user lists programmatically.

Example: You might use this node to get all users who have signed up on your feedback platform and then send them a newsletter or export their details to a CRM.

Properties

Name Meaning
URL Target URL to visit (the base URL of the Fider instance you want to interact with).

Note: Although only the "URL" property is listed here, the node internally uses other parameters depending on the resource and operation, but for the User-Get operation, no additional input properties are required beyond the URL.

Output

The output is an array of JSON objects representing users retrieved from the Fider API. Each item in the output corresponds to one user and contains user-related fields as returned by the API, such as user ID, username, email, and any other user metadata provided by Fider.

No binary data output is produced by this operation.

Dependencies

  • Requires access to a Fider API endpoint specified by the URL property.
  • Requires an API authentication token credential configured in n8n to authorize requests to the Fider API.
  • The node depends on internal helper functions (from GenericFunctions) to perform API calls.

Troubleshooting

  • Common issues:

    • Incorrect or unreachable URL: Ensure the URL points to a valid Fider instance.
    • Missing or invalid API authentication token: Verify that the API key credential is correctly set up.
    • Network connectivity problems: Check firewall or proxy settings that may block API requests.
  • Error messages:

    • Errors thrown by the node typically contain the message from the underlying API call failure.
    • If "continue on fail" is enabled, errors will be returned as part of the output JSON under an error field.
    • To resolve errors, verify credentials, URL correctness, and network accessibility.

Links and References

Discussion