AI OmniBlocks

What OmniBlocks are in Aimogen Pro, how a workflow of chained blocks executes, and when to reach for one instead of a bulk rule.

OmniBlocks are Aimogen Pro workflow builder. A workflow is an ordered list of blocks; each block does one thing and publishes its result as a placeholder that later blocks can use.

Fifty-seven block types are available, covering AI generation, scraping, product data, media, logic, triggers and output.

OmniBlocks Tutorial: Aimogen Game Changer Update To Allow Creation Of Unmatched ContentAn introduction to building workflows.Watch on YouTube

When to use an OmniBlock#

The bulk creators implement one fixed pipeline very well. OmniBlocks exist for everything else.

Situation	Tool
Articles from a keyword list	Bulk creator
Scrape three competitor pages, compare them, publish a comparison	OmniBlock
Read an RSS feed, summarise each item, post to a social network	OmniBlock
Take a webhook from an external system and create a product	OmniBlock
Generate a report every Monday and email it	OmniBlock
Run a workflow when a chatbot user asks for something	OmniBlock

If you can describe the job as a sequence of steps with data flowing between them, it is an OmniBlock.

How a workflow executes#

Blocks run in order, top to bottom.
Each block writes its output into a placeholder named after its type and its block ID.
Later blocks reference earlier output through those placeholders.
Logic blocks can skip, jump or stop.
Output blocks save a post, send an email, call a webhook or post to a social network.

A minimal four-block workflow — the default template shipped with the plugin:

#	Block	Does
1	`ai_text`	Writes a title for `%%keyword%%`
2	`ai_text`	Writes an article for `%%keyword%%`
3	`dalle_ai_image`	Generates a featured image
4	`save_post`	Publishes, using `%%ai_text_1%%` as the title, `%%ai_text_2%%` as the content and `%%dalle_image_3%%` as the featured image

In this section#

Building a workflowCreating, ordering and configuring blocks. Block referenceAll 57 block types with their output placeholders. Passing data between blocksHow block placeholders are named and referenced. Triggers and webhooksStarting a workflow from an event, a webhook, a form or the chatbot. Logic and flow controlConditionals, jumps, waits and early exit. Running and schedulingManual runs, schedules and caching. TroubleshootingDiagnosing a workflow that stops or produces nothing.

Global settings#

Settings › OmniBlocks

Setting	What it does
`Enable OmniBlocks Webhook Functionality`	Enables the webhook listener block and its REST route. Off by default
`Enable OmniBlocks Result Caching`	Caches block results so repeated runs with identical inputs do not re-call the AI
`OmniBlocks Temperature`, `Top_p`, `Presence Penalty`, `Frequency Penalty`	Defaults for AI blocks
`Clear OmniBlock Data`	Clears stored workflow state
`Don't Render OmniBlock Shortcodes`	Stops placeholder rendering, for debugging

Default templates#

A set of example workflows is imported on first activation, from the plugin defaults/ folder. They are ordinary editable workflows — start from one rather than a blank canvas.

Bulk actions on the OmniBlocks list let you enable, disable, duplicate or delete several at once.

AI content creation
AI Agents — when the sequence should be decided by the AI rather than by you

Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.