Automation library · Hiring

And extract job postings with OpenRouter

Started by another system calling it. It calls services over plain HTTP rather than through connectors. It hands the judgement calls to OpenRouter. 10 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: OpenRouter

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 3Model 2Logic 5

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

  1. 1OpenRouter Chat Model1Lm Chat Open RouterModel
  2. 2WebhookWebhookStarts it
  3. 3When Executed by Another WorkflowExecute Workflow triggerStarts it
  4. 4Split Out JobsInformation ExtractorModel
  5. 5Set DataSetLogic
  6. 6Split Out1Split OutLogic
  7. 7Deep Jobs Research AgentExecute WorkflowLogic
  8. 8If Source is WebhookIfLogic
  9. 9Respond to WebhookRespond To WebhookStarts it
  10. 10Set OutputSetLogic

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
OpenRouter

Questions

What does it need to run?

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

What starts it?

It starts on another system calling it.

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. 10 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 10 steps before you point it at anything that matters.