Usable HTTP path, held native app
For Make social media workflows, Postdom's native Make app is not live or installable. You can use Make's generic HTTP app with Postdom's documented API today. The native app, confidential OAuth client, listing, screenshots and all three templates remain held and unpublished.
Use the generic HTTP path now. Treat the native app and its marketplace material as a transparent roadmap, not as an install option.
Usable now · documented
Configure requests from Postdom's developer documentation. This is the available route today, but this page does not claim that an authenticated Make production run has been completed.
Open the HTTP app referenceRead Postdom's API documentationPrepared · HOLD
8 prepared modules and 3 groups exist in marketplace-owned source. The confidential OAuth client is not registered, so these modules are not released behavior.
Inspect what is preparedNot published
The listing is not submitted. The shot list is ready, but screenshots have not been captured. All three templates are held, with no live marketplace links and no promised release date.
Review the held proposalsYes—use Make's generic HTTP app with Postdom's documented API and a connected TikTok account. The useful proof comes after the request: keep the returned Postdom post ID and read TikTok to a terminal per-destination outcome.
Postdom publishes supplied finished video to these destinations. It does not generate video, add unsupported networks or make every feature inside a destination available.
An accepted or requires_approval response is not provider publication. A scheduled state and a green Make execution are also not provider publication.
Use the documented HTTP configuration, keep credentials and approval with a human, send one supplied video, and reconcile the returned post to a terminal outcome. This is a configuration guide, not evidence of an authenticated Make production test.
Add Make's generic HTTP app and configure it from Postdom's current developer documentation. The prepared native modules are not released behavior, and this guide does not claim an authenticated Make production run.
A human owns the credentials, actual account, policy, consent, intended audience and required disclosures. Store the scoped Postdom credential in Make's connection controls rather than a prompt or ordinary field. An AI agent cannot approve itself or register the held confidential OAuth client.
Use the actual video and caption the human reviewed. Postdom handles supplied finished video; it does not generate video. Stop if the actual video, account, audience, consent, disclosure, commercial-use rights or approval is unresolved.
Target only the selected connected accounts and preserve the returned Postdom post ID. An accepted or requires_approval response is not provider publication. A scheduled state and a green Make execution are not provider publication either.
Use the returned post ID to read the same request through its terminal per-destination outcome. Do not retry the whole workflow when one destination already succeeded. Read metrics only when reported: null is not zero and keeps its availability reason.
Confirm the actual account, actual video, caption, audience, consent, disclosures, reviewer and time. A row marked ready is routing data—not evidence of human approval.
Retain the post ID and inspect each destination before retrying. Preserve unavailable metrics and their reason; null is not zero.
The phrase “AI agent social media Make” describes an agent that can prepare a bounded request and interpret its result inside a scenario. It cannot approve itself, connect an account for the human, widen policy or turn model output into permission to publish.
For metrics, preserve Postdom's availability state beside every value. The metric availability reference explains why an unavailable observation cannot be relabeled as zero.
The manifest contains 8 prepared modules across 3 groups. These names explain the intended surface; they do not establish release, installation or production behavior.
The held acceptance recipe, Postdom closed-loop acceptance recipe, contains 6 planned checks. Its preconditions are not evidence that those checks have run, and its held status is not a production result.
Prepared group
watchPostOutcomewatchPerformanceSnapshotsPrepared group
uploadMediapublishVideosubmitPublicationPlanPrepared group
listAccountsgetPostgetPostPerformanceThese are marketplace-owned source proposals. They are not live Make template pages, not authenticated executions and not evidence that their partner flows have run in production.
Intended trigger: OpenAI response created for an approved video asset
This description is for planning only. No marketplace template or install URL exists to link.
Intended trigger: Approved automation brief received from an AI agent
This description is for planning only. No marketplace template or install URL exists to link.
Intended trigger: Google Sheets row marked Ready with video URL, caption, and account IDs
This description is for planning only. No marketplace template or install URL exists to link.
No. The native app is prepared source under HOLD, not submitted, not listed and not installable. Its shot list is ready, but screenshots have not been captured. Its confidential OAuth client is not registered, all three templates are held, and there is no promised release date.
Use Make's generic HTTP app with Postdom's documented API, a human-owned credential and a connected TikTok account. Send the supplied finished video once, retain the returned post ID, then read that same post to its terminal TikTok outcome. This page describes documented configuration, not an authenticated production run from Make.
It means an agent inside a Make scenario can prepare a bounded API request and interpret its result. Human approval remains mandatory: the human owns credentials, connected accounts, policy, consent, audience and disclosures. The agent cannot approve itself, and Postdom does not generate the video.
No. The marketplace-owned manifest describes 8 prepared modules grouped for publishing and reading outcomes, but that is prepared source, not released behavior. Use the documented generic HTTP path until a real native release exists.
No. All 3 are held source proposals. They have not been published in Make or executed as authenticated production scenarios, and this page does not invent template links.
Postdom's publishing scope is supplied finished video for TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads and Bluesky. It does not add unsupported networks or promise every surface inside those destinations.
No. accepted, requires_approval and scheduled are workflow states, and a green Make execution only means the HTTP step completed. Keep the Postdom post ID and read each destination to its terminal outcome before treating that destination as published or retrying it.