Actions48
- Account Actions
- Authentication Actions
- Blocks Actions
- Bookmarks Actions
- Favourites Actions
- Featured Tags Actions
- Follow Requests Actions
- Media Actions
- Mutes Actions
- Notifications Actions
- Polls Actions
- Status Actions
- Timeline Actions
Overview
This node allows users to interact with the Mastodon API, specifically enabling operations on various Mastodon resources such as statuses, accounts, timelines, media, polls, bookmarks, and more. For the Status resource with the Edit Status operation, it provides functionality to modify an existing status (toot) on a Mastodon instance.
Typical use cases include:
- Updating or correcting a previously posted status.
- Adding or changing content in a status without creating a new one.
- Automating status edits based on external triggers or workflows.
For example, you might use this node to programmatically update a status with new information after an event occurs or to fix typos in a published toot.
Properties
| Name | Meaning |
|---|---|
| Mastodon URL | The URL of the Mastodon instance to connect to, e.g., https://mastodon.social. This defines which Mastodon server the node will interact with. |
Note: Additional properties related to the "Edit Status" operation (such as status ID, new content, visibility, etc.) would typically be defined in the broader node properties but are not included here.
Output
The node outputs JSON data representing the response from the Mastodon API after editing a status. This usually includes the updated status object with fields such as:
id: The unique identifier of the status.content: The edited text content of the status.created_at/edited_at: Timestamps for creation and last edit.visibility: Who can see the status (public, unlisted, private, direct).- Other metadata like media attachments, mentions, tags, etc.
If multiple items are processed, the output is an array of such JSON objects.
The node does not output binary data for this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Mastodon instance.
- Needs the Mastodon instance URL provided by the user to target the correct server.
- Relies on the Mastodon REST API endpoints for status editing.
Troubleshooting
Error: The operation "Edit Status" for resource "Status" is not implemented!
- This indicates a misconfiguration or typo in the operation name. Verify that "Edit Status" is correctly selected.
Authentication errors (e.g., 401 Unauthorized)
- Ensure the API authentication token is valid and has sufficient permissions to edit statuses.
- Confirm the Mastodon URL matches the instance where the token was issued.
Network or connection issues
- Check internet connectivity and that the Mastodon instance URL is reachable.
- Verify no firewall or proxy is blocking requests.
Invalid input data errors
- Make sure the status ID and new content are correctly provided.
- Validate any additional parameters required by the Mastodon API for editing statuses.
If the node is set to continue on fail, errors will be returned in the output JSON under an error field instead of stopping execution.