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 "Create" operation allows you to create a new user in the Fider system by providing their name and email address.

Common scenarios where this node is beneficial include:

  • Automating user registration workflows in feedback management systems.
  • Integrating user creation into customer support or CRM pipelines.
  • Syncing user data from other platforms into Fider for unified feedback tracking.

For example, after receiving a signup form submission on your website, you could use this node to automatically add the new user to your Fider instance.

Properties

Name Meaning
URL Target URL of the Fider instance to interact with (e.g., https://example.com). This is the base endpoint for API requests.
User Name The name of the user to be created in Fider.
Email The email address of the user to be created.

Output

The node outputs JSON data representing the newly created user object as returned by the Fider API. This typically includes user details such as ID, name, email, and any other metadata provided by the API response.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to a Fider API instance specified by the URL property.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests to the Fider API.
  • Relies on internal helper functions (createUser) that handle the actual API call.

Troubleshooting

  • Common issues:

    • Invalid or missing URL: Ensure the URL points to a valid Fider instance.
    • Authentication errors: Verify that the API key or token credential is correctly set up and has sufficient permissions.
    • Missing required fields: Both "User Name" and "Email" must be provided; otherwise, the API will reject the request.
    • Network connectivity problems: Confirm that n8n can reach the Fider server.
  • Error messages:

    • Errors thrown by the API (e.g., 400 Bad Request) will be surfaced as node execution errors unless "Continue On Fail" is enabled.
    • If the node fails due to invalid input, check the parameter values carefully.
    • Timeout or connection refused errors indicate network or server availability issues.

Links and References

Discussion