Buildable
Search…
Environments
A simple summary of Buildable's development environments, error management and debugging tools
Every Flow has two distinct development environments for testing and production. Every new Flow starts in the test environment, called Workstation, by default. Once testing is complete, developers can easily deploy the Flow to production. Let's learn more about these powerful environments and why they're useful for rapid development.

Starting in Workstation mode

When you create a Flow, you're automatically dropped into the Flow's test environment, called Workstation. You'll notice you're in Workstation mode by the environment label in the header of the Flow editor, which says Workstation in yellow. You'll also notice your Flow's unique URL has an environment label, called 'test', embedded just before the Flow's Trigger ID.

Testing your Flow

When in a selected step, simply use the Test Step button on the top right of the sidebar drawer to execute the test. Once activated, the results will appear in a window that slides from the bottom of the drawer with the appropriate response.
When you're ready to test all steps of a constructed Flow, simply use the Test Flow button on the right side of the Flow editor's header to activate the full recipe test. The sidebar drawer will convert to a test console, which indicates the result of each step.
You'll also notice a red error notification beside the step card that has the error if an error is present.

Deploying your Flow to Production

Once you're done testing your Flow, you're ready to deploy to production. To do this, you simply need to click the Deploy button in the top right corner of the screen.
When you deploy a Flow, Buildable automatically spins up an entirely separate live environment for your Flow, called Production. You'll notice you're in Production mode using the environment label in the header of the Flow editor, which now says Production in green. You'll also notice your Flow's unique URL has an environment label, called 'live', embedded just before the Flow's Trigger ID.
If you're connecting Flows to frontend code in user apps or internal tools, you can easily set up a config that can alternate the environment label depending on whether you're activating in staging or production. This is easy because the Flow's Trigger ID (i.e., the last string of text in its Endpoint URL) is the exact same between Workstation and Production versions. The only difference is the environment label.
Example
If you had a Flow in Workstation mode, its Endpoint URL would like this:
1
https://api.buildable.dev/trigger/v2/test-f9830903-ad71-4450-b71e-1a5a68c8b387
Copied!
Once you deployed this Flow to production, its Endpoint URL would like this:
1
https://api.buildable.dev/trigger/v2/live-f9830903-ad71-4450-b71e-1a5a68c8b387
Copied!

Toggling between Workstation and Production

Once deployed, you can easily toggle between your Workstation (i.e., test) and Production (i.e., live) versions by clicking the environment label in the header of the Flow editor.
A Buildable developer toggling between Workstation and live environments
For safety reasons, you cannot make edits directly to a Production Flow. To make changes in Production, you need to switch to the Flow's Workstation mode, make your changes and deploy again.
Last modified 2mo ago