> 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/resources/videos-and-events/getting-started.md).

# Getting started videos

See what's possible with Fyxer.

Fyxer is your AI assistant, working across your inbox, meetings, and the tools you already use, from Gmail and Outlook to Slack and Microsoft Teams. These videos walk you through the essentials, so you can get the most out of Fyxer from day one.

***

{% stepper %}
{% step %}

### Overview

Get your inbox under control, and never miss anything important across your email, calendar, and chat tools.

In this overview, you'll see what Fyxer does and how it fits into your day.

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

{% step %}

### Drafts and email categorization explained

See how Fyxer sorts your emails into categories and drafts replies in your voice, ready to review and send.

In this video you'll learn more about email categories, where to change your inbox settings, and how drafts work.

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

{% step %}

### Integrations and agents

See how connecting tools like Slack, Microsoft Teams, and Claude brings Fyxer into the places you already work, and how Fyxer Agents help you get answers without switching tools.

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

{% step %}

### Notetaker and scheduling

In this video, learn how Fyxer's Notetaker joins your meetings to capture notes and action items, and gives you a clear summary afterwards.

You'll also see how Fyxer handles scheduling, taking the back and forth out of booking meetings.

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

{% step %}

### Spaces

In this video, learn how to create a Space in Fyxer, choose which information goes into it, and see what you can do once it's set up.

You'll also see how roles work, from viewers to contributors, and how you can control which actions happen in a Space, so your team misses fewer commitments and keeps everything in one place.

{% embed url="<https://vimeo.com/1232322915?fe=ci&fl=sv&share=copy>" %}
{% endstep %}

{% step %}

### Flows

In this video, learn how Fyxer's Flows work, from the trigger that starts them to the action Fyxer takes and how the result is delivered. Nothing runs until you click Activate, so you stay in control.

You'll also see Fyxer's preset Flows, including the Morning Briefing, and how to build your own, so you can stay focused on the work that actually needs you.

{% embed url="<https://vimeo.com/1232321687?fe=ci&fl=sv&share=copy>" %}
{% endstep %}
{% endstepper %}

***

### Watch the full playlist

Visit the [**Fyxer YouTube channel**](https://www.youtube.com/@fyxerofficial) to explore all videos in one place, including setup, feature guides, and new releases as they’re added.


---

# 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/resources/videos-and-events/getting-started.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.
