Scheduled AI jobs with every run on record

Tell an agent in chat or Slack what to run and when: on demand, on a cron schedule, or when an event arrives. The job runs unattended with that agent's access, stays private to you, and keeps every run's output and steps.

Early access. Request a demo to get started.

A cron job's morning run lands: Pending, Running, then Completed, with its output on record. With Slack connected, a scheduled single-turn job also DMs its owner the result.

Create a job by asking for it

In Insulin, AI workflow automation starts with one message. Tell an agent in chat or Slack what should run and when, and it sets up the job with the trigger that fits. There is no form to fill in: to change a job, ask again. Developers can also call POST /jobs.

A job created by asking: the agent picks the trigger and writes the schedule in words.
TriggerWhen it runsWhat you control
Manual When you start it, and again whenever you like. Run, and Terminate while a run is going
Cron On any cron schedule, such as 0 9 * * 1-5 Run now, and Enable or Disable
Push When an event arrives: a Fours marketplace event, such as an offer accepted or a listing updated, or a GitHub, Google Calendar or Gmail event. An optional filter, such as event.amount > 1000, plus Run now, and Enable or Disable

Every fire leaves a run, including events the filter skips, recorded as Filtered, and runs over the hourly limit, recorded as Rate limited.

A failed run keeps every step it took before it stopped, so the reason is one tab away.

Every run leaves a record

Each time a job fires, Insulin records a run with its status, start time and duration, and keeps its Output, Steps and Input. Steps hold the agent's full tool-call transcript, even when the run fails.

Pending
Queued, waiting to start.
Running
The agent is working.
Completed
Finished successfully.
Failed
Ended with an error; its steps are kept.
Cancelled
A run in progress was stopped.
Filtered
The event did not pass the job's filter.
Rate limited
Skipped: the job or organization hit its hourly limit.

A job works within its agent's access

A job runs as its agent, with that agent's integrations, knowledge bases, skills and model, and never more.

  • Read-only stays read-only

    Set an integration to Read-only on the agent and its runs have no write tools there.

    Read-only · no write tools
  • Runs never pause for approval

    Jobs run unattended, so no run waits for an Allow. Decide what the agent may change before you schedule it.

  • Private to you

    Only you can see, run, change or delete a job you created; not even an org admin can. Work that the Planner schedules in an organization channel belongs to the channel.

  • Limits you can plan around

    Runs that Insulin starts are capped at 60 per job and 300 per organization each hour; running a manual job is exempt. A job has one run in flight at a time.

    60 per job · 300 per org · hourly

Goals keep working until the objective is met

Ask for something that takes many rounds and the agent sets a goal. It keeps working in the background until the objective is met or you stop it, and it appears in Jobs as a goal job.

  • A goal card with its status and the round it is on
  • Steer it while it runs; your message is picked up on the next round
  • Cancel it from the card, or write “Stop.” in the conversation
  • It posts nothing to Slack on its own; follow it on its card or in Jobs
A goal on its third round, with a steer typed in for the next one.

Frequently asked questions

What is a job in Insulin?

A job is one agent, its instructions and one trigger: Manual, Cron or Push. It runs unattended with that agent's access, and each time it fires it leaves a run record with the output and every step.

How do I create a job?

Ask an agent in chat or Slack, for example “every Monday at 9, summarize last week's accepted offers”, and it sets up the job. There is no form; to change a job, ask again. Developers can also use the API.

What can start a job?

You, on demand; any cron schedule; or an event: a Fours marketplace event such as an offer accepted or a listing updated, or a GitHub, Google Calendar or Gmail event. An optional filter decides which events run it.

Can anyone else see my jobs?

No. A job is private to the person who created it, and not even an org admin can see, run, change or delete it. Work that Planner schedules in an organization channel belongs to the channel.

Do jobs wait for approval before acting?

No. Runs are unattended and never pause for approval, so a job can do whatever its agent's integrations allow. Set an integration to Read-only on the agent and its runs cannot write there.

Will I hear when a job finishes?

If your organization has connected Slack, Insulin DMs you when a manual or scheduled job you own finishes, with the result and a link to the job. Jobs started by events, goals and channel jobs don't send one.

What happens when a run fails?

The run is recorded as Failed, and its Steps keep the full tool-call transcript up to the failure, so you can see which call broke and why.

How is a goal different from a job?

A goal is work that takes many rounds. It keeps going in the background until the objective is met or you stop it, you can steer or cancel it from its card, and it appears in Jobs as a goal job.

Put the recurring work on a schedule

Insulin is in early access. Book a demo to see jobs run unattended, with every run on record.