Insulin · Jobs New

Scheduled AI jobs that do the work while you are elsewhere.

A job runs an Insulin agent unattended — once, on a recurring schedule, or when a business event fires. The recurring parts of marketplace operations stop depending on someone remembering them.

Now in early access — request a demo to get started.

Insulin · Jobs
Scheduled runs + New job
Disbursement reconciliation
Daily · 07:00
Recurring
Co-sell referral hygiene
Mon · 09:00
Recurring
Listing drift check
On listing update
Event
Q3 entitlement backfill
Ran once · complete
One-time
Last run · Disbursement reconciliation
Records
1,482
Matched
1,469
Flagged
13
Summary posted to #finance-ops · 07:04

What they are

What is an AI automation job?

An AI automation job is an agent set to run on its own. In Insulin, a job pairs one of your agents with a task and a trigger, then executes it unattended — one time, on a recurring schedule, or when a business event fires.

The point is not that the agent is faster than you. It is that the run happens whether or not anyone remembers it. The month-end check, the Monday digest, the sweep that only matters when something drifts — all of it moves off a person's to-do list and onto a schedule.

One-time

Run it once

Kick off a single unattended run — a backfill, an audit, a one-off sweep across your records — and pick the results up when it finishes.

Recurring

Run it on a schedule

Put the agent on a timer so the work happens every morning, every Monday, or at month-end without anyone remembering to ask.

Event-driven

Run it on a business event

Let a change in the business start the run, so the agent reacts when something actually happens instead of waiting for the next tick of the clock.

What you can build

Jobs marketplace teams tend to build first

These are not shipped presets. They are the shape of the work teams hand to a job once they have an agent scoped to the right domain — you describe the task, pick a trigger, and the run is yours.

A disbursement reconciliation sweep

Have an agent compare marketplace disbursements against what your finance system expects and write up the gaps before anyone opens a spreadsheet.

A co-sell referral hygiene check

Point an agent at referral records on a schedule and surface the ones missing a stage, an owner, or a next step.

A listing check

Sweep your marketplace listings for anything that has drifted — a stale pricing dimension, a missing field, a listing that never went live.

A recurring reporting digest

Generate the same summary every Monday from your own data and drop it into the channel the team already reads.

An entitlement expiry watch

Ask an agent to look ahead at what is about to lapse and flag the accounts that need a renewal conversation.

An overnight data sync review

Check that records moved between your connected systems as expected, and raise it in a thread when they did not.

New job
Agent
Finance agent
Task
Compare yesterday's marketplace disbursements with the finance ledger. List every record that does not match and explain why.
Trigger
One-time
Recurring
Event
Every day at 07:00
Deliver to
#finance-ops channelEmail summary
Schedule job

Why it matters

The work that only gets done when someone remembers

Most marketplace operations problems are not hard — they are simply easy to forget. Jobs take that class of work off people entirely and give it a schedule.

  • Recurring work stops depending on someone's memory
  • The same instructions run the same way every time
  • Findings arrive before the deadline, not after it
  • Agents keep the integration scope you granted them
  • Results land where the team already talks
  • One-time runs handle backfills and audits

How it works

Four steps to a job that keeps running

If you can describe the task in chat, you can schedule it. Jobs use the same plain-English instructions.

1

Pick the agent

Choose the specialist that already has the instructions and integration scope for this work.

2

Write the task

Describe what the run should do in plain English, the same way you would ask in chat.

3

Choose the trigger

Run it once, set a recurring schedule, or start it from a business event.

4

Review the runs

Read the output, adjust the task, and let the job keep going.

Jobs are part of Suger Insulin, the AI workspace in the Suger console — view pricing or contact sales for availability.

A job is only as good as the agent behind it. Start with AI agents for cloud marketplace operations, ground them with an AI knowledge base, or install one from the AI agent marketplace.

Prefer to watch a run happen live? Insulin chat shows the plan, the tool calls, and the approval step in real time.

Frequently Asked Questions

Common questions about Insulin jobs

What is a job in Suger Insulin?

A job is automated agent execution. You pair an Insulin agent with a task and a trigger, and the agent runs unattended — one time, on a recurring schedule, or when a business event fires.

How is a job different from chatting with an agent?

Chat is interactive and you are present for it. A job runs the same agent without you there, so recurring work happens on its own schedule and the result is waiting when you look.

What kinds of jobs can we build?

Anything you would otherwise ask an agent to do on a repeating basis — reconciliation sweeps, co-sell referral hygiene checks, listing checks, recurring digests. You define the task; Insulin does not ship a fixed list.

Do jobs work with our own documents and systems?

Yes. A job inherits the agent's integration scope and any attached knowledge bases, so an unattended run reads from the same connected systems and grounded documents an interactive session would.

Can a job trigger from something happening in the business?

Yes. Alongside one-time and recurring schedules, a job can be triggered by a business event, so the agent reacts when a change occurs rather than on the next scheduled tick.

Give the recurring work a schedule

See how Insulin jobs run your agents unattended — once, on a timer, or on a business event.