Skip to main content
A Mission is a saved workflow. When you run a multi-step command in the Command Center — something like pulling data from Slack, summarizing it, and creating tasks in ClickUp — Bridge can save that entire sequence so you can run it again later without retyping anything. Missions are how you turn a one-off command into a repeatable process.

​
What a Mission contains

Every Mission captures the sequence of tool steps from a successful execution, plus the values that were used in that run. Those values — a ClickUp workspace ID, a list name, a Slack channel, a date range — become variables you can override each time you replay the Mission.

Steps

The ordered sequence of tool calls that Bridge executed: for example, “fetch Slack messages → summarize with AI → create ClickUp tasks”. The step pattern is fixed when the Mission is saved.
Named placeholders for values that were specific to the original run. When you replay the Mission, Bridge presents these as fillable fields so you can target a different list, channel, or date range without editing the underlying steps.
The set of connectors the Mission needs to run. Bridge shows a warning if any of them are not currently connected when you try to run.

​
How Missions are created

Bridge watches for multi-step executions that went well. After a successful run, it may show a Save as Mission? prompt at the bottom of the conversation.
1

Run a multi-step command

Execute any command in the Command Center that triggers multiple tool steps — for example:
2

See the prompt

If the run succeeded and used two or more tool steps, Bridge shows a Save as Mission? card below the response.
3

Click Save

Click Save. Bridge names the Mission based on the command you typed and extracts the variable slots from the step inputs.
4

Edit the name (optional)

You can rename the Mission immediately after saving, or later from the /missions page.
Not every multi-step command triggers the save prompt. Bridge uses the number of steps, the connectors involved, and whether the execution completed without errors to decide when to offer it.

​
How to run a Mission

1

Go to the Missions page

Navigate to /missions in the Bridge dashboard.
2

Select a Mission

Click the Mission you want to run. Bridge opens the detail view showing the step pattern, required connectors, and any variables.
3

Fill in variables

Review the pre-filled values (carried over from the original run) and change any that should be different for this run — a new date range, a different list, a different channel.
4

Click Run

Bridge executes the full step sequence with your updated variables. Progress appears in the same Progress Panel you see in the Command Center.

​
Mission variables

Variables are the dynamic parts of a Mission. They are extracted automatically from the inputs of each step when the Mission is saved.
If a variable you expect to change often is showing as fixed, you can split the command differently — for example, name the list explicitly in your command so Bridge captures it as a variable rather than resolving it automatically.

​
Mission history

Each Mission card on the /missions page shows:
  • Run count — how many times this Mission has been executed
  • Last run — when it was last triggered (shown as relative time, e.g., “3h ago”)
Use this to track which Missions your team relies on most and to spot ones that haven’t been used in a while.

​
Use case examples

Weekly standup summary

Pull Slack messages from your standup channel, summarize action items, and post a digest to another channel — every Monday morning.

Client onboarding checklist

Create a set of ClickUp tasks, send a welcome email via Gmail, and add the client to your HubSpot CRM — all from a single run with the client’s name as a variable.

Transcript to ClickUp tasks

Paste a meeting transcript, have Bridge extract action items, and create a task in ClickUp for each one assigned to the right team member.

Command Center

Where you run commands that can be saved as Missions.

Plays

Pre-built instruction sets that make complex commands more consistent.