Deploy
Last updated
Last updated
The deployment process holds significant importance within the workflow creation cycle. It serves as the pivotal step that not only saves all the modifications made to your workflow but also meticulously verifies that the finalized workflow, complete with all its connections and intricacies, is fully functional and error-free.
Moreover, deployment grants you access to a designated URL specific to your workflow. This URL acts as the primary gateway to your workflow, providing you with a direct means to thoroughly test its functionality and performance.
The deployment process offers developers swift access to the workflows they create. It's not just about speed, but also about ensuring safety and security. This method provides a fast, reliable, and secure means for developers to deploy their workflows.
Deploying your workflow is as simple as clicking on the deploy button located at the top right corner.
Once clicked, a loading toast will appear, indicating that the deploy process is underway.Once the deployment process is finished, an information tooltip will appear, containing comprehensive details about your deployed workflow.
Workflow name is the name you typed on the creating of the workflow. The workflow name will also be part of the Workflow URL.
Workflow URL is the result URL that will be available to be used and called anywhere you need this response. The Trigger node have the PATH field, where if you change the information inside of it, it's also going to be part of the result URL.
Here you can decide how you want to call your workflow using all the REST methods (GET, POST, PATCH, PUT and DELETE).
If you need more information on how that works, please check the Trigger section.
