Scheduled jobs

Done before you open your laptop.

Write the job once and say when. It runs at 02:00 with nobody watching. The finished work is on your desk at 08:00.

Last night22:00 → 09:00

08:00 You open your laptop

Six jobs. One hour and nine minutes of work. One thing left for you.

Four triggers can start a task

One of them is a clock. The other three exist because work does not always arrive on the hour.

Five fields, read in your own timezone. Or one date, for a job that runs once and then retires itself.

02***

Every day at 02:00Europe/Rome

Runs once · 30 Sep, 09:00

A Slack message
Somebody posts in the channel. The job starts on that message and answers in the same thread.
#finance · Priya 23:38
The Stripe export for August is in the folder.
Job started on that message
An API call from another system
Your app, your CRM, your billing — anything that can send one HTTP request.
POST/v1/events/{trigger}202
Queued. A retry never runs it twice.
Someone presses run
The same job and the same instruction, off the schedule, right now.
Last run 06:30 · 22 min

A file landing in a folder does not start a job yet. Ask for it in the channel and it will.

Not a dashboard to go and check. What ran, what it found, and the one thing it could not finish without you.

Alfera#finance08:02

Overnight — Tuesday

Done

02:00Reconciled 214 payments. 3 did not match.

04:30Pipeline report rebuilt in Sheets.

06:3031 replies drafted in Gmail. None sent.

Waiting for you

03:1214 chase emails, written and unsent.

6 jobs · 1 h 9 m of work · 1 waiting

Nothing runs past what you wrote, or past the credit you set. It stops at the cap and waits for you.

It posts where you told it to: a channel, a thread, an inbox. Every run is also kept in Alfera, with what it read and what it changed.

Write one job. Say when. Read the result over coffee.