EN
Meeting APIClosed beta

Automatic meeting recording API for Google and Outlook calendars

Turn matching calendar events into scheduled notetakers, for the CRM, ATS or AI agent you build. When a meeting moves or is cancelled, its capture follows automatically, with one configuration per connected account and no scheduling database to maintain.

In closed beta. Contact us to get access.

How it works

How automatic meeting recording works with a connected calendar

Your user connects a calendar, one configuration decides which events get a notetaker, and every new, changed or deleted event creates, moves or cancels its capture.

  1. Step 1

    Connect the calendar

    Your user connects a Google or Microsoft account through Unipile. The same account powers the Calendar API, the Email API and the Notetaker API.

  2. Step 2

    Set the recording rules

    Choose internal or external meetings, host-only rules, confirmed events, recurring meetings and whether private events are excluded.

  3. Step 3

    Reconcile existing events

    Run calendar-sync once for the next 1 to 28 days. New, updated and deleted events are handled automatically afterwards.

Recording rules

Which meetings get recorded? Set the rules once

Six rules, combined per connected account, decide which events receive a notetaker. Record customer calls without recording every event indiscriminately.

Rule What it does
External meetingsrecord_external

Captures calls with customers, candidates and partners outside the organisation.

Internal meetingsrecord_internal

Includes or leaves out meetings between colleagues of the same organisation.

Host onlyrecord_only_host

Limits automation to meetings organised by the connected user, when your policy requires ownership.

Confirmed attendancerecord_confirmed

Avoids sending a notetaker when the user declined or has not confirmed the invitation.

Recurring meetingsrecord_recurring

Includes or excludes recurring series, without writing recurrence expansion and rescheduling logic yourself.

Private event exclusionexclude_private

Keeps events marked private out of automated capture, independently of the other rules.

Event lifecycle

What happens when a meeting is moved or cancelled

The notetaker follows the source event, with no scheduling database to maintain. Calendar automation is not a daily batch that goes stale.

  • Initial reconciliation

    calendar-sync imports the events already planned in the next 1 to 28 days and schedules those that match your rules.

  • Live updates

    After that, Unipile reacts to Calendar event creation, updates and deletion. A changed start time updates the planned join; a cancelled event cancels the scheduled notetaker.

  • Same webhooks as manual jobs

    Every automatic capture uses the standard Notetaker API lifecycle and artifact webhooks, so manual and automatic jobs share the same backend code and the same transcripts.

Request and response

Configure automatic recording with one API call

Create one account-scoped notetaker-configuration, then run calendar-sync once. Settings are versioned and resolved again before a scheduled notetaker is dispatched.

Requestcreate-configuration.sh
curl --request POST \
  "https://api.unipile.com/v2/notetaker-configurations" \
  --header "X-API-KEY: $UNIPILE_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "name": "Automatic customer meetings",
    "scope": { "type": "account", "id": "'$ACCOUNT_ID'" },
    "settings": {
      "calendar_automation": {
        "enabled": true,
        "record_internal": false,
        "record_external": true,
        "record_only_host": false,
        "record_confirmed": true,
        "record_recurring": true,
        "exclude_private": true
      },
      "artifact_settings": {
        "transcript": { "enabled": true },
        "summary": { "enabled": true },
        "action_items": { "enabled": true }
      },
      "retention": { "type": "timed", "hours": 72 }
    },
    "deduplication": "enabled",
    "quota_mode": "metered"
  }'
Initial reconciliationcalendar-sync.json
{
  "object": "NotetakerCalendarSync",
  "scanned_events": 18,
  "scheduled": 6,
  "updated": 1,
  "cancelled": 0,
  "unchanged": 11
}

The full configuration reference is in the developer documentation.

Deduplication

One meeting, one capture, even with several connected attendees

When several of your users are invited to the same meeting, eligible scheduled jobs in the same account scope share one capture. More on the Notetaker API page.

  • No duplicate bots

    No duplicate participants and no duplicate usage, however many connected attendees are invited.

  • Rules per customer

    Configuration is inherited from the application and overridden for an account scope or one connected account.

  • Metered or hard limit

    Allow paid overage or stop new dispatches at the included quota, according to the customer's plan. See Notetaker pricing.

Automatic meeting recording: frequently asked questions

Calendar sync, recording rules and rescheduled meetings, answered for developers.

The calendar-sync endpoint accepts a lookahead from 1 to 28 days. New and changed events keep syncing automatically after that initial reconciliation.

Yes. Internal, external, hosted by the user, confirmed, recurring and private events can each be included or excluded, per connected account.

Subsequent Calendar update events move the scheduled notetaker. Deleting or cancelling the source event cancels its scheduled capture.

Yes, when the confirmed attendance rule is on: no notetaker is sent when the user declined or has not confirmed the invitation.

Yes. Configuration can be inherited from the application and overridden for an account scope or one connected account.

Still have questions? Our team is here to help.

Talk to an expert