Use the Document source in Auto Post to turn an uploaded file into a publishing workflow. Choose social or blog destinations, keep ready-made content as written, or use AI to adapt it.
Open the Auto Post dashboard and choose Documents. Sign in and select the workspace that owns the destinations you intend to use.
Supported files
The document picker accepts CSV, JSON, TXT, Markdown (.md), and Word (.docx). Prepare content in the format you intend to publish and check the parsed records before activating the workflow.
Uploads are limited to 2 MB, up to 500 records and up to 8,000 characters per record. Review the parsed preview rather than assuming every spreadsheet or Word layout becomes a separate record. This workflow stores the uploaded source; editing the original file on your computer does not update it automatically.
Set up the workflow
- Open Auto Post and choose the social or blog destination and the Document source.
- Upload your file and review the extracted content. Choose how to group it, such as one post per record or the whole document as one post.
- Choose Ready-made posts to preserve prepared content, or Extract and rewrite when you want AI to adapt it. Review the resulting copy.
- Select eligible connected channels, set the schedule, and configure publishing presets and media.
- Review the workflow, time zone, and any end date, then activate it when ready. Generated posts still follow required workspace approvals.
For a workflow using separate records, each scheduled occurrence publishes the next unused record from the uploaded document. Check the preview and workflow history instead of assuming every file layout produces the intended posts.
When all records have been used, the occurrence skips without AI generation or source-failure retries. Replace the file to continue, or pause the finished workflow to stop future checks. See Auto Post timing and resource use for the differences between documents, RSS, videos, articles and prompts.
When to use it
- Publish a prepared series of tips or announcements over time.
- Adapt a document into a sequence of social posts.
- Turn records into blog content for supported connected blog destinations.
Prepare a simple series
For example, a TXT document can contain one short tip, a blank line, then the next tip. Choose grouping that matches the file and confirm the preview contains the intended records in the intended order. Use a whole-document group only when you want one record from the whole file.
Ready-made posts preserves the prepared text, subject to destination formatting and limits. Extract and rewrite lets AI adapt each record, so review its factual meaning and attribution. AI text rewriting, selected AI media and destination publishing can use different allowances; ready-made text does not make selected AI images free.
Replace a source or finish a series
Use the workflow's document replacement action when the saved source needs to change. Review whether you want to continue the record history or explicitly restart from the beginning; restarting can prepare previously used content again. Check delivery history before making that choice, particularly if any publication outcome is uncertain.
When the series is finished, pause the workflow to stop further scheduled checks. If the source is missing or invalid, correct the file rather than repeatedly trying the same publication. Required approvals, connected-channel access and provider limits still apply to every prepared record.
For row-by-row bulk scheduling with destinations and dates in a spreadsheet, explore Bulk Post and Google Sheets publishing. For source-driven automation, see the other Auto Post workflows.