Bridge: Key Concepts and Terminology

Applies to

Bridge by Smartsheet


Who can use this capability

People with a Bridge account can create, view, edit, and delete workflows, workspaces, integration authentications, and manage users.

Bridge is available for purchase with an Enterprise Smartsheet plan.

As you get started using Bridge by Smartsheet, having a basic understanding of key concepts and terminology will help you get up to speed faster. This article will help you do that.


With Integrations, you can connect Bridge to other systems, using them to send or receive information from and to Bridge and, some of them, to trigger workflows.


For a workflow to run it needs to be triggered. A trigger can be based on a scheduled time, other workflows, integration triggers, and more. For more information about using webhooks with Bridge, see the Inbound Webhook topic on the Bridge technical documentation site.


States are the individual stages of a workflow. Depending on if you're building a workflow with chat or not they can be used differently.

States act like data collectors in workflows. If you are building a chat based workflow, this is where the questions are asked and user responses stored. If you are building a fully automated workflow the data collected from other systems is stored here too. The state's name influences the data references in the workflow.


Modules are the various elements of integrations and utilities. They can be used to send or collect data to and from 3rd party tools or manipulate data within a workflow. They will run once the previous state has been successfully processed.

With modules you can:

  • push updates from a workflow 
  • pull information into a workflow in real time
    - OR - 
  • manipulate already gathered data for use in other parts of the workflow.

Data References

A key strength of Bridge is the ability to Reference Data gathered at a previous point in a workflow, to dynamically set values and inputs.

Child Workflows

Child Workflows are workflows that are triggered by another workflow, called a Parent Workflow. This may be useful when your workflow is complex and breaking it into multiple pieces would make it easier to read. Additionally you might have several workflows where a portion of each is the same. Instead of building the same steps over and over you can build it in a child workflow and trigger it from all the other workflows.


Contexts are libraries of phrases used for chat based workflows. Instead of defining a range of words to look for each question asked, within each workflow you can create contexts and simply reference them in any number of workflows. Bridge comes with a large catalogue of contexts or you can create your own.


Junctions let you route workflows in different directions as needed.