Product Update - June, 2021

The new release is here and it brings really important features when it comes to integrating third-party services in your flows. Discover the new email verification and subscription payments templates too and how to use the ‘Undefined’ value in variables.

Centralize and reuse app connections

Save even more time when configuring native actions to integrate third-party services and centralize the connection data used in your flows, with a new field and the vault.

The new connection field

When adding actions to your flows, you will find that a new field called ‘Connection’ has replaced the ones we had before to configure the connection of third-party services: the Base URL, API keys, Secret keys, etc.

This new field allows you to create, save and reuse connection data, so that you do not have to copy and paste it every time you add actions for that service to your flows.

To create a connection, just click on the plus button of the field to open the settings. 

There are 3 options to configure a connection:

• With API keys, getting them from your account in the service you are configuring.
• With OAuth, which is available for services like MailChimp.
• Creating an empty connection and filling data later. If you do not have the data at the time, you can choose this option and paste the keys later. 
  

The most common scenario is to create it by pasting the keys from your account in that service. Once pasted, simply click on 'Add connection' to save them.

When configuring services with available OAuth connections, the three possibilities will be displayed in the window so that you can choose the one you prefer.

Once you have added it (either with OAuth, API keys or empty), the new connection will appear in the field selector.

Now you can reuse the connection in all the actions of this service, simply by selecting it.

The connections vault

Check and edit all your connections in the Vault section, under the user menu.

Click on the service whose connections you want to edit to open the list and access the settings.

Here you can edit the name of each connection, change the connection data by clicking on the ‘Reconnect’ option or delete them.

Connection data is not visible in the editor, not even here or in the debugger mode.

The legacy authentication mode

If you already have flows and actions with connection data in your workspace, you will be happy to know that the data you have configured has not disappeared.

You will see that we have placed, in the actions that you already had configured, an option called ‘Use legacy auth’ which allows you to still use the fields prior to vault deployment.

To start using the vault, disable this option and create a new connection with that data.

New ready-to-use templates

There are two new templates available in Arengu: one to build a signup form with email OTP verification and another one to create subscription payment forms.

Templates allow you to create fully customizable use cases without effort, since both the form, as well as the flows and their actions are already configured.

Simply edit content and CSS styles, and include the connection data of your API and the external services that you want to use in the flows, using the vault.

Using the ‘Undefined’ value in variables

Now you can use "undefined" values in variables to not send a variable in case it has no value or it is 'null', for example, if we have an HTTP Request that sends this in the JSON:

{
    "email": "{{ fields.email }}",  
    "password": "{{ fields.password ?? undefined }}",
}

In this example, if we don't add the ‘?? undefined’ value, even when the password is null or an empty string (``), it would send the ‘password’ property with that value in the request.

By using it, the property is removed and it would be sent the following data:

{
    "email": "{{ fields.email }}"
}