Blogger - Drive Automation

Drive Automation checks a Google Drive folder and creates or updates content on your Blogger blog. Adding a document does not automatically make it public. New posts default to Draft unless the document sets another publication outcome.

Use Frontmatter in your Google Docs to set the title, labels, publish status, and more on a per-document basis.

Tenwrite checks your Drive folder once every hour. New Google Docs become new Blogger posts. Docs that have changed since the last run sync back to the existing post.

Only Google Docs in the folder root are picked up — files inside subfolders are ignored.

For a new post, no publication settings means Draft. Use frontmatter in the Google Doc when you want to set the outcome:

• Keep as draft: saves the content without making it public, even if the document has a future date.
• Publish without a future date: makes the content public when the automation processes it successfully.
• Scheduled with a valid future date: saves a schedule for that time. A future date with Publication set to Automatic also schedules the post.

Scheduling uses your Tenwrite account timezone. Blogger pages cannot be scheduled. If an existing post has no new publication settings, updating its content keeps its current publication state; it does not reset a published post to Draft.

There is no confirmation dialog for each document in an automation run. Review the folder contents and frontmatter before enabling it. Start with one manual draft if you have not checked an export yet.

Open the Tenwrite add-on or Web Dashboard, go to Blogger > Automations, and make sure you’re on the Drive tab.

Click New Automation (or Create Drive Automation if no automations exist yet).

You need a folder in Google Drive that Tenwrite can read. Create a new one or use an existing folder.

Create the folder:

In Google Drive, click + New and select New folder.

Share it with Tenwrite:

Click the three-dot menu on the folder, choose Share > Share, and enter automation@tenwrite-gcp.iam.gserviceaccount.com. Set the role to Viewer and click Share. Click Share anyway if prompted.

Copy the folder link:

Open the three-dot menu again and choose Share > Copy link. You’ll paste this into Tenwrite.

Choose the Blogger Site and enter the Google Drive Folder URL. Set document-specific labels and publication settings in frontmatter.

Enable automation immediately is selected by default. Clear it if you are still preparing the folder; you can enable the automation later from its row. Click Create Automation to save it. If you leave the option selected, the automation can process the folder on its next run.

1. Prepare one new test Google Doc in the shared folder, with no earlier export to this destination. Choose Keep as draft in its frontmatter, or use a document without publication settings.
2. Save the automation with Enable automation immediately cleared. This leaves its regular schedule Disabled while you test.
3. Check the destination and document settings, then click Run Now on that automation’s row. This starts a real run; it is not a preview. You do not need to enable the regular schedule first.
4. Wait after Automation queued. appears. The row can show Queued, then Running. These states mean work is pending or in progress, not that a post has already been created.
5. When the run finishes, check its last-run time, result, and any warning or error message. If the result has not refreshed, refresh the list before trying again.
6. Open Blogger > Posts and find the resulting draft. Open it in Blogger and check its status, content, images, and links. If there was an error, check for any content that was created before retrying.
7. Leave the schedule disabled while testing. When you want repeated runs, click Enable and check Next run at. To publish or schedule later, review the document’s publication settings before the next run.

Run Now does not change the saved schedule. It uses the same document settings and plan limits as a scheduled run. A successful run can create a draft, update an existing item, or make no changes when nothing new needs processing.

• Status: Enabled or Disabled describes the regular schedule. A plan or destination block is shown separately from that saved setting.
• Queued / Running: a run is waiting or being processed. Run Now is unavailable until it finishes.
• Next run at: the next regular scheduled attempt, shown in your browser’s local time. A disabled schedule shows Schedule disabled. An enabled but blocked schedule shows Scheduled attempts are blocked.
• Last run: check the time and result, then read any warning or error text. A previous Success result does not mean the schedule is currently enabled.
• Runs, Posts, Failed: cumulative counts. The Posts count shows created items, not every update and not just public posts.

If Next run at says Unavailable, refresh the list and check the status. That message alone does not mean an export failed. See run controls and status messages for the shared controls.

See the WordPress example of the same Run Now and timing controls.

Disabled means the regular schedule is paused. Use Run Now for a single run, or Enable to resume the schedule.

Blocked by your current plan means the plan does not allow this automation to run. Open Review your plan. Destination inactive or unavailable means the target needs attention; open Review destinations and check that it is connected, accessible, and active within your site allowance. Run Now is unavailable while a block applies.

A block keeps the saved enabled setting. If the row says Schedule remains enabled, scheduled runs can resume when the block is resolved. Click Disable first if you want to keep the automation paused. If it says Schedule is disabled, use Enable only when you are ready.

• If the row is Queued or Running, wait for that run instead of starting another.
• If it is blocked, follow Review your plan or Review destinations. Enabling the schedule does not remove a block.
• If the schedule is merely Disabled, Run Now can still be used. Enable is only needed for repeated scheduled runs.
• If starting the run returns an error, read that message before retrying. If a queued or running state does not clear, contact support with the automation ID and message.

• Share the folder with automation@tenwrite-gcp.iam.gserviceaccount.com as Viewer, and check that the automation has the correct folder URL.
• Use native Google Docs in the folder root. Drive automation skips Word files, PDFs, local uploads, and files inside subfolders.
• Check that the test Doc inherits access from the folder. Connecting Google files for a manual export does not replace the automation account’s folder access.

Check Blogger > Posts and the destination blog for a draft or scheduled item. A successful export does not always make content public. Read the document’s publication settings and publication outcomes.

The run may also have found no new or changed documents. Check the existing item before creating another automation or using New Export.

Read the message beside the last-run result. A warning can accompany a completed export; check the resulting content and any skipped or unchanged settings. An error can occur after some content has been processed, so inspect existing items before retrying.

• Publication settings: correct invalid frontmatter or scheduling dates. Use the frontmatter guide and check the outcome with a manual draft test if needed.
• Plan or file limits: review your subscription and the per-run Drive file allowance. Do not assume every file in a large folder will be handled in one run.
• Destination access: For a Blogger access error, use Reconnect Blogger in the web app and choose the Google account matching your Tenwrite account. That account must have access to the blog. For the installed add-on, close and reopen it instead. See Google connections.

After fixing the reported problem, use Run Now on the same automation to test again. If the cause is unclear, send the automation ID, destination URL, last-run time, and error message to support@tenwrite.com.

Edit the original Google Doc in the shared folder. Copies have different file IDs and are treated as separate documents. Confirm that the document is in the folder root, then use Run Now or wait for the Next run at time. Check the latest result for errors or plan limits before retrying.

• Document Frontmatter
• Sheet Automation
• Export Google Docs to Blogger

Need help? Contact support@tenwrite.com.