Refresh a batch of stale posts with AI-written intros each week

Every week, FlowMattic reads your sheet of ageing posts, and an AI agent drafts a fresh two to three sentence intro for each one and emails it to your editor, with a Slack note per post.

Schedule

Google Sheets

Iterator

AI Agent

Slack

Download this workflow Browse more workflows

6 steps Setup ~12 min Used on 777 sites Content Ops Free to import

The Refresh a batch of stale posts with AI-written intros each week workflow on the FlowMattic canvas, with 6 steps across Schedule, Google Sheets, Iterator, AI Agent, Email, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Older posts often still rank and get traffic, but their openings can feel dated. Rewriting intros one by one is slow, so this workflow prepares the drafts in a weekly batch and leaves the final edit to a person. It doesn't change anything on your site by itself.

The Schedule trigger runs once a week. A Google Sheets Get Rows step then reads the rows of the sheet you choose, where you keep the posts to refresh, with their titles and URLs. It ships without a sheet picked, so set that after import.

An Iterator takes the rows one at a time. For each post, the AI Agent receives the title and URL and is told to act as an editor: write a fresh, engaging intro of two to three sentences, then email it to the editor with the title and URL. Its Send Email tool has no recipient set, so enter your editor's address. After the agent, a Slack message notes that a refresh intro was drafted for that title.

Each weekly run works through every row in the sheet again. Keep only this week's batch in it, or remove posts once their new intro is published, or the editor gets the same drafts again next week.

Quarterly content refresh for a blog

A content manager lists ten older posts that still get search traffic, and the editor receives a new intro for each by email on Monday to paste in.

Agency maintenance for client sites

An agency keeps one sheet per client of posts due for an update and uses the weekly drafts as a starting point for its refresh work.

Tracking refresh work in Slack

A small editorial team sees a Slack note for each post in the batch, so everyone knows which intros are waiting in the editor's inbox.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Schedule Every Week
Starts the workflow once a week on the day and time you set. It carries no post data; it only decides when the batch runs.
Step 2Action
Google Sheets Get Rows
Reads the rows from your Google Sheets list of posts to refresh. Choose the spreadsheet and sheet after import; each row should hold a post title and URL.
Step 3Logic
Iterator Loop Through Array
Loops through the rows from the sheet one by one, so the agent and the Slack step run once for each post in the batch.
Step 4Action
AI Agent Execute Agent
Runs an AI agent on GPT-4o, told to write a fresh two to three sentence intro for the current post and email it to the editor with the post title and URL.
Step 5Tool
Email Send Email
Agent tool that emails the new intro to your editor. The agent writes the subject and body; the recipient isn't set in the template, so add the editor's address.
Step 6Action
Slack Send Channel Message
Posts a Slack note saying a refresh intro was drafted for the post title. One note goes out per row; select the channel when you configure it.

What you need

FlowMatticCore
Google Sheets AccountAccount
AI ProviderAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Give the agent the FlowMattic Browser tool so it can open each post's URL and read the current article. As imported, it only has the title and URL to work from.
Name the sheet's columns title and url, or remap the agent's input after a test run, so the Iterator passes the right values into the prompt.
Clear the sheet after each batch, or move done posts to another tab, because every weekly run reads all rows again.
Add your style rules to the agent's instructions, such as no questions as openers or always name the main keyword, so the drafts need less editing.

Questions about this workflow

Does this workflow update the old WordPress posts itself?

No. The agent emails each new intro to your editor, who pastes it into the post. Nothing on the site is changed by the workflow.

Will the same posts get new intros every week?

Yes, if they stay in the sheet. Each run reads every row and drafts an intro for each one, so remove refreshed posts or replace the list before the next run.

Can the AI agent read the existing post before rewriting its intro?

Not as imported. It receives only the post title and URL from the sheet. Add the FlowMattic Browser tool to the agent so it can open the URL and read the page.

How many stale posts can one weekly batch hold?

The Iterator runs the agent once per row the Get Rows step returns. Start with a small sheet, check Task History after the first run, and grow the list from there.