Social Scheduling & Repurpose-to-Post Agent
Not another one-shot calendar — this is the always-on automation behind it. A build-it-once Automation Blueprint (shipped for BOTH n8n and Make.com) that generates on-brand posts from your content pillars and auto-queues them into your OWN Buffer or the native platform APIs on your chosen cadence, plus the content-generation prompt pack that feeds the queue. You import the blueprint, paste your own API keys, and run it on your own accounts — ECTD hosts nothing, stores no posts, and never touches your logins.
The choice in front of you is not which scheduling app to subscribe to. It is whether the machinery that fills your queue belongs to you or to somebody else's platform. This is that machinery: A$99 one-off for an Automation Blueprint you import into your own stack and run on your own accounts.
What arrives is a written build specification — a full n8n build, node by node, and a full Make.com build, module by module, in the one Markdown file — together with the content-generation prompt pack that feeds the queue. The specs are shaped by what you tell us at intake: the platforms you post to, your cadence, your content pillars and brand voice, and the scheduler you already use. Turnaround is around 20 minutes, delivered to your order page.
Once it is built, it generates on-brand posts from your pillars and auto-queues them into your own Buffer account or the native platform APIs, on the cadence you set. ECTD hosts nothing and stores no posts. The A$99 buys the blueprint; the running of it belongs to you.
Both automation platforms, written out in full
The n8n spec and the Make.com spec sit in the same document, and neither is an abbreviated version of the other. If your team lives in n8n, work from that half. If you already run scenarios in Make, work from that half. Migrate later and the other spec is already sitting in the file you bought.
Worth being plain about what that means: this is a build specification, not a hosted service. The importing and the wiring are yours to do, following the steps as written.
Keeping the queue stocked, not just started
The prompt pack supplies one generation prompt per content pillar, plus a hook prompt and a hashtag prompt. The calendar-fill logic is the piece that matters over time — it sets out how a run maps your pillars against your cadence into dated slots, so each execution leaves the queue stocked rather than posting once and stopping.
A field-mapping table connects your data to the fields Buffer or the native platform APIs expect, so nothing is guesswork at wiring time. What comes out of the prompts is still AI-written copy, so read the queue before it goes live — particularly in the early weeks — and treat the prompts as something you tune rather than set once.
Your keys, your credentials, your running costs
Every credential stays inside your n8n or Make instance. We never touch your logins, and the blueprint carries a "paste your OWN key here" data-safety note so the boundary is written down rather than assumed.
The same boundary applies to cost. Model calls and platform API calls accrue on your keys each time the scenario fires, which is why a credit-burn note is included: how the charges build, and how to cap a run before an over-eager schedule does it for you.
Prove the queue fills before you go live
A "test it in 5 minutes" checklist ships with the blueprint so you can watch the queue populate before you point anything at real accounts. A troubleshooting FAQ covers the failure modes that actually turn up: auth failures, rate limits, duplicate posts and an empty queue.
Three free AI revisions come with the purchase, and this is the sensible moment to spend them. You have the spec in front of you, you have run the test, and you know which parts need adjusting for your setup.
What you get
- Automation Blueprint (.md) with a full n8n build spec AND a full Make.com build spec — node/module by node/module
- Content-generation prompt pack that feeds the queue (one prompt per content pillar, plus a hook + hashtag prompt)
- Calendar-fill logic — how the run maps pillars → cadence → dated slots so the queue never runs dry
- Field-mapping table: your data → Buffer / native platform API fields
- Credit-burn warning note — how model + API calls accrue on YOUR keys, and how to cap the run
- “Test it in 5 minutes” checklist to prove the queue fills before you go live
- “Paste your OWN key here” data-safety note — you own and run everything; ECTD holds nothing
- Troubleshooting FAQ (auth failures, rate limits, duplicate posts, empty queue)
- 3 free AI revisions included
Turnaround: ~20 minutes. Delivery: Automation Blueprint — Markdown download (n8n + Make specs).
Frequently asked questions
We already pay for Buffer. Does this replace it?
No — it feeds it. The automation you build queues posts into your existing Buffer account, or straight into the native platform APIs if you would rather skip the middle layer. There is no ECTD dashboard to log into and no software subscription attached to this.
Our team only uses Make.com. Are we paying for half a file?
No. Both specs are written out in full and both ship at the same price. Implement the one that matches your stack; the other is there if you change tools later.
Who checks the posts before they go out?
You do. The prompt pack is shaped by the content pillars and brand voice you supply, so specific intake answers produce closer output. But this is AI-generated copy publishing to your accounts, and it should be read before it goes out rather than trusted blind.
What is the ongoing cost once it is running?
From ECTD, nothing — the A$99 is one-off. Your ongoing spend is whatever your model provider and the platform APIs charge for the calls the scenario makes, billed to your own keys. Volume tracks your cadence and platform count, which is why the credit-burn note is in there.
Included in Agency Growth Pack, Creator Content Pack — save with a bundle.