Use Automations to run recurring AI Puffer tasks from WordPress. A task can create content, index WordPress content into a vector store, rewrite existing content, or reply to comments.In WordPress admin, go to AI Puffer > Automations.Set up the AI provider, image provider, vector store, or source connection required by the task you want to run. If the Automations menu is not visible, check that the module is enabled and that your WordPress role has access to it.
Create Content
Create posts from topics, CSV, RSS, URLs, and Sheets.
Optimize
Rewrite existing content and update products.
Content Indexing
Add WordPress content to vector stores on a schedule.
Comment Replies
Generate replies for approved WordPress comments.
Settings
Configure schedule, model, prompts, SEO, images, and knowledge.
A task-specific cron event runs on the selected frequency.
The task finds matching work and adds items to the queue.
The main queue processor handles pending queue items in batches.
Each queue item becomes Completed or Failed.
The queue processor handles up to 5 pending items per run. If more items remain, AI Puffer schedules another queue run about 30 seconds later.
WordPress cron depends on site traffic unless you run a real server cron. If site traffic is low, scheduled tasks can run late. If DISABLE_WP_CRON is enabled, set up a server cron job for WordPress.
RSS Feed creates posts from feed items.To create an RSS Feed automation:
Click New Task.
Select RSS Feed.
Add one RSS feed URL per line.
Add include keywords if only matching feed items should be used.
Add exclude keywords if matching feed items should be skipped.
Set the model, prompts, publishing, image, and SEO options.
Set the task frequency.
Save the task.
Scheduled RSS tasks use the task’s last run time and RSS history to avoid processing the same feed item again. Run Now checks recent feed items and still skips items that are already in the task history.
Google Sheets tasks create posts from spreadsheet rows.Open the sample Google Sheet, make a copy, and keep the same column order.AI Puffer reads columns A:G.
Column
Field
Notes
A
Topic
Required.
B
Keywords
Optional.
C
Category ID
Optional.
D
Author Login
Optional.
E
Post Type
Optional.
F
Schedule Date
Optional. Use YYYY-MM-DD HH:MM.
G
Status
Leave empty for rows that should be processed.
Column G controls whether a row is processed. If column G has any value, AI Puffer skips that row.
Rows are processed only when column A has a topic and column G is empty. After a post is created, AI Puffer writes Processed on ... to column G so the row is not used again.If you use a header row, put a value in column G for that row, such as Status, so it is skipped.
Before creating the task, set up Google access. AI Puffer uses a Google Cloud to read rows and write the processed status.
Use Rewrite Content to update posts, pages, or custom post types on a schedule.
Rewrite Content updates WordPress content directly. Test with one small task before enabling a broad scheduled rewrite.
Choose which content the task can update.
Filter
Notes
Post Types
Required. Select one or more post types.
Categories
Optional. Applies to category-supported content.
Authors
Optional. Limits updates to selected authors.
Statuses
Published, Draft, or Pending Review.
Use Queue all matching content now to enqueue the matching content one time when the task is saved. If this option is off, scheduled runs process content that becomes eligible later.Select at least one field to update. Each selected field has its own prompt.
Field
What AI Puffer updates
Title
WordPress post title.
Excerpt
WordPress post excerpt.
Content
WordPress post content.
Meta Description
SEO meta description in supported SEO plugins.
Use placeholders in rewrite prompts to include existing post data.
Post placeholders
Placeholder
Value
{original_title}
Existing post title.
{original_content}
Existing post content without shortcodes and HTML.
{original_excerpt}
Existing excerpt.
{original_meta_description}
Existing meta description or excerpt fallback.
{original_focus_keyword}
Existing focus keyword when available.
{original_tags}
Existing tags.
{categories}
Existing categories.
Rewrite Content can optionally use vector context from the right-side Advanced card.
Provider
Required setup
OpenAI
Select OpenAI Vector Stores.
Pinecone
Select a Pinecone index and embedding model.
Qdrant
Select a Qdrant collection and embedding model.
Chroma
Select a Chroma collection and embedding model.
The task searches the selected knowledge source using the post title and adds matching context to the AI request.
For Pinecone, Qdrant, and Chroma, use the same that was used when the data was added.
To create a Rewrite Content automation:
Click New Task.
Select Rewrite Content.
Select the post types to update.
Add category, author, or status filters if needed.
Choose whether to queue all matching content now.
Select the fields AI Puffer should update.
Review the prompt for each selected field.
In Advanced, set Context if the rewrite should use stored knowledge.
Set the task frequency.
Save the task.
When the task runs, AI Puffer finds matching content, queues it, and updates only the fields you selected.Run Now queues matching content that is not already present in that task’s queue history.
Use Rewrite Content with the product post type to update WooCommerce product copy on a schedule.
The task can update these product fields:
Field
What AI Puffer updates
Title
Product name.
Excerpt
Product excerpt or short description.
Content
Main product description.
Meta Description
SEO meta description in supported SEO plugins.
Price, SKU, stock, dimensions, purchase note, categories, and attributes can be used in prompts as source data. AI Puffer does not change those WooCommerce product fields in this task.Product prompts can use the normal post placeholders and these WooCommerce placeholders:
Placeholder
Value
{price}
Product price.
{regular_price}
Product regular price.
{sku}
Product SKU.
{attributes}
Product attributes.
{stock_quantity}
Stock quantity.
{stock_status}
Stock status.
{weight}
Product weight.
{length}
Product length.
{width}
Product width.
{height}
Product height.
{purchase_note}
Product purchase note.
{product_categories}
Product categories.
To create a WooCommerce product update automation:
Click New Task.
Select Rewrite Content.
Select product under Post Types.
Add category, author, or status filters if needed.
Choose whether to queue matching products now.
Select the product fields AI Puffer should update.
Review the prompt for each selected field.
In Advanced, set Context if product copy should use stored product or business information.
Use Content Indexing to add WordPress content to a vector store for later retrieval.
Destination
Required setup
OpenAI
Select an OpenAI Vector Store.
Pinecone
Select a Pinecone index and embedding provider/model.
Qdrant
Select a Qdrant collection and embedding provider/model.
Chroma
Select a Chroma collection and embedding provider/model.
Pinecone, Qdrant, and Chroma require an because AI Puffer needs to create embeddings before writing vectors.
For Pinecone, Qdrant, and Chroma, the index or collection dimension must match the embedding model.
Content selection settings:
Setting
What it does
Post Types
Selects the public post types to index.
Queue existing content now
Queues matching published content for initial indexing.
Auto-index new and updated content
Keeps the vector store updated when selected content changes.
Frequency
Controls how often the task checks for work.
Content Indexing only queues published content.
To create a Content Indexing automation:
Click New Task.
Select Content Indexing.
Choose OpenAI, Pinecone, Qdrant, or Chroma as the destination.
Select the vector store, index, or collection.
For Pinecone, Qdrant, or Chroma, select the embedding provider and model.
Select the public post types to index.
Choose whether to queue existing content now.
Choose whether new and updated content should be indexed automatically.
Set the task frequency.
Save the task.
Queue all existing content now creates an initial batch for matching published content. AI Puffer queues existing content in batches of 200 posts. After the initial queueing pass finishes, the one-time flag is turned off for the task.Run Now queues all matching published content again.Auto-index new and updated content checks posts modified after the task’s last run time. Use this when the vector store should stay in sync with published WordPress content.
Use Comment Replies to draft and publish replies to WordPress comments.
Setting
What it does
Post Types
Selects which comment areas the task monitors.
Approve Immediately
Inserts the AI reply as an approved comment.
Hold for Moderation
Inserts the AI reply as an unapproved comment.
Do not reply to other replies
Limits the task to top-level comments.
Include keywords
Replies only when the comment contains at least one keyword.
Exclude keywords
Skips comments that contain any excluded keyword.
Use placeholders to include the original comment and post title in the reply prompt.
Placeholder
Value
{comment_content}
Original comment text.
{comment_author}
Original comment author.
{post_title}
Title of the commented post.
To create a Comment Replies automation:
Click New Task.
Select Comment Replies.
Select the post types to monitor.
Choose whether to reply only to top-level comments.
Choose whether replies should be approved immediately or held for moderation.
Add include or exclude keywords if needed.
Review the reply prompt.
Select the model.
Set the task frequency.
Save the task.
Scheduled runs check approved comments. Each run queues up to 50 matching comments.AI Puffer checks whether a comment is already queued or already has a reply from the same task before adding it again.Replies are inserted as child comments. The reply author is the post author when possible, with a fallback to the site administrator.
Task schedule controls whether the task is active and when AI Puffer checks for work. These settings are in the right-side Schedule card.
Setting
What it does
Active
Schedules the task.
Paused
Stops future scheduled runs. Existing queue items remain in the queue.
Frequency
Controls how often AI Puffer checks the task source.
Available frequencies:
Frequency
Notes
One-time
Runs once.
Every 5 Minutes
Uses a custom WordPress cron interval.
Every 15 Minutes
Uses a custom WordPress cron interval.
Every 30 Minutes
Uses a custom WordPress cron interval.
Hourly
Uses the WordPress hourly interval.
Twice Daily
Uses the WordPress twice-daily interval.
Daily
Uses the WordPress daily interval.
Weekly
Uses a custom WordPress cron interval.
Manual Entry and CSV tasks are one-time tasks. RSS Feed, Web Page, Google Sheets, Rewrite Content, Content Indexing, and Comment Replies can use recurring frequencies.The first run is scheduled shortly after the task is saved or resumed.
AI settings choose the model that writes the content.xAI can be used for text automation tasks such as content creation, rewriting, and comment replies. It can also be selected as an image source for content-writing automation tasks. It is not used for Knowledge Base indexing destinations.To set the model:
In the right-side General card, use Model to choose the provider and model.
Select Length for content creation tasks.
Click the settings icon next to Model to open Model settings.
Adjust Temperature if you want more or less variation.
Set Reasoning only for models that support it. Keep it on None for faster runs.
Setting
What it does
Model
Provider and model used by the task.
Length
Token budget for generated content.
Temperature
Response variation.
Reasoning
Reasoning effort for supported OpenAI and Ollama models.
Length values map to these token budgets:
Length
Token budget
Short
2000
Medium
4000
Long
6000
If the provider or model list is empty, configure the provider first in AI Providers.
Prompts are the instructions Automations sends to the selected model. Content creation tasks can generate a title, content, SEO fields, excerpt, tags, inline image prompt, and featured image prompt.To customize prompts:
In the right-side General card, click Customize next to Prompts.
Enable the outputs you want AI Puffer to generate.
Click the edit icon next to an output.
Select a saved prompt or edit the prompt text directly.
Use the variables shown under the editor.
Save the task and run one test item before enabling a larger task.
Output
What it creates
Title
WordPress post title.
Content
WordPress post content.
Meta Description
SEO meta description.
Focus Keyword
Focus keyword in supported SEO plugins.
Excerpt
WordPress excerpt.
Tags
WordPress tags or product tags.
Content Image
Prompt used for inline images.
Featured Image
Prompt used for the post thumbnail.
Available variables change by source.
Source
Variables to use
Manual Entry, CSV, Google Sheets
Use {topic} and {keywords}.
RSS Feed
Use {description} and {source_url}.
Web Page
Use {url_content} and {source_url}.
SEO, excerpt, tags
Use {content_summary} when the output should be based on the generated article.
AI Puffer checks required variables before generation. If a required variable is missing, the task will not run until the prompt is fixed.
Use SEO settings when generated posts should include search metadata. AI Puffer can create a meta description, focus keyword, tags, and a cleaner WordPress URL slug. Pro users can also use Smart SEO to audit and improve generated posts before each automation queue item is completed.To generate SEO output:
In the right-side General card, click Customize next to Prompts.
Enable Meta Description, Focus Keyword, or Tags.
Edit the enabled prompts if needed.
In the right-side Schedule card, click the settings icon next to Status to open Post settings.
Enable Optimize URL if AI Puffer should update the post slug.
Save and test the task.
Output
How it is saved
Meta Description
Saved to the active SEO plugin. If no supported SEO plugin is active, AI Puffer saves fallback post meta.
Focus Keyword
Saved to Yoast SEO, Rank Math, or All in One SEO.
Tags
Saved as WordPress tags or product tags.
URL
Updates the WordPress post slug when Optimize URL is enabled.
It supports Manual Entry, CSV, RSS, URL, and Google Sheets tasks.
It automatically detects the active SEO plugin.
It checks each generated post against that SEO profile.
It improves the generated draft before the post is saved.
For SEO revisions, Smart SEO may use a quality-focused model from the same AI provider selected for generation, never switches providers, and uses the selected deployment or local model for Azure and Ollama.
It tries to improve the generated draft up to 100/100.
It can run up to three SEO revisions.
If the generated post cannot reach 100/100, AI Puffer keeps the best-scoring revision.
In Automations, Smart SEO runs in the background for each queue item.
There is no live SEO score during task setup because the content does not exist yet.
After the queue item finishes, AI Puffer saves the final SEO score and Smart SEO details with the generated post.
Free users can still generate meta descriptions, focus keywords, tags, and optimized slugs.
To use Smart SEO in an automation:
Open AI Puffer > Automations.
Create or edit a content-writing task.
Configure the task source, model, prompts, publishing settings, and SEO outputs.
Enable Smart SEO.
Save the task.
Depending on the active SEO plugin profile, Smart SEO can check:
Area
Examples
Focus keyword
Title, introduction, headings, meta description, slug, and duplicate-keyword usage.
Metadata
Meta description presence and length.
Content structure
Content length, heading balance, table of contents, paragraph length, and sentence length.
Links
Internal links, outbound links, and dofollow outbound links when the active SEO plugin scores them.
Media
Image presence and focus-keyword image alt text.
Readability
Transition words, repeated sentence openings, passive voice, and reading ease where supported.
Smart SEO follows the active SEO plugin profile automatically. If more than one supported SEO plugin is active, AI Puffer chooses one profile and shows a warning in Content Writer. For predictable scores, use one SEO plugin at a time.
Some SEO plugin checks are owned by the SEO plugin itself and cannot always be fixed by AI Puffer. For example, plugin-specific premium AI checks or settings-based checks may still appear in the SEO plugin after generation.
AI Puffer saves the generated meta description to the Yoast meta description field and the generated focus keyword to the Yoast focus keyphrase field.If Optimize URL is enabled, the slug is built from the focus keyphrase when available. If there is no focus keyphrase, the post title is used.Smart SEO’s Yoast profile is tuned for Yoast SEO analysis and readability checks, including keyphrase placement, meta description length, links, image alt text, and readability signals.
AI Puffer saves the generated meta description to the Rank Math description field and the generated focus keyword to the Rank Math focus keyword field.Smart SEO’s Rank Math profile is tuned for Rank Math’s Basic SEO, Additional SEO, Title Readability, and Content Readability checks.
AI Puffer saves the generated meta description to All in One SEO and updates the focus keyphrase data used by AIOSEO.Smart SEO’s All in One SEO profile is tuned for TruSEO checks, focus keyphrase analysis, readability checks, and headline score improvements.
AI Puffer saves the generated meta description to The SEO Framework description field.The SEO Framework does not provide a native focus keyword field, so AI Puffer does not save a focus keyword for it.Smart SEO’s The SEO Framework profile focuses on title and description behavior because The SEO Framework does not provide a native focus keyword field.If none of the supported SEO plugins are active, AI Puffer still saves the meta description as fallback post meta. WordPress tags and the optimized URL slug still work without an SEO plugin.
Content creation tasks have a task schedule and a post publishing schedule. The task schedule controls when AI Puffer checks the source and queues work. The post publishing schedule controls the date used for the generated WordPress post.
Publishing mode
What it does
Publish Immediately
Creates the post with the selected post status.
Smart Schedule
Schedules generated posts starting from a selected date and spaced by hours or days.
Use Dates from Input
Reads the date from Batch Editor, Quick Paste, CSV, or Google Sheets.
Image settings can add images inside generated content, set a featured image, or both.To enable images:
In the right-side Media card, set Images to Content, Featured, or Content + Featured.
Select the image provider or model from Image source.
Click the settings icon beside Image source to open Image settings.
Set count, placement, WordPress display size, alignment, and provider options.
To change image prompts, in the right-side General card, click Customize next to Prompts and edit Content Image or Featured Image.
Mode
Result
Off
No images are generated or fetched.
Content
Adds images inside the post content.
Featured
Sets a featured image.
Content + Featured
Adds content images and sets a featured image.
Supported image sources:
Source
Setup
OpenAI
Add the OpenAI API key in AI Puffer > Settings > AI and sync image models.
Google
Add the Google API key in AI Puffer > Settings > AI and sync image models.
OpenRouter
Add the OpenRouter API key in AI Puffer > Settings > AI and sync image-capable models.
Azure
Add the Azure endpoint, API key, API version, and image deployment in AI Puffer > Settings > AI.
xAI
Add the xAI API key in AI Puffer > Settings > AI and sync image models.
Replicate
Add the Replicate API key in AI Puffer > Settings > Integrations and sync models.
Pexels
Add the Pexels API key in AI Puffer > Settings > Integrations.
Pixabay
Add the Pixabay API key in AI Puffer > Settings > Integrations.
xAI image generation uses xAI image models such as grok-imagine-image.For content images, placement controls where images appear after the post is saved.
Placement
Result
After 1st H2
Inserts the first image after the first H2 heading.
After 1st H3
Inserts the first image after the first H3 heading.
Every X H2s
Inserts images after every selected number of H2 headings.
Every X H3s
Inserts images after every selected number of H3 headings.
Every X paragraphs
Inserts images after every selected number of paragraphs.
End of content
Adds images at the end of the article.
Pexels can filter by orientation, size, and color. Pixabay can filter by orientation, type, and category.
Provider options control the generation request sent to the selected AI provider. They are separate from WordPress display settings such as image size and alignment.Only options supported by the selected provider and model are shown.
Provider
Available options
OpenAI
Canvas size, quality, output format, compression, background, moderation.
Azure
Canvas size, quality, output format, compression, background.
Google
Aspect ratio, image resolution, and person generation for supported Imagen models. Nano Banana models are included in the Google image model list.
OpenRouter
Aspect ratio and image resolution for models that support image configuration.
xAI
Aspect ratio and image resolution.
Replicate
Model-specific options from synced model schemas.
Pexels and Pixabay are stock image sources. Their filters narrow search results instead of changing an AI generation request.
For AI image providers, the image prompt controls content images and the featured image prompt controls the featured image. To edit them, in the right-side General card, click Customize next to Prompts and open Content Image or Featured Image.You can use these placeholders:
Knowledge Base lets content creation and Rewrite Content tasks use vector data from AI Puffer > Knowledge Base > Data.When enabled, AI Puffer searches the selected source and adds matching context to the generation request.To enable it:
Add data in AI Puffer > Knowledge Base > Data.
In the right-side Advanced card, set Context to OpenAI, Pinecone, Qdrant, or Chroma.
Select the vector store, index, or collection in Source.
Click the settings icon beside Source to open Context settings.
Set Results Limit. For content creation tasks, you can also set Confidence Threshold.
For Pinecone, Qdrant, or Chroma, select the embedding provider and model in Context settings.
Save and test the task.
Provider
Required setup
OpenAI
Select one or more OpenAI Vector Stores.
Pinecone
Select a Pinecone index and the embedding model used when the data was added.
Qdrant
Select a Qdrant collection and the embedding model used when the data was added.
Chroma
Select a Chroma collection and the embedding model used when the data was added.
For Pinecone, Qdrant, and Chroma, use the same embedding model when adding data and when selecting Context in an automation task.
Pinecone stores vectors in an index. AI Puffer creates and searches those vectors with the embedding model you choose.The Pinecone index dimension must match the embedding model. For example, if your index is 3072 dimensions, use a 3072-dimension embedding model.To prepare an index:
Add your Pinecone credentials in AI Puffer > Settings > Integrations.
Go to AI Puffer > Knowledge Base > Stores.
Select Pinecone as the provider.
Select the embedding model you want to use.
Click Create Store.
Enter an index name and use the dimension for the selected embedding model.
Create the index, then add data with the same embedding model.
To use it in Automations:
Create or edit the automation task.
In the right-side Advanced card, set Context to Pinecone.
Select the Pinecone index in Source.
Click the settings icon beside Source to open Context settings.
Select the same embedding provider and model used when you added the data.
Adjust Results Limit. Content creation tasks also show Confidence Threshold.
Qdrant stores vectors in a collection. AI Puffer creates and searches those vectors with the embedding model you choose.The Qdrant collection size must match the embedding model. For example, if your collection is 3072 dimensions, use a 3072-dimension embedding model.To prepare a collection:
Add your Qdrant URL and API key in AI Puffer > Settings > Integrations.
Go to AI Puffer > Knowledge Base > Stores.
Select Qdrant as the provider.
Select the embedding model you want to use.
Click Create Store.
Enter a collection name and use the dimension for the selected embedding model.
Create the collection, then add data with the same embedding model.
To use it in Automations:
Create or edit the automation task.
In the right-side Advanced card, set Context to Qdrant.
Select the Qdrant collection in Source.
Click the settings icon beside Source to open Context settings.
Select the same embedding provider and model used when you added the data.
Adjust Results Limit. Content creation tasks also show Confidence Threshold.
Chroma stores vectors in a collection. AI Puffer creates and searches those vectors with the embedding model you choose.Chroma collections do not require a dimension when they are created in AI Puffer, but stored vectors still need a consistent dimension.To prepare a collection:
Add your Chroma endpoint, tenant, database, and API key in AI Puffer > Settings > Integrations.
Go to AI Puffer > Knowledge Base > Stores.
Select Chroma as the provider.
Click Create Store.
Enter a collection name.
Create the collection, then add data with the same embedding model.
To use it in Automations:
Create or edit the automation task.
In the right-side Advanced card, set Context to Chroma.
Select the Chroma collection in Source.
Click the settings icon beside Source to open Context settings.
Select the same embedding provider and model used when you added the data.
Adjust Results Limit. Content creation tasks also show Confidence Threshold.
Automations can send task results to Connected Apps and webhooks.
Event
When it fires
content.generated
After a content creation task creates a post.
task.item_completed
After a queue item finishes successfully.
Use these events when another system needs the generated post, task result, or queue item details. Recipe templates include generated content or completed task notifications for apps such as Slack, Notion, Zapier, and Make.