> ## Documentation Index
> Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sidekick in workflows

> Start a Sidekick session from a workflow, triggered by what happens in your queue.

Workflows can start a Sidekick session on their own, triggered by what happens in your queue or by a clock, so work gets done before anyone opens the app.

This article covers how Sidekick fits into workflows. For how to build and configure workflows in general, see the Workflows docs.

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/in-workflows.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=d98b2b2854541c98f19ec8e44fe30a3f" alt="Sidekick in workflows in Plain" width="1520" height="960" data-path="public/images/in-workflows.png" />
</Frame>

## Thread-based workflows

A thread-based workflow fires whenever a thread meets conditions you set.

* **Triggers** include: a new thread arriving, a message added, labels changed, priority changed, tier updated, an SLA status transition, a thread escalated, thread fields set or updated, a thread locked, or a customer survey response landing.

* **Conditions** narrow it further: company, tenant, tier, channel, label, SLA state, or thread fields.

* **Steps** then run automatically: reassign, reprioritise, label, notify in Slack, fire a webhook, or start a Sidekick investigation.

For example, a workflow fires on new enterprise threads: Sidekick matches them against active errors and monitors in Datadog and Sentry, sets a label and priority, assigns the right team, and posts its findings as an internal note.

## Scheduled workflows

A scheduled workflow runs on a cron schedule with no trigger thread. It fires at a set time, runs its steps, and completes.

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/in-workflows-sidekick-step.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=7622d756c7638093053b4e8ef1f5f3c7" alt="Sidekick in workflows: sidekick step" width="846" height="276" data-path="public/images/in-workflows-sidekick-step.png" />
</Frame>

A scheduled workflow can include a **start a Sidekick discussion** step. The workflow parks while Sidekick works, then resumes once it's done. This makes fully autonomous reports possible: a structured briefing every morning without anyone asking for it.

* **Morning queue brief.** Every morning, a scheduled workflow has Sidekick pull breaching and near-breach threads, check their linked issues, and add discussion context, so the team walks in to a ready-made triage summary.

* **Weekly support digest.** Every Friday, Sidekick counts threads opened, resolved, and breaching, checks linked issues, reads high-activity discussions, and posts a structured digest to Slack.

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/in-workflows-output-automated-report.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=f20213843c291007b721315ec6c8f619" alt="Sidekick in workflows: output automated report" width="1600" height="1740" data-path="public/images/in-workflows-output-automated-report.png" />
</Frame>

## Where sessions show up

Sessions that a workflow starts run on the same engine, tools, and approval rules as any other Sidekick session, and they appear alongside your own in Home and the sessions shelf. Workflow-created discussions are visible to your workspace; personal sessions stay private.
