Actions12
Overview
This node interacts with the "Post" resource of the Fider API, specifically supporting the Edit operation for posts. It allows users to update existing posts by modifying fields such as the post's title and description. This is useful in scenarios where content needs to be corrected, updated, or improved after creation.
Practical examples include:
- Updating a post's title to better reflect its content.
- Changing the description to add more details or fix errors.
- Detaching a post from certain contexts if supported (see properties).
Properties
| Name | Meaning |
|---|---|
| Post ID | The unique identifier of the post to edit. |
| Update Fields | Collection of fields to update on the post. Options: |
| - Title: New title of the post | |
| - Description: New description of the post | |
| Detached | Boolean flag indicating whether to detach the post (meaning depends on API context). |
| URL | Target URL to visit (likely used internally or for API endpoint configuration). |
| Flattened Output | Boolean flag to determine whether the output data should be flattened (simplified). |
Note: For this operation, the required inputs are Post ID and optionally any fields inside Update Fields to modify.
Output
The node outputs an array of JSON objects representing the updated post data returned from the API after the edit operation. The structure corresponds to the post object as defined by the Fider API, typically including fields like id, title, description, and other metadata.
If the "Flattened Output" property is enabled, the output data may be simplified or normalized for easier consumption downstream.
No binary data output is indicated for this operation.
Example output snippet (conceptual):
{
"id": 123,
"title": "Updated Post Title",
"description": "Updated description text",
...
}
Dependencies
- Requires an active connection to the Fider API via an API key credential configured in n8n.
- The node uses internal helper functions (
editPost) to perform the API call. - Network access to the target Fider instance URL is necessary.
Troubleshooting
Common issues:
- Invalid or missing Post ID will cause the API call to fail.
- Providing no fields in "Update Fields" may result in no changes or an error.
- Network connectivity problems can prevent successful API communication.
- Insufficient permissions or invalid API credentials will cause authorization errors.
Error messages:
- Errors thrown by the API (e.g., "Post not found", "Unauthorized") will be surfaced.
- If "Continue On Fail" is disabled, the node execution will stop on error.
- Enabling "Continue On Fail" will return error messages in the output JSON under an
errorfield.
Resolution tips:
- Verify the Post ID exists and is correct.
- Ensure at least one field is provided to update.
- Check API credentials and permissions.
- Confirm network connectivity to the Fider API endpoint.
Links and References
- Fider API Documentation (for detailed API endpoints and data structures)
- n8n documentation on Creating Custom Nodes