Workflows

Workflows are the autopilot layer of Tyrex AI. A workflow is a job your AI runs automatically: a trigger starts it, steps do the work, and the result is delivered where you want it. No code required.

Where to do it

Workflows live under Works → Workflows (sidebar). From there you can create a workflow, open the builder, configure triggers, view run logs, and run it manually. Your AI can also start workflows on its own when you enable that in the workflow's settings.

Anatomy of a workflow

TRIGGER → STEPS → RESULT
(cron / manual /    (ai + action +     (delivered to app,
 webhook / chat)     data + flow)       Telegram, or WhatsApp)

Triggers — what starts a workflow

Schedule (cron) configuration

{
  "triggerType": "CRON",
  "schedule": "0 7 * * 1-5"
}

The schedule field is a standard 5-part cron expression: minute, hour, day-of-month, month, day-of-week. 0 7 * * 1-5 runs every weekday at 07:00.

Webhook configuration

{
  "triggerType": "WEBHOOK",
  "webhook": {
    "method": "POST",
    "payload": {
      "orderId": "string",
      "customerEmail": "string"
    }
  }
}

The workflow exposes a public URL — POST /workflows/webhook/<workflow-id>/<secret> — where the secret is generated by Tyrex when you pick the trigger (no bearer token needed; the secret in the URL is the credential). Rotate it any time from the workflow's trigger settings. See API & Webhooks for the full reference. The payload you define here is what callers send to start a run.

Steps — what it does

Channels — where the result goes

Example workflows

• Morning brief — every weekday, your AI reviews your calendar and notes, then sends a summary to Telegram.
• Customer triage — a webhook from your store page starts a workflow: fetch the new order, check the FAQ knowledge base, draft a personalized reply, and notify you for approval.
• Reminder service — a scheduled workflow checks a calendar or list and sends a reminder when something is due.
• Report generator — at month-end, gather the numbers from your spreadsheet, write the report, and generate a PDF into the project.

Run lifecycle

Every run moves through a predictable lifecycle:

QUEUED → RUNNING → SUCCESS
                  └──→ FAILED (logged with the failing step)

• Queued — accepted and waiting for a slot.
• Running — steps executing in order.
• Success — result delivered to the configured channel.
• Failed — the run log shows exactly which step failed and why; fix and re-run.

Workflows are built to fail loudly and log cleanly: if a step errors, the run shows exactly where, and you can re-run without rebuilding the whole workflow.

Staying in control

• Every run is logged — see what happened, when, and the result.
• Pause or edit any workflow anytime — edits apply to the next run.
• Runs meter against your plan usage, shown on the workflow page.

Plan limits

FAQ

What happens when I hit my monthly run limit? New runs queue until the limit resets at the start of the next month — your dashboard shows remaining runs.

Can a workflow use my connectors? Yes — connected services (Drive, Slack, Telegram, and more) are available to workflow steps.

Do runs cost extra? Runs consume your plan's monthly allowance — see Plans & Billing.

Can I trigger a workflow from my own app? Yes — webhook triggers are built for that. See API & Webhooks.

Next: Tools & Connectors.