Skip to main content
Admin automations are the recording automations workspace Admins configure in the Claap workspace settings. An automation is defined by 3 key components: a priority, a set of filters, and a set of actions. The endpoints live under /v1/admin-automations. Managing admin automations requires a workspace plan that includes them; on other plans the endpoints fail with a forbidden error.

​
Priority

Automations are ordered: the first automation in the list has the highest priority. By default newly created automations are placed first. To control the position, set beforeAdminAutomationId when creating or updating an automation: it is inserted (or moved) right before the referenced automation. When the referenced automation does not exist, the request fails with a validation_error. When beforeAdminAutomationId is omitted on update, the automation keeps its current position.

​
Filters

Filters select which meetings an automation applies to. An automation without filters applies to all meetings. Each filter has a type (matching on the meeting type, organizer, participants, recording team, title, source or folder), can be negated with not, and combines with the other filters through combineWith (And or Or). When a filter does not define its own combineWith, the top-level combineWith value of the request (Or by default) is used. Filters can be grouped with the Group filter type, but groups cannot be nested. Some combinations are rejected: for instance the autoRecord action cannot be combined with a FolderIs filter, since the folder of a recording is only known after the meeting is recorded.

​
Actions

An automation automatically applies one or more of the following actions to the recordings matching its filters:
  • autoRecord records matching meetings (or prevents them from being recorded).
  • autoShare controls how matching recordings are shared: who they are shared with, how they are published in the workspace and whether a public link is enabled.
  • moveToFolder adds matching recordings to a folder (aka channel).
  • updateOverview personalizes the AI notes of matching recordings with the given summary sections.

​
Enforcement

By default automations are enforced (disallowUserOverride: true), meaning members cannot override them with their personal preferences. Set disallowUserOverride to false to let personal preferences win.

​
Full replacement updates

The update endpoint performs a full replacement, not a partial update: the automation becomes exactly what is sent, and omitted attributes are reset to their default values instead of being preserved. Always send the complete desired actions, filters, combineWith and disallowUserOverride values.

​
Name generation

The name attribute is optional when creating or updating an automation. When omitted, a name is generated from the actions and the first filter, for instance Auto-record, Auto-share on internal meetings and other filters.