Jobs

A Job is Routario’s picture of one real, recurring piece of work your company does — processing invoices, keeping a product catalogue up to date, following up with quiet customers. It isn’t a single automation. It’s the whole job-to-be-done, and the tools that carry it out live together inside it.

Think of a Job as a labelled folder. Inside are the pieces that do the work:

• Flows — the automations that run when something happens (an invoice arrives, a schedule fires).
• Agents — the assistants that read, decide, and draft.
• Tables — the reference data the Job reads and writes (suppliers, cost codes, a history of what it has seen).
• Scouts — a device’s eyes, ears, or voice, when the Job needs them.

You don’t have to assemble that folder yourself. Most Jobs start from the catalog.

The catalog: ready-made Jobs

The catalog is a shelf of Jobs other people have already designed — each one a description of a process, what it produces, and the tools it’s made of. You browse it the way you’d browse an app store: open a Job to read what it does, what it needs from you, and what it will hand back.

Each catalog Job carries a maturity that decides how you start it:

• Install Job — a ready, tested Job. Installing it sets up a real, private copy in your workspace.
• Start guided setup — a Job that’s ready to install but expects a bit of configuration first; installing it and walking you through that setup are the same action.
• Draft pilot plan — an early-stage idea. Instead of installing, it opens the builder so you can shape it into a real automation.

What install actually does

Installing a Job from the catalog makes your own copy of it. Routario builds out its parts for you — the flows and tables it’s made of are created fresh in your workspace — and records what it was installed from, so you always know its origin.

Two things are true right after install, and they matter:

• It’s a draft. Nothing runs yet. An installed Job sits quietly until you finish setting it up and turn it on — so installing to take a look is always safe.
• It’s yours to change. The copy is independent. Editing it never touches the catalog or anyone else’s Job.

An installed Job usually needs a few details before it can do its work — which mailbox to watch, who signs off, which table holds your cost codes. That’s what guided setup is for, and it ends in one deliberate click: Activate.

From installed to working

A Job moves through a simple lifecycle:

• Draft — installed but not yet running. You finish setup here.
• Active — armed. Its flows fire on their triggers and schedules.
• Paused — temporarily stopped. Future runs don’t start; work already in flight finishes.
• Archived — retired.

Only an active Job runs. A draft’s flows stay disarmed no matter what would normally trigger them, so a half-configured Job can never fire by accident — the one gate is Activate, and you reach it by finishing guided setup.

Note

Values you set during setup (the mailbox, the approver, the table) are saved on the Job itself. Flows inside the Job read them through the {{ job.inputs.* }} variable — so one place holds the Job’s configuration, and changing it there changes it everywhere the Job uses it.

Where to go next

• Set up and activate an installed Job — the step-by-step walkthrough of guided setup.
• Add a manual action button to a Job — give a Job a one-press button for an on-demand task.
• Anatomy of a flow — how the flows inside a Job are built and run.