Actions47
- 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 enables interaction with the Mastodon social network API, specifically allowing users to perform various operations on Mastodon resources such as accounts, statuses, timelines, and more. The "Unmute Account" operation under the "Account" resource allows a user to unmute a specific Mastodon account, effectively restoring notifications and visibility from that account.
Common scenarios for this node include managing Mastodon accounts programmatically, automating social media workflows, or integrating Mastodon interactions into broader automation pipelines. For example, a user might automate unmuting certain accounts after a period of muting or based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Mastodon URL | The URL of the Mastodon instance to connect to (e.g., https://mastodon.example). |
| Account ID | The unique identifier of the Mastodon account to unmute. |
Output
The node outputs JSON data representing the result of the unmute operation on the specified account. This typically includes details about the account's updated mute status or confirmation of the unmute action. The output structure corresponds to the Mastodon API response for unmuting an account.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Mastodon instance.
- Needs the base URL of the Mastodon instance to direct API calls correctly.
- Relies on the Mastodon API being accessible and the authenticated user having permission to unmute the specified account.
Troubleshooting
Common Issues:
- Incorrect or missing Mastodon instance URL can cause connection failures.
- Invalid or expired API authentication tokens will lead to authorization errors.
- Providing an invalid or non-existent Account ID may result in errors or no action taken.
- Network connectivity issues between n8n and the Mastodon instance can cause timeouts or failures.
Error Messages:
"The operation "unmuteAccount" for resource "account" is not implemented!"— indicates a misconfiguration or unsupported operation; ensure correct resource and operation names.- Authorization errors typically indicate problems with the API credentials; verify and refresh them as needed.
- HTTP errors from the Mastodon API (e.g., 404 Not Found) suggest the Account ID does not exist or is inaccessible.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network connectivity.