> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/using-fyxer/run-tasks-with-flows.md).
# Run tasks with Flows
Hand over repeat tasks, and get the results sent to you.
{% hint style="success" %}
* [How a Flow works](#how-a-flow-works)
* [Flows you can turn on](#flows-you-can-turn-on)
* [Turn on a Flow](#turn-on-a-flow)
* [Make a Flow your own](#make-a-flow-your-own)
* [Create a Flow from scatch](#create-a-flow-from-scratch)
* [Workflows to try](#workflows-to-try)
* [Flows, Spaces or categorization rules?](#flows-spaces-or-categorization-rules)
* [Watch the Flows webinar](#automate-your-workflows)
{% endhint %}
Some tasks come back every day or after every meeting: checking what needs you, rounding up actions, keeping track of where deals stand.
A Flow lets you set the task up once, so Fyxer runs it for you and sends you the result.
{% hint style="info" %}
You might not see Flows yet. We're rolling this feature out gradually as we test and refine it, so availability will vary. We'll keep this page updated as things evolve.
{% endhint %}
### How a Flow works
Every Flow has three parts:
* **Trigger:** what starts it. This can be a schedule, like every weekday at 7am, or an event, like a meeting ending or an email getting a Fyxer label
* **Action:** the plain-English instructions Fyxer follows when the Flow runs
* **Delivery:** where the result goes. You can choose a Slack DM or channel, a Microsoft Teams DM, email, or an in-app notification
Learn more: [**Set up Fyxer Flows.**](https://support.fyxer.com/article/set-up-fyxer-flows)
***
### Flows you can turn on
Fyxer has ready-made Flows you can turn on in a couple of clicks, including:
* **Fyxer Briefing:** a short morning email of what needs your attention today, drawn from your open action items
* **End-of-day wrap-up:** what got done, what's still open, and what tomorrow looks like
* **Commitments-first summary:** see what everyone promised after every meeting
* **CRM-less deal tracker:** a daily digest which scans your email for new inbound interest and cross-references your calendar for what's already booked
***
### Turn on a Flow
Go to [Dashboard](https://app.fyxer.com) → Flows, select the Flow you want, then select **Activate Flow**.
To turn it off, select **Pause Flow**. To remove it, select **Delete**.
***
### Make a Flow your own
Once a Flow is active, open it to change how it works. On the right, you’ll see **Trigger**, **Action**, and **Delivery**. Change any of these, then select **Save**.
Some fields in ready-made Flows can’t be changed. You’ll see a padlock next to them.
***
### Create a Flow from scratch
Select **Create Flow** and describe what you want in plain English. Fyxer sets the title, trigger, and instructions for you. Check them, change anything you need to, then select **Save**.
Some ideas to try:
* “After each meeting with someone outside my company, list what I agreed to do, and send it to me in Slack”
* “Every Friday at 4pm, send me a list of client emails I haven’t replied to”
* “When an email is labeled To respond, send me a Slack message straight away”
Wherever your Flow is delivered, reply to the message to ask Fyxer a follow-up question.
***
### Workflows to try
* [**Get your briefing pushed to you.**](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/get-your-briefing-pushed-to-you) Start each day knowing what needs you
* [**Never drop a follow-up.**](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/never-drop-a-follow-up) Keep track of what you promised, and when
***
### Flows, Spaces, or categorization rules?
Flows send you updates. They don’t move or label emails. To have emails sorted a certain way, use a categorization rule instead.
Learn more: [**Spaces, Flows or categorization rules: which do I need?**](https://support.fyxer.com/article/spaces-flows-or-categorization-rules)
***
### Watch the Flows webinar
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
#### Automate your workflows
This 15-minute walkthrough will show you how you can get more done in the background with Fyxer Flows.
[**Masterclass: Automate your workflows**](https://zoom.us/rec/share/YlhsLgZaNe1PYhqDrdU9Fqi7byg95stF3oYiRMpKNbrWIUDa3RbHxT3gcmZVwI-3.ihh-xGtDmK8-UJBu)
{% endcolumn %}
{% endcolumns %}
***
### Next up
Learn how Spaces bring together everything about one client or project.
* Next: [**Share context with Spaces**](https://docs.fyxer.com/using-fyxer/share-context-with-spaces)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.fyxer.com/using-fyxer/run-tasks-with-flows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
