> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/chrome-extension/inbox-shortcuts.md).

# Inbox shortcuts

Type `di/` in a supported message body to open your Distro links. Keep typing a link name to narrow the list, use the arrow keys to highlight a result, and press **Enter** to insert it. **Escape** closes the picker.

The selected link replaces the shortcut at your cursor. It doesn't send your message.

## Where it works

| App             | Write the shortcut in   |
| --------------- | ----------------------- |
| Gmail           | A compose message body. |
| Gong            | An email composer.      |
| Google Calendar | An event description.   |
| LinkedIn        | A message.              |

Personal, group, and reusable outbound links are available in these supported editors. Recipient-aware actions and Outbound Router launches in this picker are Gmail-specific.

The shortcut doesn't activate in recipient fields, subjects, search boxes, or unrelated website inputs.

## Shortcuts worth remembering

* `di/` opens the picker.
* `/slots` or `di/slots` starts **Offer times** in Gmail.
* `di/book` starts an outbound booking in Gmail; add the recipient first.
* A code shown beside a link, such as `di/p-1`, selects that particular link. Use your link's displayed code, not the example number.

Saved links appear first under **Favorites**. You can press **Shift+Enter** to change whether the highlighted link is a favorite without inserting it.

To control where shortcuts appear, open the extension's **Settings → Browser integrations → Keyword detection**. Turn detection off entirely or change it for individual apps.


---

# 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://help.distro.so/integrations/chrome-extension/inbox-shortcuts.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.