With the 10,000ft for Bridge integration, you can use the 10,000ft APIs and webhooks to build workflows that interact with APIs without having to construct API calls.
The integration consists of both triggers and modules, and can be used to start workflows based on changes in 10,000ft or to interact with 10,000ft in workflows triggered by another system.
You must have an account with 10,000ft and any other systems you want to include in your workflows.
You can start building 10,000ft workflows before authenticating or creating triggers, but you will get a popup reminding you to authenticate while doing so. You will not be reminded to create triggers, but you can review the Trigger panel in the designer to see if any exist for the workflow you are building.
- Log into Bridge by Smartsheet and navigate to the Integrations page.
- Locate the 10,000ft logo and click on it.
- In the Info tab click Continue, and then Authenticate in the Connect Tab. This will open up a new window asking you to give Bridge permission to your 10,000ft account.
- Click Allow to continue. The window will close automatically after 5 seconds.
Once authenticated you’ll be taken to a third tab called Triggers. You can choose to come back to this later or set up the triggers right away. Once you have added 10,000ft modules in a workflow you can also access this pop-up by clicking on the settings icon in the setup panel of the designer.
Frequently Asked Questions
How do I reference the value for Project Type in the triggers or modules related to projects?
Project Type is used to specify if a project is Confirmed, Internal, or Tentative. However, the label in the response from the 10,000ft API calls it Project State. It is therefore called Project State in the Bridge Run Log to follow the 10,000ft format.
How do I update another system with a work item's status when it changes if it is always blank in the Run Log?
A work item’s status will appear as status_option_label. You will not want to use the data label Status, as it is specific to 10,000ft only.
Why do I receive an error saying Time Entry Lockout field is incorrect?
The Time Entry Lockout field requires the values -1, 0 or any other number, but in the 10,000ft UI these numbers aren’t visible but represented by text. -1 Corresponds to ‘Do not lock time entries for this project’, 0 corresponds to ‘Lock all time entries for this project’ and any other numbers will result in the setting ‘Lock time entries for this project that are older than X calendar days’.