`add_post_media` — put a visual on Scripe posts, many at once (up to 20). Per item `source`: "recommended" (the visual the data picks — `get_post_media_options` explains it: a fitting media-library photo, else a Scripe template visual, else none); "library" (`mediaIds` from the media library — `search_media`, `get_post_media_options` — or an image YOU made and uploaded with `create_media_asset`); or "scripe" (Scripe makes `format` — QUOTE_CARD, CAROUSEL, INFOGRAPHIC, BILLBOARD, MEME — from its own templates in the workspace's brand; pass `direction`, what it shows; an INFOGRAPHIC needs it). TWO-PHASE: the first call attaches and makes NOTHING — it returns a PREVIEW of the visual each post would get (the library picture, or what Scripe would make: format and direction), whether it uses Scripe AI credits, and `confirmItems` (exactly that plan), plus a `confirmationToken`. Show the user the preview and wait for their explicit yes; only then call again with `items: confirmItems` (or the same arguments) plus the token. Never confirm for the user, not even on autopilot. Library pictures attach in the confirmed call; anything Scripe makes runs in the background (about a minute, in parallel) — poll `get_draft_run` with the returned runId. A post that already has media keeps it unless `replace: true`. Scripe never generates a photo of a person: a post that wants one and has none gets a template visual, and the preview says a real photo would do better. Nothing is scheduled.
Connector
Destructive
OAuth