News & Updates

October 25, 2020

April 11, 2022

Product Update - April, 2022

Table of contents

The new release is here with the first set of native widgets!

Forget about coding features to block spam, autocomplete addresses or check ID cards from scratch, and configure them by simply copying and pasting a couple of data, plus secure your API connection data with the vault. Keep reading!

The Google reCAPTCHA widget

Start using Google's v2 Invisible reCAPTCHA badge in your forms by simply dragging and dropping it, plus copying and pasting the Site key and the Secret key of your account.

Google's reCAPTCHA will not bother your users unless it considers them to be spam. When a user clicks the submit button on the form, it will assess a risk score and, if necessary, display an image reCAPTCHA to solve. The form will not be sent until the user solves it.

Block spam and brute force attacks without adding friction to your forms. You will find it especially useful in flows that trigger actions with associated costs, such as SMS, coupons, etc. 

The Google Address Autocomplete

Allow users to easily and quickly fill in addresses, and avoid human errors, such as misspelling or wrong zip codes, by automatically completing and validating them with Google Maps.

Configure this widget by simply copying and pasting the API key of your Google Cloud account. No further configuration is necessary.

Once the form is submitted, you will get an object with the location data in standard GeoJSON format, as you can see in the example below, so you can reduce form fields and friction.

The Passbase ID verification widget

Identify and verify users with government ID documents and facial recognition by embedding the Passbase widget in your forms.

To configure this widget, just copy and paste the Publishable and the Secret key of your Passbase account. You can also edit the text of the button that starts the verification, plus automatically send input email and country variables to pre-fill those fields.

For privacy reasons, Arengu will filter the output data of this field, so it can't be seen in the editor. However, you can get all the data in Passbase using the verification ID. This is an example of the output data that you will see in the ‘Submissions’ tab of the editor:

Thanks to the integration of Passbase and Arengu, you can build user verification forms in no time and trigger different actions based on it, by including conditional logic actions.

New connection field: ‘HTTP Request’ actions

When using ‘HTTP Request’ actions, you will find a new field called ‘Connection’. Just like in all other native actions, this field allows you to create, store and reuse connection data, so you don’t have to add it every time you configure a request for the same API.

Just click on the plus button to create a connection or select an existing one. This field allows you to store your API’s Bearer token in the vault, instead of inputting it in the 'Headers' field.

From a security perspective, this is also a better solution because the data stored in the vault is not visible anywhere in the editor.

You might like to read

Subscribe to our newsletter

Subscribe to our email newsletter to receive article notifications and regular product updates.