AssistantAutomations

Automations

Create and manage Automations across your Bridge workspace with the Bridge Assistant.

Automate workspace actions with Assistant

Ask the Assistant to manage your workspace by renaming meetings, organizing meetings into Spaces, sharing meetings, applying labels, creating agents, and more.

Before a proposed workspace action runs, the Assistant shows a summary, risk level, preview or affected-item count, and consequences. You can confirm or cancel the proposal.

An action can complete, complete partially, or be unsuccessful. Completed or partial actions may offer undo when undo is available and safe, and undo may require confirmation.

Automations let Assistant perform recurring actions based on your needs. You create and edit them by talking to Assistant rather than filling out a separate form.

Find actions that are still processing, or review proposals and results, in Action History and Automations.

Create and manage Automations

Use a direct instruction that describes the event and the action you want. For example:

  • "Always rename meetings with John to Sales Sync."
  • “Always put meetings with @acme.com into the Acme Space.”
  • “Make new customer Spaces private.”

Open Assistant

Open Assistant and describe the recurring action you want to create or change.

Describe the trigger and action

Include the event that should start the Automation and what Assistant should do. You can specify meeting participants, meeting titles, labels, Space names, access settings, or more.

Review your Automations

Open the Assistant menu and select Automations. Review each Automation's name, When → then summary, saved instruction when available, run count, last-run time, and paused state.

You can pause or resume an Automation from its card. Deleting an Automation stops future runs but does not undo changes it already made.

Deleting an Automation does not reverse its previous effects.

For related workspace actions, see Assistant capabilities.

Automate actions when meetings are completed

A meeting-completed Automation can inspect:

  • Participant email addresses
  • Participant email domains
  • Participant names
  • Keywords in the meeting title
  • Meeting labels

Choose whether the conditions must all match or whether any matching condition is enough.

The supported meeting actions shown in Automations are:

  • Add the meeting to a Space
  • Add labels
  • Apply a recap template

Apply a meeting Automation to existing meetings

Meeting Automations include Apply to existing meetings. Use this option when you want to check past meetings against the Automation.

The operation creates a normal workspace action proposal. Review the affected meetings and confirm the proposal before Bridge applies the changes. If no meetings match, Bridge displays No existing meetings match this automation.

Applying an Automation to existing meetings requires confirmation.

Review Action History

Action History records workspace actions that were made or proposed by:

  • Assistant
  • Automations
  • Connected AI apps

Open the Assistant menu and select Action History. Entries appear newest first. Each entry identifies its origin, such as From chat, From a Space, From a meeting, From an automation, From the app, or From a connected AI app. Actions linked to a named Automation appear as Automation: automation name.

Review and control actions

Action cards show the action summary, risk level, affected items, and available results. Depending on the action, you can:

  • Confirm a proposed action
  • Cancel a proposed action
  • Open Details
  • Undo a completed or partly completed action when undo is available

Action statuses include:

  • Needs your confirmation
  • Working on it
  • Done
  • Partly done
  • Failed
  • Cancelled
  • Expired
  • Undone
  • Undo failed

Completed actions can group affected items into Done, Failed, and Skipped results. High-risk proposals can also show consequences before you confirm them.

Undo is available only for actions marked as undoable. Bridge may request another confirmation, and it will not undo a change when a later edit makes restoring the previous state unsafe.