Automation library · AI assistants

Rank Math bulk title & description optimizer for WordPress

Started by an event in a connected app, and works across WordPress. It hands the judgement calls to OpenRouter. 12 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

MediumCalls a model: OpenRouter

12 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Model 3Logic 5Service 3

The steps in the order they run, from what starts it.

  1. 1When clicking ‘Execute workflow’Manual triggerStarts it
  2. 2OpenRouter Chat ModelLm Chat Open RouterModel
  3. 3Structured Output ParserOutput Parser StructuredModel
  4. 4settingsSetLogic
  5. 5Create Meta InfosChain LlmModel
  6. 6Get Posts IDHttp RequestService
  7. 7Update Post MetasHttp RequestService
  8. 8LimitLimitLogic
  9. 9PostSplit In BatchesLogic
  10. 10Finish 🚀No OpLogic
  11. 11Get postWordpressService
  12. 12Should I RewriteIfLogic

How it's built

Starts on
An event in a connected app
Steps
12, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
WordPress
Model
OpenRouter

Questions

What does it need to run?

An n8n account, plus your own WordPress account, and a key for OpenRouter. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

Yes. It calls OpenRouter. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 12 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.