Workflows

AI Workflows turn a natural-language prompt into a recurring report. Each run recalls your organization's memory through the same policy gate as everything else — a workflow can only cite what its creator's role and level are cleared to see — then writes a concise, cited summary and delivers it.

Anatomy of a workflow

A workflow has four parts:

1. Prompt — what you want, in plain language ("Summarise what every team shipped yesterday").
2. Trigger — when it runs (see Triggers).
3. Output — where the result goes: a Slack channel or an email digest.
4. Owner — the creator. Every run executes against the owner's governed view of memory and is written to the audit log as a workflow_run.

Only a CEO or Manager can create workflows.

Quick-start templates

The builder ships with five defaults tuned for how lean teams — including early-stage Indian startups — actually run. Each maps to a real trigger and a real delivery channel:

Selecting a template loads its prompt, trigger, and output into the builder so you can tweak before saving.

Triggers

Scheduled triggers are driven by a cron endpoint (POST /api/cron/workflows) that an Upstash QStash schedule calls every five minutes; the endpoint runs only the workflows whose trigger is due and skips any that already ran in the current window (so a workflow never double-fires). The request is authenticated with CRON_SECRET.

Delivery formatting

• Slack — the model writes standard Markdown, which Cortex converts to Slack's mrkdwn dialect before posting, so **bold** renders as bold and -/* bullets render as • instead of showing literal asterisks. Numeric [1] citations are preserved as readable footnote markers. See Slack integration.
• Email — delivered via Resend to the workflow owner's address.

A run's delivery status (sent, failed, not_requested) and token counts are recorded on each execution and visible in the workflow's History.

Weekly digests

Weekly summaries are built as workflows rather than a fixed setting — create one from the Weekly Investor Update template (or any prompt) so you control the schedule, wording, and whether it lands in email or Slack.

Running against real memory

Press Run now on any saved workflow to execute it immediately against live governed memory. The execution console shows the produced summary with inline [n] citations; every run — scheduled or manual — is auditable.