> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Workflows
> Switch one on and everything a connected tool sends lands in your feedback, with no agent and no brief.
A workflow brings everything a connected tool sends straight into your feedback. Name it, say what it covers, switch it on. There is no brief to write and no schedule to pick, because it captures as things happen.
An [agent](/agents) reasons. A workflow does not. An agent reads what you gave it and decides what to do, which is what you want for research and reports, where a wrong answer costs you a paragraph. Ingestion is different. A customer's support ticket should reach your [signals](/signals) whether or not a model felt like fetching it that morning.
## Switching one on
Open **Agents** in the sidebar and go to the **By Squad** tab. Workflows sit in the same gallery as the [agent templates](/agent-templates), with the provider's logo on the card and **As it happens** where a cadence would be.
Click **Set up** on the card. Only connected providers appear, so if the one you want is missing, connect it first on [Integrations](/integrations).
The name is prefilled and yours to change. It is what you will scan for in the list, so name it after what it covers rather than the tool it came from.
Each workflow asks for whatever it needs to know what is yours. Leave it empty and you get everything the connection can see.
It starts capturing immediately. Nothing that arrived before this moment is backfilled.
You can run several instances of the same workflow. Two Jira workflows over two different sets of projects, each named for the team that cares about them, is a normal setup, and the card says **Add another** once one is running. Take the prefilled name twice and the second becomes "Jira requests 2", so the list never shows you two rows you cannot tell apart.
## What you can switch on
Every new service desk request, with its comment thread, as it is raised. Scope it to the service desks you pick, or leave it empty for every service desk the connection is monitoring.
Meeting notes and their transcripts, as Fellow finishes them. Scope it by words in the meeting title, so "discovery" and "renewal" come in and your one-to-ones stay out.
Fellow's scope is worth setting. Its trigger fires for every meeting the connected user attends, so an empty list pulls in one-to-ones, interviews and board calls alongside the customer calls you wanted.
## Reading what happened
Workflows appear in the **Agents** tab alongside your agents, with what they have captured and when they last did. Open one and the page is mostly its history.
Every attempt is a row, and there are three kinds.
It arrived and is in your feedback. The title links out to the item in the tool it came from, when the provider has a web view for it.
It was outside the scope you set. On a narrowly scoped workflow this is most of the list, and that is the workflow doing its job.
Something went wrong, and the row says what. A transient failure is retried; a permanent one is not.
This history is the answer to "why is nothing arriving". A column of skips means the scope is narrower than you thought. A column of failures usually means the connection broke.
## Pause, resume, delete
**Pause** stops new items arriving and keeps everything else. Nothing is captured while it is paused, so this is a real off switch rather than a filter on the view. **Resume** starts it again, and the gap is not backfilled.
Deleting removes the workflow and its history. Everything it already captured stays in your feedback, because those are signals now and they belong to your workspace rather than to the workflow that fetched them.
A workflow shows **Error** when its connection stops working. The page says what broke and offers **Check connection** and **Retry**. Reconnect the provider on [Integrations](/integrations) first, then retry.
## Workflows and agents together
Use both. Run a workflow to get the raw material in reliably, then point an agent at the [insights](/insights) it feeds, or at the [goals](/goals) those insights move. The workflow guarantees the evidence arrives. The agent is what has an opinion about it.