Workflowscoming soon

Frozen trigger ids

These four trigger ids are frozen now, so a workflow authored against one of them won't need to change later. Each maps to a specific backing event.

transcript-ready has no producer in this release. It will not fire until the Workflows release ships, and there's no ETA for that yet. It's reserved and won't be dropped from this list.

Build against the API today

You don't need to wait for Workflows to react to these same events. Webhooks & SSE and Events already cover subscribing to recording.stopped, summary.completed, and job.completed, then fetching the actual transcript, summary, or meeting content with a scoped token once the event arrives.

What is coming (not yet available)

Workflows will package this into something you can author once and distribute, instead of hand-rolling a webhook receiver per automation. Planned pieces:

• A manifest schema, plus an authoring CLI/SDK.
• An out-of-process sidecar runtime, so a workflow runs outside Meetily's own process.
• Install and consent sheets, so a person installing a workflow sees what it can access before it runs.
• A trigger-picker UI, built on the frozen trigger ids above.
• Per-workflow data directories.
• Distribution and Verified tiers.

None of this changes how a workflow runs relative to recording, transcription, or summary generation: a workflow stays off the hot path, its execution is bounded, and it's measured against the same 6-KPI budget the rest of the app is held to.

The platform is already workflow-ready: a workflow consumer kind is reserved in the token model today and will slot in when this ships, with no schema change needed.

Start building today

The meetily-workflows examples repo has working examples against the current API, including an unsupported, vendored Python helper. It's a good place to start building today, ahead of the packaged Workflows release.