Recall.ai

Connect your Recall.ai meeting recordings to Cloudglue

Connect your Recall.ai account to use your media recordings with Cloudglue APIs.

Adding the Recall Data Connector

1. Navigate to the Data Connectors page in the Cloudglue app.
2. Click the Recall data connector card.
3. Follow the popup instructions to authorize Cloudglue access to your recordings.
4. Verify the connection by checking for the Connected indicator on the card.

Ready to set up your Recall data connector? Visit our app to get started.

Need help setting up your data connector? Contact our team directly for assistance with the setup process.

Using Recall with Cloudglue

To use Recall.ai recordings with Cloudglue, you can use the recall://recording/{recording_id} prefix in your Cloudglue API requests.

Example:

recall://recording/1234567890

Example API Request to get a multimodal description of a recording:

curl --request POST \
  --url https://api.cloudglue.dev/v1/describe \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "recall://recording/1234567890",
  "enable_summary": true,
  "enable_speech": true,
  "enable_visual_scene_description": true,
  "enable_scene_text": true
}'

Browsing and filtering recordings

GET /data-connectors/{id}/files lists recordings from your Recall account, and from/to filter by recording creation date.

curl --request GET \
  --url 'https://api.cloudglue.dev/v1/data-connectors/YOUR_CONNECTOR_ID/files?from=2026-06-01&to=2026-06-30' \
  --header 'Authorization: Bearer YOUR_API_KEY'

A date range can span multiple pages: when has_more is true, pass the response’s next_page_token back as page_token (with the same filter parameters) until it returns null.

Recall’s list API exposes no meeting title, so items are named Recall Recording {id}; the title (when Recall has one) appears as meeting_title inside each item’s metadata. title_search is ignored for Recall. Recordings of every status are listed — check metadata.status_code; only done recordings can be synced.

Source metadata

When a Recall recording is imported, Cloudglue captures the recording’s source metadata onto the resulting file under source_metadata: timestamps (created/started/completed/expires), status, meeting title and platform when available, artifact availability flags (has_transcript, has_audio, has_participant_events), the capturing bot’s id, and any custom metadata you attached to the bot in Recall. Signed artifact download URLs are never stored. The source_metadata field is returned on the file object.

GET /data-connectors/{id}/source-metadata previews a recording’s source metadata without importing it:

curl --request GET \
  --url 'https://api.cloudglue.dev/v1/data-connectors/YOUR_CONNECTOR_ID/source-metadata?url=recall://recording/1234567890' \
  --header 'Authorization: Bearer YOUR_API_KEY'

UI Importing for Testing

Use the Cloudglue integration UI to quickly import Recall files for testing your endpoints.

To access this page, visit our app and click on Select Videos on the Recall connector.

Managing Access

You maintain full control over your data access. To remove the Recall Data Connector, visit the Data Connectors page and click Disconnect under Recall.

Once removed:

• You cannot import new recordings into Cloudglue until you reconnect.
• Any recordings you previously imported will remain in Cloudglue. These can be viewed and deleted from File Management.

Security

Cloudglue uses your Recall.ai API key to securely access your recordings. This approach:

• Maintains your control - You own and manage the connector. Revoke the API Key at any time to stop Cloudglue from accessing your recordings.