The flow editor
Easily configure custom server-side logic, integrate any service with an API and automate tasks in any stage of the form.
Execute custom server-side logic flows in any step of the form. Validate data, jump between steps, integrate any service with an API and trigger different actions and automations based on form inputs.
Get data from your form fields and from previous flow actions using the autocomplete data menu.
Simply configure action fields by selecting the variables you need from previous executions of the flow.
Use math operators to do calculations and build logic based on its results. You can even use advanced functions as round, generate random numbers, transform between data types or use nullish operator "??" to build your logic.
Store custom variables and use them both in the form and the next flows linked to it.
Transform data, pass it through the different flow actions, use it to prefill form inputs or to modify form fields configuration.
Generate temporal codes with native actions and send them to an email or a phone to verify that your user has access to it. In addition, you can block free emails and configure which domains are allowed.
Check if everything is working properly by debugging your flows, action by action. Easily find and solve bugs by inspecting the inputs, outputs and errors of the actions of your flows after any execution.
Send your data back and forth between Arengu and your favourite apps.
Everytime your flow is executed, Arengu lets you inspect and debug it by showing a data history with inputs, outputs and errors of every action of your flow.
Arengu is different because you can also create the server-side logic for your forms. Apart from being a form builder, you can add logic without coding, in order to create complex behavior, such as conditional logic, dynamic behavior, add integrations, or call your own API, among others.
Plus, you can completely customize this server-side logic, so your forms and flows adapt totally to your business needs.
Yes!
You can create a free account and start creating your first forms and flows. If you need a large amount of submissions, workspaces to work jointly or other extra features, you can see our pricing plans.
A flow is a series of actions that take place in the background of your form, composing the server-side logic of it. Flows can be linked to different stages of the form: after or before submission.
In order to create a flow, go to the Flows editor and click on Create a flow. There you can open the suite of actions, where you can find every action you can add to your flow. Click on the action you want to add, and configure it accordingly. If you don’t find the action you need, you can create one of your own with an HTTP action, and send a call to the API you need.
When you’re done configuring your flow, remember to link it to the preferred stage of the form, in the Forms editor.
Arengu offers native integrations with some of the most popular apps. These include CRMs, email providers, SMS providers, communications tools, and much more. Currently, Arengu offers native integrations with ActiveCampaign, Clearbit, Hubspot, MailChimp, MailJet, Pipedrive, PrestaShop, SendGrid, Slack, Telegram, Twilio, WordPress, and Zapier.
Plus, you can call any API with an HTTP action, which allows you to connect Arengu with your own services. You can check here all the integrations, actions and widgets available to create completely personalized flows.
The Flows editor is where the magic happens. Here, you will be able to create and implement server-side logic, without the need of coding.
Thanks to this, you can create personalized behavior for your form and target specific use cases that can be a great help for your business. For instance, you could create a form with multi-factor authentication systems, passwordless forms, dynamic forms with conditional logic, and much more, without wasting development resources.
Arengu’s actions need to be configured in order to work properly. Every action requires some mandatory settings, such as secret API keys, or input references. You can find detailed information about each action’s configuration in our Documentation.