Automations

Agent tasks that span weeks or months.

Schedules and business signals can start a Corin task. Agents use permitted context, wait for people when needed, and resume the same work after a pause.

Corin workspace/Automations
01 / 04 · START

A scheduled review starts.

01 / STARTScheduled review

A new task begins at the scheduled time.

02 / WORKAgents use context

Read permitted records and the relevant SOP.

03 / REVIEWHuman decision

Wait for approval before acting.

04 / CONTINUE THE SAME TASKContinue after the decisionSame task · next step
Access and approval rules apply to every step.01 / 04

Task lifecycle

Define when to create a task and when to update it.

A schedule can create a periodic review. An event or business condition can open a case. A reply or approval can then update that case.

Corin keeps the task state as agents and people take their turns. The work can continue over weeks or months.

WAYS TO START
SCHEDULEPeriodic review

Start a new task on schedule.

WORK ITEMNew task

Use permitted records and SOPs.

Access stays within configured permissions.01 / 03

Start conditions

Choose what starts a new task.

Use a schedule for periodic reviews. Use an event or business condition when a specific case needs attention.

Associate later replies and approvals with the open task. Configure its data, tools and approval points separately from the start condition.

Long-running tasks

Keep one task open for weeks or months.

An agent can complete a step and wait for a person or an external system. The task keeps its state through those waits and handoffs.

Built-in Temporal supports waits, retries and resumption. When a reply or approval arrives, Corin continues at the pending step. No model runs while the task waits.

ONE WORK ITEM
START

Open the task.

Record the case and its first step.

Temporal built in for supported durable execution01 / 04
WHAT YOU CAN INSPECT
01Records retrievedWhich records informed this step
02Agent and modelWho ran this step
03RecommendationWhat the agent proposed
Langfuse trace and separate business record01 / 02

Access and inspection

The start condition does not change permissions.

Agents use the access configured for the task. If a step needs approval, work waits for the authorized person before the next action.

Built-in Langfuse lets developers inspect agent steps and supported usage and cost data. Separate business records show who approved a decision and what changed in a connected system.

Example task

Invoice mismatch: one case through review.

Suppose an invoice and order do not match. Agents check permitted records and the relevant SOP, prepare a recommendation, and wait for a person to decide the next step.

INVOICE EXCEPTIONIllustrative flow
START

Open a task for this mismatch.

The task starts with the permitted invoice, order and SOP.

Task progressStarted
INSPECT THIS STEP

What started the task, and which records may agents read?

The trace shows agent steps; the business record shows approvals.

Build with Corin

Build an automation in Corin.

Try Corin free. Inspect a task, then configure its start condition, procedures and approval point for your workflow.