Synchronous automations allow users to receive feedback from their automation, in the Design section or via a webhook response.
Automations are usually asynchronous, this means that when an automation runs, it does so in the background and the user is unable to access its result, but with synchronous automations the result is available to the user.
The following features are available to:
- All installations with a Business or Enterprise license
You can make an automation synchronous by adding a Collect Data step.
A Collect block will simply return whatever binding or value is passed to it.
As the Collect Data action returns data from your automation, it must be the last step. Otherwise you will see that the action is greyed out:
When using the Webhook trigger, you can return data to the caller of the trigger URL.
For example consider this webhook automation that queries an Employees table, filtering on the City that is passed into the trigger:
We can then specify data that should be returned to the caller of the trigger, in this case simply all of the rows matching the city provided.
After publishing this automation, we can see the result in our POST request:
You can now see the response from the Collect Data step has been provided in the response of the trigger call. Note that value in this case is a string - this is because Handlebars always return strings.
And now the result:
For users to access the result of your automations in a published Budibase app, you will need to configure an App action trigger within the Design section. Click on
Define actions to open the actions drawer to create a new or use an existing synchronous automation.
As shown in the screenshot, a synchronous automation can run for up to 120 seconds, or less if required.
Once added this provides a binding with the result of the automation to any following action, through Chaining actions.
In this example, we will use the binding to add the result of an automation into App state and then display it in a paragraph component.
When the button with these actions attached is clicked, state will now be updated with a key called
result that contains the result of our automation.
To display this we now simply to need bind the state to the paragraph.
We can now preview our app and click the Button for which our actions are defined.
The automation result is stored in to state, and due to the binding of that state to the paragraph, appears on screen whenever the
Trigger button is clicked.
Instead of displaying the result in a paragraph, you could just as easily use the Show Notification action, or any other combination of actions.
The automation result binding will only be available if your automation has a Collect Data step.
Updated 5 months ago