Blogger
CMS & ContentPublish to Blogger with AI agents. Agents create, update, publish, and revert posts, manage pages, moderate comments including spam handling, and read page view stats across every blog on the account.
What This Integration Enables
Blogger's API has a default worth respecting: Create Post publishes immediately unless you explicitly save as draft. That single fact should shape every automated publishing workflow you build on it. FlowRunner agents treat Blogger as the last mile of a content pipeline, drafting always, publishing only after a person has seen the post, and handling everything around the article that nobody budgets time for: the comment queue, the static pages, the traffic numbers. The connector covers the full surface: posts through their whole lifecycle including scheduling and reverting to draft, static pages, comment moderation with four distinct outcomes, and page view statistics. - Publish approved articles on a schedule with HTML content, labels, and geo-location - Draft first, publish second: agents create unpublished drafts and Publish Post goes live only after review - Run comment moderation as a continuous process with approve, spam, redact, and delete as separate tools - Keep About, Contact, and policy pages current across every blog on the account - Log page views to a dashboard or sheet so content decisions have data behind them
Without FlowRunner
With FlowRunner
Use Case Scenarios
The editorial calendar that executes itself
A content team plans posts in [Google Sheets](/integrations/google-sheets). When a row flips to approved, the agent runs Search Posts to confirm the topic does not cannibalize an existing live post, then Create Post with Save As Draft, carrying over the HTML body and label taxonomy. The editor gets the draft link in [Slack](/integrations/slack), reviews it in place, and replies approve. Publish Post schedules it for the next open slot on the calendar. The team writes; the pipeline files, checks, and ships.
Comment moderation with a spam floor and a human ceiling
Every hour, List Blog Comments pulls everything pending across the blog. The agent classifies each comment: link-stuffed junk goes straight to Mark Comment As Spam, plain questions from readers are approved with Approve Comment, and anything borderline, a complaint, a legal-sounding threat, a comment naming an employee, goes to the moderator with full context and the thread it belongs to. The moderator picks the outcome, including Remove Comment Content when the record should stay but the words should not. The queue stays near zero without the blog ever auto-hiding a genuine reader.
The monthly traffic story, assembled
On the first of the month, the agent calls List My Blogs, then Get Page Views for each blog across the 7 day, 30 day, and all-time ranges. It joins the numbers to the posts published that month via List Posts, appends the lot to a reporting sheet, and posts a short digest to the content channel: what shipped, what moved, what flatlined. When the team debates what to write next, the argument starts from the same numbers.
Human-in-Loop Highlight
Publish Post is the write that reaches the public, and on Blogger the danger is sharper than usual because Create Post defaults to publishing immediately. A pipeline that generates or transforms content and pushes it straight to a live blog is one bad generation away from a public embarrassment with your domain on it. So FlowRunner workflows hold the line at the draft boundary: agents create drafts, run the checks, and assemble the preview, but Publish Post fires only after a named editor has read the actual post and said yes. The same discipline covers Delete Post, which permanently removes a post and cannot be undone: an agent may nominate stale posts for removal, with traffic numbers attached, but the deletion list gets a human signature first. Reverting is cheap, Revert Post To Draft exists for a reason, but unpublishing something a reader already screenshotted is not a rollback.
Agent Capabilities
28 actionsUsers
1- Get Current User Retrieves the authenticated user's profile, ID, display name, and profile URL. Used to confirm which Google account is connected before workflows write anything.
Blogs
3- List My Blogs Lists every blog the user owns with names, URLs, IDs, and post counts. The starting point for multi-blog workflows.
- Get Blog Retrieves one blog by numeric ID with its metadata, locale, and counts.
- Get Blog By URL Resolves a blog from its public address when you have the link but not the ID.
Posts
10- List Posts Lists posts with filters for status, labels, and date range, ordered by published or updated date. Draft and scheduled filtering requires author or admin access.
- Search Posts Full-text searches live posts by keyword. The overlap check that runs before any new post is created.
- Get Post Retrieves one post's title, HTML content, labels, timestamps, comment count, and URL. The View option unlocks draft and scheduled posts.
- Get Post By Path Resolves a post from its permalink path when a workflow starts from a URL instead of an ID.
- Create Post Creates a post with HTML content, labels, and optional geo-location. Publishes immediately by default: production workflows enable Save As Draft and let review happen first.
- Update Post Fully replaces a post's title and content. Omitted fields are cleared, so reach for Patch Post unless you mean to resupply everything.
- Patch Post Updates only the fields you provide. The safe default for tweaking a title, swapping a label, or fixing a paragraph.
- Delete Post Permanently deletes a post. Cannot be undone, which is why deletion lists get human sign-off on this page.
- Publish Post Publishes a draft, immediately or scheduled for a future date and time. The action this page's human gate protects.
- Revert Post To Draft Pulls a published post from public view without deleting it. The cheap undo that makes bold publishing schedules survivable.
Pages
6- List Pages Lists a blog's static pages with status filters. Pages live outside the chronological feed.
- Get Page Retrieves one static page's title, HTML content, URL, and status.
- Create Page Creates a static page, published immediately by default or saved as draft.
- Update Page Fully replaces a page's title and content. Omitted fields are cleared.
- Patch Page Updates only the provided fields on a page. Used for keeping About and policy pages current without rewriting them.
- Delete Page Permanently deletes a static page. Cannot be undone.
Comments
7- List Comments Lists comments on a single post, filterable by status and date range. Pending and spam views require author or admin access.
- List Blog Comments Lists comments across the whole blog in one moderation view. The sweep action behind continuous moderation.
- Get Comment Retrieves one comment with its content, author, status, and parent post.
- Approve Comment Marks a pending or spam-flagged comment live. The action for real readers caught in the filter.
- Mark Comment As Spam Moves a comment to the spam queue and out of public view.
- Remove Comment Content Redacts a comment's body while keeping the record in place. The middle path when the thread matters but the words cannot stay.
- Delete Comment Permanently deletes a comment. Cannot be undone, so escalation-worthy comments get a human decision before this fires.
Analytics
1- Get Page Views Retrieves view counts for a blog over 7 day, 30 day, or all-time ranges. Owner only, and the raw material for scheduled traffic reporting.
Frequently Asked Questions
What can FlowRunner do with Blogger?
FlowRunner agents can run Get Current User, List My Blogs, and Get Blog in Blogger, plus 25 more actions.
Does connecting Blogger to FlowRunner require OAuth?
Yes. Blogger connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Blogger trigger a FlowRunner workflow automatically?
Blogger doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Blogger
$100 in credits. No card required. Connect in minutes.