Skip to content
Workflow library

The first jobs worth giving an AI employee

Each workflow has a start signal, permitted context, result, review point, and a reason to stop.

Published August 24, 2026 · Reviewed against current product boundaries

Email and follow-through

Routine inbox draft

Start: a new email matching one approved type. Context: the thread and approved client record. Result: a draft. Review: recipient, facts, promise, and attachments.

Post-meeting recap

Start: a supported Zoom meeting ends. Context: transcript, brief, and explicit commitments. Result: factual recap draft. Review: decisions, owners, dates, and external wording.

Missing-item reminder

Start: an approved checklist has open items. Context: the checklist and prior communication. Result: itemized reminder draft. Review: whether the item is truly missing and who should receive it.

Status update

Start: a scheduled reporting time. Context: approved project records. Result: concise update with completed, open, and blocked work. Review: stale or inferred status.

Meetings and tasks

Meeting brief

Start: a calendar event approaches. Context: approved prior threads, notes, and open items. Result: one-page brief. Review: confidential material and outdated facts.

Zoom attendance with the owner

Start: owner dispatches the employee. Context: meeting brief and approved company knowledge. Result: write-up and open questions. Review: summary accuracy and any proposed follow-up.

Zoom attendance for the owner

Start: owner sends it to one supported Zoom meeting with a brief. Result: discussion within the brief and a write-up. Review: all decisions and commitments before they become actions.

Commitment-to-task handoff

Start: an explicit commitment appears in a reviewed record. Result: proposed task with owner and date. Review: commitment wording, assignee, and due date.

Knowledge and operations

Internal answer from approved records

Start: the owner asks a business question. Context: connected approved documents and records. Result: answer and source path where available. Review: use the system of record for consequential facts.

Recurring checklist

Start: a schedule. Context: the approved procedure and last run. Result: completed items, exceptions, and owner handoff. Review: skipped steps and silent failure.

New-client handoff

Start: intake is approved. Context: approved form, agreement, and owner notes. Result: folder, checklist, proposed tasks, and welcome draft. Review: identity, scope, privacy, and external message.

Weekly open-items review

Start: weekly schedule. Context: the selected task or CRM view. Result: aging items grouped by owner. Review: source freshness and incorrect ownership.

How to use this library

Choose the workflow closest to a real recurring job. Narrow it to one system, one output, and one owner. Run twenty cases. Keep every external or high-consequence action under review until the evidence supports a change.

A workflow page is not proof that a connector or action is available in your plan. Check the Product Guide and current dashboard before depending on it.

The library deliberately excludes autonomous professional judgment, inbound phone answering, customer-side messaging, and unsupported meeting platforms.