Triggers are what initiates a workflow, and there are a few different ways you can use them.
Some of the integrations available in Bridge can act as workflow triggers. To enable these, navigate to the Integrations page in Bridge and follow the steps to authenticate and setup the integration.
The following integrations can be used to trigger a workflow:
NOTE: Currently only set up Smartsheet triggers are visible in the designer's trigger panel.
Workflows can be set up to trigger other workflows. We call these parent and child workflows. A workflow can have one or more parents and one or more children.
Create a parent/child relationship:
- Open the parent workflow and add the Run Child Workflow module.
- In this module’s setup panel, set the name of the child workflow it should trigger under Child Workflow Name.
- Save this workflow.
Now if you navigate to the child workflow and click on its Trigger, you will see the name of the parent workflow listed in the Trigger panel. Learn more about parent and child workflows here: Use Child Workflows to Manage Complex Processes
If your workflow is chat-based, you can define phrases that trigger your workflow.
- Click on the Trigger element at the top of your workflow to see the trigger panel.
- Expand the section called Phrases and add one or more words or phrases that should trigger your workflow.
You can make a workflow trigger another workflow, or itself, on a regular cadence by using the module Schedule Start Conversation.
There may be times when you want to trigger a workflow manually:
- Open the workflow in the designer.
- Click on the chat bubble in the top bar, second from the right.
- Click on the play button in the window that opens up.
NOTE: You can also start a workflow with a trigger phrase from here.
If Bridge is not integrated with a 3rd party tool that you would like to use to trigger workflows, you can define these triggers yourself.
- Navigate to the Integrations Page.
- Find the Inbound Webhooks icon.
- Fill in the required information.
You will first need to make sure that the other system offers relevant webhooks associated with the trigger events you'd like to use and that this system does not require validation of webhook endpoints.