Boost posts/statuses from a specific FediVerse account on your mastodon profile
Template Overview
This template is designed for individuals and businesses who want to maintain a consistent presence on the Fediverse while also posting on Threads or managing multiple Fediverse profiles. By automating the process of resharing statuses or posts, this workflow saves time and ensures regular engagement across accounts.
Use Case
The template addresses the challenge of managing activity across Fediverse accounts by automatically boosting or resharing posts from a specific account to your own. It is especially helpful for users who want to consolidate engagement without manually reposting content across multiple platforms or profiles.
How It Works
The workflow runs on a scheduled trigger and retrieves recent posts from a specified Fediverse account, such as your Threads.net account. It uses a JavaScript filter to identify posts from the current day and then automatically boosts or reshares them to your selected Mastodon profile.
Preconditions
You need a Mastodon account with developer access. Identify a Threads.net or other Fediverse account which you want to boost. Basic familiarity with APIs and setting up credentials in n8n.
Setup Steps
Step 1: Create a Developer Application on Mastodon
Log in to your Mastodon account and navigate to Preferences > Development > New Application. Fill out the required information and create your application. Set Scopes to atleast read, profile, write:statuses. Click Submit. Note down the access token generated for this application.
Step 2: Get the Account ID
Use the following command to retrieve the account ID for the profile you want to boost:
curl -s "https://mastodon.social/api/v1/accounts/lookup?acct=<ACCOUNTNAME>"
Alternatively, paste the URL into a GET node on n8n. From the returned JSON, copy the "id" field value (e.g., {"id":"110564198672505618", ...}).
Step 3: Update the "Get Statuses" Node
Replace <ACCOUNTID> in the URL field with the ID you retrieved in Step 2:
https://mastodon.social/api/v1/accounts/<ACCOUNTID>/statuses
Step 4: Configure the "Boost Statuses" Node
Authentication type will already be set to Header Auth.
Grab the access token from Step 1. In the Credential for Header Auth field, create a new credential. Click the pencil icon in the top-left corner to name your credential. In the Name field, enter Authorization. In the Value field, enter Bearer <YOUR_MASTODON_ACCESS_TOKEN>. (Note: there is a space after "Bearer.") Save the credential, and it should automatically be selected as your Header Auth.
Step 5: Test the Workflow
Run the workflow to ensure everything is set up correctly. Adjust filters or parameters as needed for your specific use case.
Customization Guidance
Replace mastodon.social with your own Mastodon domain if you're using a self-hosted instance. Adjust the JavaScript filter logic to meet your specific needs (e.g., filtering by hashtags or keywords). For enhanced security, store the access token as an n8n credential. Embedding it directly in the URL is ++not recommended++.
Notes
This workflow is designed to work with any Mastodon domain. Ensure your Mastodon account has appropriate permissions for boosting posts.
By following these steps, you can automate your Fediverse engagement and focus on creating meaningful content while the workflow handles the rest!
Related Templates
USDT And TRC20 Wallet Tracker API Workflow for n8n
Overview This n8n workflow is specifically designed to monitor USDT TRC20 transactions within a specified wallet. It u...
Automate Daily Keyword Research with Google Sheets, Suggest API & Custom Search
Who's it for This workflow is perfect for SEO specialists, marketers, bloggers, and content creators who want to automa...
Bulk Automated Google Drive Files Sharing and Direct Download Link Generation
This N8N workflow automates the process of sharing files from Google Drive. It includes OAuth2 authentication, batch pro...
π Please log in to import templates to n8n and favorite templates
Workflow Visualization
Loading...
Preparing workflow renderer
Comments (0)
Login to post comments