Introducing: The Form Connector

by David Simpson

You can now build web forms from within tray and use them as triggers. We've made it really easy to create a customised web end-point to kick off your workflows.

We use these forms internally for bug reporting, feature suggestions, and kicking off deployments (we'll talk about our automated deployment system more in an upcoming post) and we've decided to make this feature available for everyone.

Forms are handy for all kinds of data capture and often we found that we wanted to trigger a workflow manually, but with some configuration. When a form is submitted all of the values from its fields are available as the result of the form connector within the workflow.

Take a look at how forms are configured within tray here:

<iframe width="560" height="315" src="" frameborder="0" allowfullscreen></iframe>

There are a few nifty features in here. For example, the description fields all support markdown to provide flexibility when building your form. You can also add some simple authorisation to your form and require a user to enter a password in order to access it.

We've also included the ability to upload files and to show fields conditionally based on other fields. For example, your first field can be a checkbox which allows you to select which parts of the form to show.

Using tray's form builder means that you can build end-points for your workflows quickly without relying on another integration or polling a google sheet for updates. For example: our bug reporting workflow is triggered by a form which captures bug reports from sales engineers. The workflow then logs the bug in Clubhouse and sends a Slack alert to me so that it can be prioritised.

Next up we're looking into ways to make the form builder more user-friendly.