Social media automation with Make
Use Make's HTTP module against api.aetherhq.dev. Same contract as Zapier and n8n — one API for every connected profile.
- • A Make.com account
- • Aether API key
- • An Aether account — free, no credit card
Step 1 — Add an HTTP module
Scenario → HTTP → Make a request. Method POST, URL https://api.aetherhq.dev/v1/posts.
Step 2 — Map the JSON body
Pull text and media from the previous module (Google Sheets, RSS, Airtable). profileIds stay hardcoded or come from a Data Store.
{
"text": "{{1.text}}",
"profileIds": ["ig_abc123", "tt_xyz789"],
"mediaUrls": ["{{1.imageUrl}}"]
}Step 3 — Authenticate the request
Headers: Authorization = Bearer aeth_live_… and Content-Type = application/json. Store the key in Make's connection / variable, not in a public scenario blueprint.
Step 4 — Receive Aether webhooks in Make
Add a Custom webhook trigger, copy the URL, and register it in Aether. Route post.failed to a Slack module.
await aether.webhooks.create({
url: "https://hook.eu2.make.com/xxxxxxxx",
events: ["post.published", "post.failed"],
});Step 5 — Schedule from a Make scenario
If you want Aether to own the clock, set scheduledFor in the HTTP body. If Make should own the clock, use a Make scheduler and omit scheduledFor so the post publishes immediately when the scenario runs.
- ✓HTTP POST to /v1/posts
- ✓Bearer auth in Make
- ✓Custom webhook for publish events
- ✓Choose Make scheduler vs Aether scheduledFor
Start building
Free API key — 3 connected accounts, all endpoints, no credit card.