> 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/find-anything-wherever-it-was-said.md).

# Find anything, wherever it was said

Search Slack, email, and meetings at once, and pull your to-dos together, without leaving Slack.

### Who it’s for

Anyone who works in Slack all day, with decisions and requests spread across DMs, email threads, and calls.

***

### Sound familiar?

> "Fyxer has helped me stay on top of my inbox and meeting notes, but a lot of my work happens in Slack, and I'm losing track of what I owe there."

***

### Why the Fyxer agent fits

When you need to find something, you usually have to remember where it was said first. Then you search each place in turn.

Your Fyxer agent searches them all at once. Ask @Fyxer in Slack, and it looks across your Slack messages, emails, and meeting notes. If the answer is in a Slack message, it links you straight to it, and it can draft your reply for you to approve.

***

### Set it up

Go to [Dashboard](https://app.fyxer.com/) → Settings → Integrations → Apps and follow the prompts to connect Fyxer to Slack.

***

### Prompts to copy

You can chat with Fyxer in any channel or start a DM with it.

**Find what was said:**

* “@Fyxer what did Tom say about the launch date, on Slack or on our last call?”
* “@Fyxer has anyone sent me the final budget, in Slack or email?”
* "@Fyxer, what's the latest on the Product Updates channel?"

**Gather your actions:**

* “@Fyxer what have people asked me to do today on Slack?”
* “@Fyxer list everything I said I’d do this week, and where I said it.”

**Reply without leaving the conversation:**

* “@Fyxer find Sophia's message about the venue and draft a reply saying Thursday works.”
* “@Fyxer draft a reply to Mike's last DM, confirming I’ll send the deck by Friday.”

Fyxer shows the reply in a card only you can see. Nothing is sent until you select **Approve**, and you can select **Edit** to change it first.

***

### Make it a habit

Set up a Flow to receive your Slack action list every morning, so you don’t have to ask.

Go to [Dashboard](https://app.fyxer.com/) → Flows → **Create Flow**. In the prompt box, add:

> Every weekday at 9am, send me my outstanding actions from Slack, email, and meetings, in a Slack DM.

Learn more: [**Set up Fyxer Flows.**](https://support.fyxer.com/article/set-up-fyxer-flows)

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

***

### Learn more

Read [**Fyxer in Slack**](https://support.fyxer.com/article/connect-fyxer-to-slack) in the Help Center or watch this short video:

{% embed url="<https://vimeo.com/1231209949>" %}


---

# 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/find-anything-wherever-it-was-said.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.
