Plan captures and check for missing calls
Connect
SPIRITT
Recall.aiRecall.ai
Meetings to action
SPIRITT operates your Recall.ai meeting bots and turns available transcripts, chat messages, and recordings into completed follow-ups. Build the capture workflow and the systems that put each conversation to work.
What you can do with Recall.ai.
Reliable meeting capture
Coordinate calendar events and scheduled bots, catch missing recordings, and surface the specific capture failures your team needs to resolve.
Follow-through with evidence
Turn available transcripts and meeting chat into customer recaps, assigned tasks, and CRM updates tied to the source conversation.
A usable recording library
Build a searchable meeting library with recording metadata, processing status, and access to available media instead of scattered links.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for meeting capture, conversation follow-through, or a custom recording library.
02
Connect Recall.ai
Connect Recall.ai with your API key. Add the calendars and destination tools your mission needs, with appropriate access and recording consent.
03
Delegate an outcome
Give SPIRITT your meeting scope and recording rules. It operates the bots, processes available conversation data, and carries the resulting work into your team's tools.
Hand over a mission.
Choose a mission. Make it yours.
Put Recall.ai to work.
Put every captured meeting to work
Questions
Recall.ai, with SPIRITT.
01What can SPIRITT operate in Recall.ai?+
SPIRITT can create bots, inspect their status, update scheduled bots, start or stop recording, and remove bots from calls. It can also retrieve recordings and list available transcripts, chat messages, screenshots, participant events, and audio or video artifacts to support downstream work.
02What access is needed for calendar-driven recording?+
Recall.ai connects using an API key. Calendar-driven missions also need the relevant Google Calendar or Microsoft Outlook connection and calendar-user recording preferences. SPIRITT can inspect calendar events and manage supported preferences; your meeting scope and participant consent rules determine which calls it should capture.
03Can SPIRITT turn recordings into work in other tools?+
Yes. With the destination tools connected, SPIRITT can use available transcripts and chat to send Gmail recaps, create Asana tasks, update HubSpot next steps, or build a Notion decision register. Recording references keep the resulting work traceable to the conversation, while unstated owners and deadlines remain explicit gaps.
04What custom apps can it build around Recall.ai?+
SPIRITT can build a searchable meeting library, a bot operations desk, or a recording-health dashboard. Recall.ai provides bot details, recording metadata, artifact availability, and media references; the custom app supplies the search, team views, and operating workflow around those objects.
05How are bot cancellation and media deletion different?+
Deleting a bot cancels a scheduled bot that has not joined a call. Removing a bot from a live call disconnects it immediately. Deleting bot media permanently removes all media associated with that bot, so retention workflows need a bot-level scope, hold exclusions, and explicit authorization before deletion.
06Is this just another meeting-summary workflow?+
No. Recall.ai exposes meeting capture operations as well as conversation artifacts. SPIRITT can coordinate scheduled bots, manage recording preferences, investigate capture failures, and maintain the downstream systems. Summaries are one output; available transcripts and media can also power task execution, research repositories, and decision tracking.