> 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/prompts-to-try.md).

# Prompts to try

Ideas to copy, change, and make your own.

{% hint style="success" %}

* [Write a good prompt](#write-a-good-prompt)
* [1. Ask](#id-1.-ask)
* [2. Prepare and act](#id-2.-prepare-and-act)
* [3. Your first Flow](#id-3.-your-first-flow)
* [4. Advanced Flows](#id-4.-advanced-flows)
* [5. Bring your team in](#id-5.-bring-your-team-in)
* [Explore more](#explore-more)
  {% endhint %}

Fyxer can find, prep, and draft for you, as long as you know what to ask. This page collects the prompts we use in our hands-on workshops, from quick questions to Flows that run on their own and Spaces your team shares.

This page covers five steps to successful prompting. Each step builds on the last, so start at the first and work through in order.

| Step                  | What you learn                         | You're there when                                |
| --------------------- | -------------------------------------- | ------------------------------------------------ |
| 1. Ask                | How to get answers from one prompt.    | You ask Fyxer before you search.                 |
| 2. Prepare and act    | Prep, draft, and plan with context.    | Fyxer writes your first drafts.                  |
| 3. Your first Flow    | Put one prompt on a schedule.          | Fyxer messages you before you ask.               |
| 4. Advanced Flows     | More complex Flows with several steps. | Your routine jobs run on their own.              |
| 5. Bring your team in | Shared context in Spaces.              | Your colleagues actively use one of your Spaces. |

{% hint style="info" %}
You might not see Flows or Spaces yet. We're rolling out these features gradually as we test and refine them, so availability will vary. We'll keep this page updated as things evolve.
{% endhint %}

***

### Write a good prompt

The more Fyxer knows about what you want, the better the answer. Mention @Fyxer in Slack or Teams, or use Chat in the Dashboard, then build your prompt with these four things:

1. Describe the job: catch up, prep, find, or draft
2. Name who or what: a person, client, project, or channel
3. Set the time: today, this week, since Monday
4. Say what you want back: bullets, a short summary, a draft email

> @fyxer What did \[client] ask me for this week? Bullets, most urgent first.

Not quite right? Reply in the same thread: "shorter", "include links". Treat the first answer as a starting point.

***

### 1. Ask

One job, one prompt. Run these any time you'd normally open five tabs.

| When                               | Ask @Fyxer                              | Why it helps                                                                      |
| ---------------------------------- | --------------------------------------- | --------------------------------------------------------------------------------- |
| At the start of the day.           | "What needs my attention today?"        | You see what matters before other people's priorities take over.                  |
| When you're looking for something. | "What did we decide about \[topic]?"    | Fyxer looks across your emails, meetings, and chats and brings the answer to you. |
| To catch up on someone.            | "What has \[person] sent me this week?" | You get up to speed quickly, without scrolling through threads.                   |

***

### 2. Prepare and act

Add context and rules, and let Fyxer do the first draft.

| When                        | Ask @Fyxer                                                                                                                                             | Why it helps                                                                |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| Before a meeting.           | "Prep me for my next meeting with \[person]."                                                                                                          | You walk in knowing the history.                                            |
| After a meeting.            | "Draft a follow-up email from my meeting with \[person]. Include actions as bullets."                                                                  | The email lands while the meeting is still fresh.                           |
| Planning.                   | "Find 30 minutes for me and \[person] next week."                                                                                                      | Removes the back-and-forth over availability.                               |
| At the end of the week.     | "What did I promise people this week that's still open? Group by person, oldest first, and skip anything internal."                                    | Rules (group, order, skip) give you an answer you can act on straight away. |
| Before tomorrow's meetings. | "Look at my meetings tomorrow. For each one with someone outside my company, give me the last email thread, open actions, and three questions to ask." | Several steps in one ask. This is the shape of an advanced Flow.            |

***

### 3. Your first Flow

A Flow is a prompt Fyxer runs for you, so the answer arrives before you ask or have to search for it.

Every Flow has three parts: when it runs, what Fyxer does, and where the output lands.

To get an instant feel for Flows, turn on the **Fyxer Briefing**. You can ask Fyxer to do this for you from Teams or Slack, or go to [Dashboard](https://app.fyxer.com/) → Flows → Discover, open Fyxer Briefing and select **Activate Flow** (if this is already running, you'll see Pause Flow instead). You can change the time it runs by editing the trigger field and selecting **Save**.

Then make your own Flow from a simple prompt: "Every weekday at 8am, send me what needs my attention in Slack/Teams." Again, two ways to set this up:

**Ask @Fyxer in Slack or Teams:**

> @Fyxer "Every weekday at 8am, send me what needs my attention in Slack/Teams."

**Go to the Dashboard:**

1. Go to [Dashboard](https://app.fyxer.com/) → Flows → Create Flow
2. Paste the prompt above, or write your own. It doesn't have to be perfect; Fyxer will ask you if it needs more information
3. Check the Flow Fyxer creates. Then edit the trigger, action, or delivery if you need to

Learn more: [**Run tasks with Flows**.](https://docs.fyxer.com/using-fyxer/run-tasks-with-flows.md)

***

### 4. Advanced Flows

Take a Flow further with several steps, rules, or an event trigger. Try the prompt in Slack or Teams first, and turn it into a Flow once the answer is right.

| What it adds      | Flow prompt                                                                                                                                | Why it helps                                                              |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- |
| Multiple steps.   | "Every weekday at 5pm, send me a brief for tomorrow's external meetings: the last email thread, open actions, and three questions to ask." | Tomorrow is prepped before you log off.                                   |
| Rules and drafts. | "Every Friday at 3pm, send me what I committed to this week that's still open, and draft the nudges."                                      | Nothing you promised slips over the weekend.                              |
| An event trigger. | "After each meeting with someone outside my company, list what I agreed to do, with any dates mentioned, and send it to me in Slack."      | Your actions are captured and ready for you where you're already working. |
| Chasing others.   | "Every Monday at 9am, send me who I'm waiting on, and draft a short chase for each."                                                       | You see what's stuck without keeping a list.                              |

When a Flow's message arrives, reply to it to take the next step: "Draft replies for the ones that need an email."

***

### 5. Bring your team in with Spaces

Fyxer gets more useful when the people you work with share context. A Space gathers every email, meeting, and action with one client, from everyone in the Space, so anyone can ask where things stand.

**Set it up:**

1. Go to [Dashboard](https://app.fyxer.com/) → Spaces → Create new
2. Name the Space after the client, add the client's domain as a source, then select **Create Space**
3. Select **Invite** and add the colleagues who work with that client. Turn on automatic invites so new people join as they email or meet the client

Learn more: [**Share context with Spaces**.](https://docs.fyxer.com/using-fyxer/share-context-with-spaces.md)

**Then ask @Fyxer in Slack or Teams:**

* "What have we promised in \[Space name], who owns each item, and is anything overdue?"
* "What's changed with \[Space name] this week?"
* "Is there anything the client has asked for in \[Space name] that nobody has replied to?"

**Make it a team Flow:**

> @Fyxer, create a Flow to send me what changed this week in each of my client Spaces every Friday at 3pm. Share in my team's Slack channel \[channel name].

***

### Explore more

**Learn:**

* [Connect Fyxer to Slack](https://support.fyxer.com/article/connect-fyxer-to-slack)
* [Connect Fyxer to Microsoft Teams](https://support.fyxer.com/article/connect-fyxer-to-microsoft-teams)
* [Run tasks with Flows](https://docs.fyxer.com/using-fyxer/run-tasks-with-flows.md)
* [Share context with Spaces](https://docs.fyxer.com/using-fyxer/share-context-with-spaces.md)

**Workflows to try:**

* [Never drop a follow-up](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/never-drop-a-follow-up.md)
* [Know where every account stands](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/know-where-every-account-stands.md)


---

# 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/prompts-to-try.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.
