ceven

Recall.ai

Deploys meeting bots to record calls, pulls transcripts and chat logs into your CRM, and automates the delivery of post meeting summaries.

Try Recall.ai in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Recall.ai integration

    • Describe the outcome and Ceven picks the right Recall.ai calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Recall.ai data, across all 63 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Recall.ai access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Recall.ai, when, and on whose behalf.
    • The agent pauses and asks when Recall.ai is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Recall.ai.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Recall.ai action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Recall.ai, and when to use it.

Create bot
Use this when a workflow needs to schedule a bot to join a specific meeting link at a set time.
Delete bot
Permanently remove a bot record from the system using the bot ID.
List bots
Pull a list of all bots currently configured or active in the system.
List chat messages
Retrieve all chat messages the bot read during the meeting, excluding messages sent by the bot.
Remove bot from call
Force the bot to leave the current meeting immediately. This action cannot be undone.
Retrieve bot
Pull the current status and configuration details for a specific bot instance.
Start recording
Tell the bot to begin recording the meeting. This restarts the recording if one is already active.
Stop recording
Instruct the bot to end the current recording session and finalize the file.
Get transcript
Pull the full text transcript of a completed meeting for analysis or storage.
Update bot config
Change the name or avatar of the bot before it joins a meeting to match your brand.
Search meetings
Find past meetings based on participant email or date range.
Get recording URL
Retrieve the direct link to the video file stored in Recall AI for a specific session.

12 actions · scroll to see them all

Frequently asked questions

Ceven triggers the Create bot action which sends a request to Recall AI with the meeting URL and start time. The Recall AI infrastructure then spawns a virtual participant that requests entry into the meeting. If the meeting has a waiting room, a human host must still admit the bot just like any other participant. Once admitted, the bot remains silent and begins capturing the audio and video streams based on your recording settings. You can customize the bot name through the manage actions so your customers see a name like Meeting Assistant rather than a generic bot ID.
Yes. Recall AI provides a unified API that abstracts the differences between Zoom, Google Meet, and Microsoft Teams. When you tell Ceven to deploy a bot, it does not matter which platform the link belongs to. Recall AI handles the platform specific join logic and returns the data in a consistent format. This means your workflows for summarizing calls or extracting action items remain exactly the same regardless of whether your customer prefers Zoom or Teams, allowing you to scale your meeting automation without writing custom logic for every video provider.
If a meeting is rescheduled, the original bot instance created for the old time will not automatically move. You must use the Delete bot action to remove the stale instance and then trigger a Create bot action for the new time and link. Many users build a Ceven workflow that watches their Google Calendar for update events and automatically handles this refresh process. This ensures that a bot is always ready for the correct slot and you do not waste bot minutes on meetings that are no longer happening at the scheduled time.
Recall AI enforces concurrency limits based on your specific subscription tier. If you attempt to deploy more bots simultaneously than your plan allows, the API will return a rate limit error and the bot will fail to join. Ceven handles these errors by alerting the workflow owner, but it is important to monitor your concurrent meeting volume. For high volume teams, we recommend a queueing system within Ceven that prioritizes high value calls to ensure that the most important client discovery sessions always have a bot present.
Recall AI acts as a conduit that captures the data and stores it securely. Ceven pulls this data via encrypted API calls and moves it into your designated destination, such as a CRM or a private database. We do not use your meeting transcripts to train global models. You can set up a workflow to automatically delete the recording from Recall AI storage once the transcript has been processed and moved to your own secure vault, ensuring that sensitive customer conversations do not live on third party servers longer than necessary.
The bots provided by Recall AI are designed for passive observation and data capture. They cannot speak or unmute themselves to contribute to the conversation. They can read the chat messages and send messages into the chat if configured, but they cannot perform active voice interaction. This makes them ideal for transcription and analysis without disrupting the natural flow of a sales call or a board meeting. If you need an active participant, you would need a different type of AI agent, as Recall AI focuses on the data capture layer.
Transcripts are typically available shortly after the bot leaves the call and the recording is finalized. However, there is a processing lag depending on the length of the meeting and the platform used. Ceven uses a webhook listener to detect when the recording status changes to completed. Once the webhook fires, the agent immediately pulls the transcript. For very long meetings, this might take a few minutes. We recommend setting your post meeting automation to trigger on the completed event rather than a fixed time offset to ensure the data is fully ready.
If a meeting host removes the bot, the session ends immediately and the bot cannot rejoin that specific call. Ceven will receive a termination event from Recall AI indicating that the bot was removed. You can configure a workflow to notify the meeting owner via Slack that the bot was disconnected, which allows them to either invite it back or manually record the session. Because this is a platform level action by the host, the API cannot override the host decision to remove the participant from the virtual room.

Alternatives to Recall.ai

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Otter AI logoOtter AIFireflies AI logoFireflies AIGong logoGong

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Recall.ai and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free