Record on a calendar event

This recipe starts a recording when a calendar event begins and stops it when the event ends. The trigger - a calendar integration, a cron job, or a scheduler - is yours; this page shows the Meetily calls it makes. Set $MEETILY_PRO_TOKEN to a record-scoped token first, and turn on the Automation API under Settings > Integrations (see Enable & connect).

Start at the event start

When your trigger fires at the event's start time, call POST /v1/recording/start. Its body fields (meeting_name, mic_device_name, system_device_name, consent_attested) are all optional.

curl -s -X POST http://127.0.0.1:8420/v1/recording/start \
  -H "Authorization: Bearer $MEETILY_PRO_TOKEN" \
  -H "content-type: application/json" \
  -d '{"meeting_name":"Weekly sync"}'

meetily-pro recording start --meeting-name "Weekly sync"

Stop at the event end

When your trigger fires at the event's end time, call POST /v1/recording/stop.

curl -s -X POST http://127.0.0.1:8420/v1/recording/stop \
  -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

meetily-pro recording stop

Confirm it started

To be sure capture began before you rely on it, wait for the started transition on the recording wait stream. This is a one-shot SSE endpoint - it emits a single event, then closes - and it needs only read scope.

curl -N -s "http://127.0.0.1:8420/v1/recording/wait?until=started&timeout=30" \
  -H "Authorization: Bearer $MEETILY_PRO_TOKEN"

There's no CLI equivalent for the wait stream - use curl -N. You can also read the current state at any time with GET /v1/recording.

Before wiring a trigger up, a cheap GET /health (no token) or meetily-pro doctor first lets it fail cleanly when Meetily isn't running. See Meetily APIs for the full recording route surface.