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 "Get" operation retrieves comments associated with a particular post. This is useful when you want to fetch all comments for a given post to analyze user feedback, display them elsewhere, or process them further in your workflow.

Practical example:
You have a feedback post on your Fider instance and want to automatically pull all comments related to that post into another system (e.g., a CRM or analytics tool) for review or reporting.

Properties

Name Meaning
URL The target URL of the Fider instance you want to interact with (e.g., https://example.com).
Post ID The numeric identifier of the post whose comments you want to retrieve.

Output

The output is an array of JSON objects representing the comments retrieved from the specified post. Each item in the output corresponds to one comment and contains fields as returned by the Fider API's comments endpoint. The exact structure depends on the API response but typically includes comment content, author information, timestamps, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to a Fider API instance.
  • Needs an API authentication token configured in n8n credentials to authorize requests to the Fider API.
  • The node depends on internal helper functions (getComments) to perform the API call.

Troubleshooting

  • Common issues:

    • Invalid or missing Post ID: Ensure the Post ID is correct and exists in the Fider instance.
    • Incorrect URL: Verify the URL points to a valid Fider instance.
    • Authentication errors: Confirm that the API key credential is correctly set up and has sufficient permissions.
    • Network connectivity problems: Check network access to the Fider server.

  • Error messages:

    • Errors thrown by the API (e.g., 404 Not Found if the post does not exist).
    • NodeOperationError with the message from the underlying API error.

    To resolve these, verify input parameters, credentials, and network connectivity. Use the "Continue On Fail" option in the node settings to handle errors gracefully within workflows.

Links and References

Discussion