Fider icon

Fider

Interact with Fider API
Join our community

Actions12

Overview

This node interacts with the Fider API, a platform for collecting and managing user feedback. Specifically, the "Comment" resource with the "Create" operation allows users to add new comments to existing posts on a Fider instance.

Typical use cases include:

  • Automatically adding user feedback or discussion points as comments to specific posts.
  • Integrating external systems that collect user input and funneling it into Fider as comments.
  • Enriching posts with additional context or clarifications via comments programmatically.

For example, after creating a post about a new feature request, you could use this node to add initial comments from your team or import comments collected elsewhere.

Properties

Name Meaning
URL The target URL of the Fider instance where the comment will be added (e.g., https://example.com).
Post ID The numeric identifier of the post to which the comment will be attached.
Content The textual content of the comment to create.

Output

The node outputs JSON data representing the newly created comment as returned by the Fider API. This typically includes details such as the comment's ID, content, author information, timestamps, and any other metadata provided by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to a Fider instance via its API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node depends on internal helper functions (from GenericFunctions) to perform API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials can cause authentication failures.
    • Incorrect Post ID may result in errors if the post does not exist.
    • Network connectivity problems to the Fider instance URL.
    • Missing required parameters like URL, Post ID, or Content will prevent successful execution.

  • Error messages:

    • Errors from the Fider API (e.g., 404 Not Found for invalid Post ID) will be surfaced.
    • If the node is set to continue on fail, error messages will appear in the output JSON under an error field.
    • Authentication errors usually indicate misconfigured or expired API tokens.

To resolve these:

  • Verify the API key and permissions.
  • Confirm the Post ID exists on the target Fider instance.
  • Ensure the URL is correct and reachable.
  • Provide all required fields when configuring the node.

Links and References

Discussion