> ## Documentation Index
> Fetch the complete documentation index at: https://heybtw.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompts and resources

> The workflow prompts and guides heyBTW serves alongside its tools.

Besides tools, the heyBTW connector serves **prompts** (ready-made workflows you start from your client) and **resources** (guides an agent can read). Clients show them in different places; in Claude they appear with the heyBTW connector.

## Prompts

Each workflow prompt opens with "Follow the workflow rules in the server instructions" and takes the event to run on. Leave the event out and the prompt asks which one, or picks the nearest event for its window.

| Prompt | When | What it does |
| - | - | - |
| `invite_sprint` | The two weeks before an event (`sprint` and `event_week` windows) | Where the event stands against its RSVP target, who to ask and through whom, partner seat asks, and a Luma send last, sized to what is left. Reads first, proposes, and writes only what you accept. See [Fill the room](https://heybtw.com/docs/playbooks/invite-sprint.md). |
| `debrief` | The first days after (`wind_down`) | Walks the attendees with you, records who met them and what was said, and commits the follow-ups you accept, with owners from your own CRM. See [The morning after](https://heybtw.com/docs/playbooks/morning-after.md). |
| `follow_through` | From the third day after (`wind_down`) | Who has not been followed up, by owner, what was committed against what the CRM shows, and nudges you send through your own connectors. Changes no task. See [Follow-up and ROI](https://heybtw.com/docs/playbooks/follow-up-and-roi.md). |
| `record_roster` | Before or after any event | Puts one event's guests into heyBTW: creates or finds the collab from its link, records who registered from the guest export, marks only the people who attended, and checks the counts. See [Record who came](https://heybtw.com/docs/playbooks/record-who-came.md). |
| `format_attendee_list` | Any time | Turns an attendee list that is not a table (an email thread, a badge dump, pasted names) into the CSV [`record_signups`](https://heybtw.com/docs/tools/record-signups) takes. Never use it on a file that is already a table. |

| Prompt | Arguments |
| - | - |
| `invite_sprint`, `debrief`, `follow_through` | `collab_ref` (optional): a `channel_id` from [`list_events`](https://heybtw.com/docs/tools/list-events) or an event name |
| `record_roster` | `event` (optional): a public link, an event name or a `channel_id`; `attendees` (optional): who attended |
| `format_attendee_list` | none |

The prompts read the event clock from the server (`goal.clock.event_window`). Run outside its window, a prompt says which window the event is in and stops.

## Resources

| URI | What it is |
| - | - |
| `heybtw://guides/event-follow-up` | How to write the immediate follow-up after an event and build the list to send it to: claim only what the evidence supports for each person, state the basis, context first, in the host's voice. |
| `heybtw://prompts/format_attendee_list` | The same instructions as the `format_attendee_list` prompt, for clients that read resources rather than prompts. |

Resources hold no workspace data. They are the same text a person reads in these docs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.