I use Typefully as the only social media tool for scheduling content for X (Twitter), Threads, Mastodon, Bluesky, and LinkedIn at once. And I used their launched v2 API to automate the publishing of my blog posts to Threads, Mastodon, and Bluesky via a simple n8n workflow.
As you can see the screenshot of n8n workflow in this post on X, here, I will explain the Typefully POST node that you see here. First, I selected an HTTP node in n8n and below are the different fields' data I have:
| HTTP Node Fields |
Value |
| Method |
POST |
| URL |
https://api.typefully.com/v2/social-sets/{social_set_id}/drafts |
| Authentication |
Generic Credential Type |
| Generic Auth Type |
Header Auth |
| Header Auth |
Header Auth Account (Name: Authorization, Value: Typefully API Key), Nothing else changes |
| Send Query Parameters |
OFF |
| Send Headers |
OFF |
| Send Body |
ON |
| Body Content Type |
JSON |
| Specify Body |
Using JSON |
| JSON |
JSON provided below |
| Options |
No properties |
I needed to replace {social_set_id} with my actual social set ID, and then it was done. Also, here's the body JSON in the HTTP node.
{
"platforms": {
"mastodon": {
"enabled": true,
"posts": [
{
"text": "🎉 New post: ARTICLE_TITLE ARTICLE_LINK"
}
]
},
"threads": {
"enabled": true,
"posts": [
{
"text": "🎉 New post: ARTICLE_TITLE ARTICLE_LINK"
}
]
},
"bluesky": {
"enabled": true,
"posts": [
{
"text": "🎉 New post: ARTICLE_TITLE ARTICLE_LINK"
}
]
}
},
"draft_title": "SOMETHING_HERE",
"share": false,
"publish_at": "now"
}
It's very simple and straightforward, and it just works as expected. As soon as a blog post goes live on my site, the n8n workflow executes and the article's link gets published on Threads, Mastodon, and Bluesky.
And the reason I don't publish these on X and LinkedIn because I use these two platform a bit differently.