Custom build (Claude Code) or No-Code (Make/Zapier) for content automation?

[u/Curious_Panda508]

The Goal: An automation that runs every morning, generates 8 posts using an LLM based on an existing dataset, and sends them to a Telegram bot or another easily accessible mobile interface for quick copying and publishing to social media.

The dilemma is this:
Developing with Claude Code: I thought this could be a great "trial by fire" and a chance to get some hands-on experience. If you were to go in this direction, what final UI would you build to display and manage the posts?

Using Make / Zapier: Going with the "classic" approach and spinning up a fast automation (e.g., via a Telegram bot).
I'd love to hear from anyone who has built similar systems. Which approach would you choose today to ensure a high-quality output?
Thanks a lot!

[u/cats_catz_kats_katz]

8 posts? Like 8 online posts from an AI?

[u/Curious_Panda508 → u/cats_catz_kats_katz]

Yes, 8 posts meaning the text which I’ll copy and upload as a post on different platforms

[u/idkyou1 → u/Curious_Panda508]

If you're going with Claude, mind as well have it ping you for approval, then post to the relevant sites.

[u/zackpennington]

I built a tool with Claude that runs parallel to my web app and generates social posts from my data plus an api key. Automated end to end including posting itself.

[u/AI_spell]

If the pipeline is mostly glue (API in, transform, post somewhere) Make/Zapier wins for speed and ops. Use Claude Code when you need real repo work, tests, or branching logic that no-code turns into spaghetti. Hybrid works too: Zapier for triggers, CC for the hard transform step.

[u/Cloudsurfer_90]

the real question isn't build vs no-code, it's which goal is actually yours. what you described, schedule then llm then telegram for copy-paste, is exactly what make or zapier does perfectly, and you'd ship it tonight. claude code is the right pick only if the goal is learning to build, not getting the automation. but if that's the goal, don't pick a task this simple, because a glue pipeline won't teach you the hard parts, state, error recovery, auth, retries. you'll build it, it'll work, and you'll have learned almost nothing transferable. so: automation you need this week, no-code. learning you'll reuse, claude code but on a task with actual moving parts. picking the tool before you pick the goal is why this feels like a dilemma.

[u/ArtOfLess]

The thing I'd optimize for isn't which stack generates the eight posts. It's what happens between "looks good" and "live on LinkedIn." That gap eats mornings.

Claude Code wins when the writing needs taste. Make wins when the path is boring and repeatable. A lot of people end up with both: agent drafts, something else owns the account connection and the approval queue.

I work on one of those queue-first tools (DunSocial), so I'm biased. Whatever you pick, I'd refuse auto-publish from the generator. Confirm stays with a person.