> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-notetaker/meetings.md). # Meetings Find any meeting AI Notetaker recorded, read its recap and transcript, play the recording, and send what was said to Slack, HubSpot or Google Sheets in a few clicks. The **Meetings** tab holds every meeting AI Notetaker recorded in your workspace. Find one, open it, read the recap or the transcript, and send what matters to the tools your team works in. Open **AI Notetaker** and go to the **Meetings** tab. *** ## Find a meeting The list shows each meeting's **Meeting name**, **Status**, **Duration**, **Host**, **Participants** and **Tags**. Click the play button to listen to a recording without leaving the list, or click a meeting to open it. | To | Use | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Search by words | **Search** looks in the title, the host, the participants, the summary and the meeting link. | | Show one person's meetings | **Host**: tick one or more hosts. The list updates as you tick. | | Show tagged meetings | **Tags**: tick the tags. Switch on **Match all tags** to show only meetings that carry every tag you ticked. | | Pick a period | **Date**: choose **From** and **To**, then click **Apply dates**. A period can be up to 30 days long. | | Include meetings with no recording | **Recorded only** is on by default. Click it to also see meetings the bot couldn't record. | | Change the order | Sort by **Date** or **Duration**. | **Select** lets you pick several meetings and **Delete** them, **Move to folder** or **Add tags** in one go. The download button exports the list to a CSV file with the date, duration, host, participants, status, platform and meeting ID of each meeting. *** ## Inside a meeting A meeting opens on its **Summary**: | Tab | What you find | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Summary** | The recap: **AI Insights**, the summary of the meeting, then **Action Items**, **Decisions**, **Key Topics**, **Stakeholders** and **Sales Tips & Call Insights**. **Copy Recap** copies all of it. | | **Transcription** | Every line, with who said it. **Search transcript...** finds a word, and clicking a line plays the recording from that moment. **Copy Transcript** copies the whole text. | | **Comments** | Notes your team leaves on the meeting, each tied to a moment of the recording. Select a moment in the transcript and click **Comment**. | | **Dapti** | Ask Dapti questions about this meeting. | At the top of the meeting, **Share** copies the meeting link, or the audio or video URL, and the tags and folder buttons file the meeting where you need it. *** ## Send a meeting to your tools Under the **Summary**, **Send this to** shows the Slack, HubSpot and Google Sheets logos. Each one sends this meeting with a ready-made Dapta instruction: | Logo | Instruction | What arrives | | ------------- | -------------------- | ----------------------------- | | Slack | *Churn risk alerts* | A message in a channel | | HubSpot | *BANT qualification* | A note on the contact or deal | | Google Sheets | *Next steps* | A new row | **Step 1:** Click a logo. Dapta extracts the instruction's fields from the meeting and opens **Review & sync**. *** **Step 2:** Under **Review**, check the fields Dapta pulled from the meeting. Click **Continue**. *** **Step 3:** Under **Destination**, the tool you clicked is already selected. Click **Continue**. If that tool isn't connected yet, click **Open Connections**, connect it, and come back to finish. *** **Step 4:** Under **Configure**, choose where it goes: the Slack channel, the HubSpot record or the spreadsheet. Click **Send**. To use any other instruction, yours or Dapta's, click **Sync** and pick it from the list. The same **Review & sync** steps follow. ### Make it automatic After a manual send, Dapta asks **Do this automatically?** if no assistant does it yet. Click **Make it automatic**: the assistant wizard opens with the same instruction and destination already filled in, and from then on every meeting is sent on its own. **Not now** closes it. See [Assistants](/ai-notetaker/assistants.md). ### What has been sent **Analysis by instruction**, lower on the **Summary**, lists every instruction run on this meeting, with the fields it extracted and who sent it: an assistant or a **Manual sync**. **View sent data** shows exactly what reached the destination. *** ## Rate the analysis **Rate this analysis**, next to **Sync**, takes a thumbs up or a thumbs down. A thumbs down asks what could be better, with an optional comment. If you haven't rated a meeting, Dapta asks once, after a minute of playback or when the recording ends. *** ## Next steps {% content-ref url="/pages/Slb3LFznmwm97ekQ0nXm" %} [Assistants](/ai-notetaker/assistants.md) {% endcontent-ref %} {% content-ref url="/pages/AAvv9wLuzQ2ZGvTY9w6W" %} [Sales Meetings](/dapti/capabilities/sales-meetings.md) {% endcontent-ref %} --- # 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.dapta.ai/ai-notetaker/meetings.md?ask=&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.