I am testing my first automated end to end social media post automation system. which is created using the free tools. But it is very efficient and productive. i can use this thing in future posting on various platforms to tell people about my learning's and update about me.
Tools :
Make.com = I use this tool to mainly automate my system it include flow how things works and system is linked.
Hashnode = I use this as a central blog and article publishing tool other tools is connected with it so content links is properly distributed.
Google Ai Studio = I use this to integrate the ai in between this whole process which just do small job to add the engaging hook and the tags for the reach
Buffer = I use to connect X (twitter) with this Because Make.com remove the platform X (twitter) to His integration. After the policy change of the platform.
Dev.to = I use this to improve SEO of my post over the google search engine.
Challenges :
I cannot integrate the github actions with the hashnode becuase this feature is become paid on hashnode. May be in future i can do this thing using self written yml file, i am guessing Not sure will this 100 % work or not.
Twitter integration as i described early that twitter integration is not present in the make.com so i use the another tool Buffer.
The limits calculation, Their was a limits on each tools for their specific use case so i have to intentionally calculate them properly. Even the free tear of the twitter which is X is few hundreds words that's why i have to limit the text of the post, which is hook only, The threads creation i don't think it will be their in this tools which i am using, i will definitely find it if their.
Solutions :
Simply use other Way if this way is closed, use different tool for twitter
May be in future i create yml file for the github actions but for now i am directly writing on hashnode.
The dev.to does not provide feature of direct posting it save your cycle into draft so you have to manually click on publish button. i choose once a week i will do for all the posts. Because these posts is My documentation of journey. Or May be an Assets.
Top comments (1)
Nice first automation setup — the tool-hopping (Make → Buffer for X, Hashnode as the hub) is exactly how these systems evolve in practice. Two suggestions from experience: (1) keep a plain-text "source of truth" for each post (a markdown file or a Notion/Google Sheet row) and let the automation read from it, so you are not fighting tool-specific limits to edit content; (2) for the dev.to draft step, you can use their API to create the draft programmatically and just click publish weekly — that saves the copy-paste cycle. The weekly manual publish cadence is actually a good habit anyway, it keeps you reviewing what goes out.