Guides & tutorials
Guides & tutorials
You've heard it before: Arengu is much more than a form builder, it's the brain behind your forms. And the flows editor is the section you need to add this intelligence to your forms, the section where you can build server-side logic without having to code.
Adding flows to your forms is the way to obtain smarter forms, apply your own business rules, trigger dynamic behavior, or adding integrations with third-party tools, among others. Find here everything you need to know to get started with Arengu's flows.
Flows can be added in different stages of your form. Consider what actions you want to trigger in every stage of the form to add the logic in the right moment.
The Flows editor allows to add different types of actions, make connections between them and connect them to your form. By adding actions, you can create a personalized and flexible behaviour for your forms.
The suite of actions will open once you click on the plus button in the editor. In the suite of actions, you will see different types of actions. This is everything you can find here, and what you can do with them, in a nutshell:
In order to execute actions and complement your form's behavior, you can use form-related actions, that don't require external platforms. These actions include a wide variety of actions: generating and verifying one-time passwords, setting cookies, mapping input data, verifying email addresses, and more.
Since these are Arengu's own actions, you won't be needing any API keys or external values. All you need to do is adding references, so these actions are connected to each other.
👉 Making references to input and output values is key to interconnect every piece of your and get it working. Learn more about our referencing system with our step-by-step guide.
Arengu's actions also help you set a defined navigation process along the form. You can choose to skip steps and jump to a selected step, continue with the predefined order of steps, and more.
These actions allow establishing different form paths for different users. When combined with the If/then condition, you can apply your own conditional logic and then trigger different form paths for a dynamic and personalized form.
Configuring form navigation actions include selecting the step where you want the user to be sent.
Use native actions to trigger events that happen in third-party platforms.
You can use these actions to create form actions for a particular platform —like the WordPress and PrestaShop actions— or to add integrations with third-party tools or platforms. This is useful if you want to connect your form with your day-a-day tools, to execute actions related to the flow, or to automate actions.
You can find integrations with Clearbit, Hubspot, MailChimp, MailJet, Pipedrive, PrestaShop, SendGrid, Slack, Telegram, Twilio, WordPress, Zapier, and more.
In order for the native actions to work, you need to have an account in the correspondent platform. The connection is API based, so you need to find your API keys in your account settings, in the correspondent platform.
The If/then condition is the action you need if you're looking to build conditional logic. This action will generate branches, and trigger additional actions of your choice. Hence, you can use it to trigger different behaviors according to your own business rules.
In order to add conditional logic to your Arengu form, select the If/then condition from the suite of actions. Then, select the rules you need to apply. Select the condition from the drop-down menu, and add additional criteria if necessary.
If you didn't find the action you need, you can use the HTTP action to connect Arengu with any third-party service, as long as it has an API. Therefore, if you're missing a certain native action or if you want to connect to your own services, you can do so by adding and configuring the HTTP action.
This "magic" action allows you to call any API and execute the actions you need. Keep in mind you will need basic coding skills to configure it.
When working with JSON objects or using your own HTTP actions, you can use this set of tools for a variety of actions: converting objects in different formats, serializing strings, creating JSON objects and more.
The executions tab is the place where you will find every flow execution. Here, you can find a list with all the executions, and click on each of them to see the details.
If the process went wrong, the execution will be listed in red under Failed. Open it to see the error and easily debug it. After this, your flow will be working correctly.
You can also check the executions tab to find valuable information, such as output data returned from third-party actions. In the example below, you can find all the data that was gathered by Clearbit, and that is now part of your user's database.