> 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/workflows/fyxer-in-practice/workflows-by-use-case/get-your-briefing-pushed-to-you.md).

# Get your briefing pushed to you

Start each day knowing what needs you, without opening five tabs.

### Who it's for <a href="#who-its-for" id="who-its-for"></a>

Anyone whose day starts with a scramble: checking the inbox, then the calendar, then last week's notes, to work out what matters today.

***

### Sound familiar? <a href="#in-your-words" id="in-your-words"></a>

> "The minute I log on in the morning, I’m straight into it, with work coming at me from every angle. I’d love to start my day with a quick snapshot of what I need to get done, before I get pulled into everyone else’s priorities."

***

### Why a Flow fits <a href="#why-a-flow-fits" id="why-a-flow-fits"></a>

You already know what you need each morning. The hard part is pulling it together without getting sidetracked, and then remembering to do it.

The Fyxer Briefing flow does the work for you. It runs at the time you choose and sends the briefing to where you'll see it first, your inbox.

{% 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 %}

***

### Set it up <a href="#set-it-up" id="set-it-up"></a>

1. Go to [Dashboard](https://app.fyxer.com) → Flows
2. Under Discover, open **Fyxer Briefing**
3. Select **Activate Flow**

If you want, adjust the time under **Trigger**. Then select **Save**.

***

### Ask a follow-up

Reply to your briefing email to ask Fyxer anything about it. For example:

* “Tell me more about Mike's email.”
* “What did we agree on my last call with Tom?”
* “Draft a reply to Priya confirming Thursday.”

***

### Want a different briefing?

The Fyxer Briefing is set up for you, so you can only change the time it runs.

To get a briefing built your way, create your own Flow. Go to [Dashboard](https://app.fyxer.com) → Flows → **Create Flow** and describe what you want, for example:

> Every Monday at 8am, send me this week’s external meetings, and anything I promised the attendees, in Slack.

You can also turn on the **End-of-day wrap-up** Flow to see what got done and what carries over.

***

### Learn more

Find out [**more about Fyxer Flows**](https://support.fyxer.com/article/set-up-fyxer-flows) in the Help Center or watch this short video:

{% embed url="<https://vimeo.com/1232321687?fe=sh&fl=pl>" %}


---

# 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/workflows/fyxer-in-practice/workflows-by-use-case/get-your-briefing-pushed-to-you.md?ask=<question>&goal=<user_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.
