Need to send the data from your registration forms to Airtable? Store your users' data and create the database you need to get to know them better.
Create a fully customized registration form that connects to Clearbit to find information about the user's professional profile and to save it in Airtable.
This use case consists of a one-step form that will ask the user email and password, and a flow linked to it that gets the information from Clearbit and stores it in Airtable.
Go to Airtable and create a table with a column for each data you want to store about the new users. For example, we will store their name, email, company and job title, but you can adapt it to your needs.
Choose also the field type that you are going to store in each column. We will use the ‘Email’ option for the user email and the ‘Single line text’ for the name, company, job title and country.
To change the field type, simply click on the triangular icon of the field, then on ‘Customize field type’ and, in this case, choose the ‘Email’ option.
Note that the column name and its reference in Arengu must be written with the exact spelling.
Go to the form editor in Arengu and build a registration form. You can create it using the editable template or from scratch.
This form will have an Email field and a Password field, with the following settings:
Go to the Flows tab, in the light gray menu on the left, and create a before-submission flow and an after-submission flow, as you can see in the picture.
Create them by simply clicking on the plus button and giving them a name. Finally, publish the changes.
The before submission flow will have this structure:
First, an HTTP Request action to register the user in your API, with the following settings:
If necessary, include the authentication header of your API in the Headers section.
Then add an If/then condition action, to manage the responses that your API returns when trying to register the user, and configure it as follows:
In the False branch, include a Show error message action and personalize the message that will be displayed on the form in the event that the email or password is not valid.
In the True branch, include a Submit the form action, and configure it as follows:
Once you have configured all the actions, publish the changes.
The after submission flow will have this structure:
First, include a Find a person and company by email action and configure it as follows:
Then add a Create a record action with the following settings:
Finally, publish the changes.
Go back to the form editor and click on the Preview button to open it in a new tab and test it. You can check if everything has worked correctly in the Executions tab of each of the flows.
Here you can check the inputs, outputs and errors of each action in each execution to fix any possible bugs.
Do you want to try it by yourself?Sign up free or book a demo with our team. Still not sure about it? Take a look at the most common use cases.