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 interacts with the Mastodon API, specifically providing functionality to manage muted accounts among many other Mastodon resources. The "Unmute Account" operation under the "Mutes" resource allows users to remove an account from their muted list on a specified Mastodon instance.
Common scenarios for this node include social media management automation where users want to programmatically control their Mastodon interactions, such as muting or unmuting accounts based on certain triggers or workflows. For example, a user might automatically unmute an account after a certain event or time period, or as part of a moderation workflow.
Practical example:
- Automatically unmute a previously muted account when it posts content matching specific keywords.
- Integrate with customer support tools to unmute accounts after resolving issues.
Properties
| Name | Meaning |
|---|---|
| Mastodon URL | The URL of the Mastodon instance to connect to (e.g., https://mastodon.social). |
| Account ID | The unique identifier of the account to unmute. |
Output
The output is a JSON object representing the response from the Mastodon API after attempting to unmute the specified account. This typically includes details about the unmuted account or confirmation of the unmute action.
If multiple input items are processed, the output will be an array of such JSON objects, each corresponding to one unmute operation.
The node does not output binary data.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Mastodon API.
- Needs the Mastodon instance URL to direct API calls correctly.
- The node depends on the Mastodon API being accessible and the authenticated user having permission to unmute accounts.
Troubleshooting
Common Issues:
- Incorrect Mastodon URL or unreachable instance can cause connection errors.
- Invalid or expired API authentication token will result in authorization failures.
- Providing an invalid or non-existent Account ID may cause the API to return errors indicating the account cannot be found or unmuted.
Error Messages:
"The operation "unmute" for resource "mutes" is not implemented!"— indicates a misconfiguration or unsupported operation; ensure the correct resource and operation names are used.- Network or authentication errors usually indicate problems with credentials or instance URL. Verify these settings.
- API error messages returned in the JSON output can provide clues, such as rate limits or permission issues.
Resolution Tips:
- Double-check the Mastodon URL and ensure it is reachable.
- Refresh or reconfigure the API authentication token credential.
- Confirm the Account ID is correct and that the authenticated user has rights to unmute that account.