Workflows and apps

AI workers

Create, run, and monitor autonomous workers for bounded recurring workflows.

Choose bounded recurring work

Workers fit processes with a stable trigger, recognizable inputs, a clear output, and an accountable owner. Start with work that can be reviewed before it has an external consequence.

A dry run shows the plan and the document it would make without touching a ticket.
Try this
Click New worker in the sidebar and describe the job: Every Monday at 8am, read last week's tickets from our connected helpdesk, draft a one-page summary of the top five issues as a document, and leave it for me to review. Do not send anything.
What you getThe worker view opens with your brief; clicking Dry run shows the steps it would take and the document it would create without touching a single ticket.

Define inputs and stopping conditions

State what begins the run, which sources are authoritative, what the worker should produce, and when it must stop and ask for help.

The stop condition fires: the run pauses and asks instead of drafting 30 emails.
Try this
In the worker view, add to the brief: Trigger: a new row in the connected leads sheet. Authoritative source: that sheet only. Output: one draft follow-up email per lead as a document. Stop and ask me if a lead has no email address or if more than 25 new rows appear at once.
What you getThe worker's plan now includes both stop conditions, and a Dry run against a test sheet with 30 rows halts and asks rather than producing 30 drafts.

Add Skills and Connectors

Attach only the reusable methods and service permissions needed for the job. A worker does not need broad access to be useful.

Read access and one skill are enough to draft; sending needs a connector the worker does not have.
Try this
Give the invoice-chasing worker only the Invoice reminder skill and the accounting connector's read permission for overdue invoices. Leave the email connector off for now.
What you getThe worker can read overdue invoices and draft reminders in the skill's wording, but has no way to send them until you attach and approve that connector.

Monitor and approve

Use live progress to see what the worker is doing. Require approval before sending, publishing, changing records, or sharing sensitive work.

The Runs tab: a run waiting at the approval gate shows Approve and Reject.
Try this
Click Run now on the social-posting worker and watch the run. It should pause when it reaches the publish step.
What you getLive progress shows each step, the run stops at Waiting approval before publishing, and you read the three drafts and click Approve, or Stop run if one is off-brand.
GUIDED LEARNING

Practise this in Oppermind Academy

Follow the related tutorial or course and apply the concept to a real task.

Open learning path