Use this when an AI agent needs to create, queue, or schedule a Postly post through the publishing pipeline, including social channels and email/newsletter targets. If media was attached, generated, selected, or supplied as a temporary/local file reference, pass it in media_file, media_file_2, and so on; the server uploads those files to Postly storage inside this same create action. If the user wants generated media published or scheduled, complete the generation and post creation in the same turn so the temporary file reference does not expire. For multi-platform posts, first resolve targets, call postly_get_channel_schema for unfamiliar social platforms, validate content, generate safe platform_posts metadata, and apply defaults. Email/newsletter targets require email_subject and body text. Ask the user only for missing media/assets, business facts, or compliance-sensitive choices that cannot be inferred. If the user asks to publish everywhere and some platforms remain blocked, offer to publish to ready channels while skipping blocked ones.