HTTP Request

By properly configuring an action HTTP request, you can extend the functionality of your app by seamlessly integrating with external services.

What is it?

An action HTTP request allows users to send HTTP requests directly from the app, and then retrieve data, update resources, and perform various actions on remote servers.

This capability is essential for integrating your app with other systems, enabling real-time communication and data exchange.

How it works

When you enable the action to the Record View, there is a menu of action buttons added to the bottom bar of the record view.

When you configure an action HTTP request in your app, you are essentially setting up a mechanism to send a request to a specific URL with a chosen HTTP method (such as GET, POST, PUT, or DELETE).

When users tap on the action button, the server that receives the request processes it and returns a response, which the app can then use to update its data or trigger further actions.

Add the action

• From the Design tab, in the Tables section of the left sidebar, click on the Record view of any table.

• Go to the Action section on the right sidebar, and click the + button.

• Enter the name and icon for the action button, then click Configure...

• Click + Then... and choose HTTP request.

Configure the action

Once the action is added, you'll need to configure the specific details of the HTTP request:

• In the URL field, enter the endpoint of the API or web service you want to interact with. This is the web address where the request will be sent.

• Choose the appropriate method for your request. There are 4 options:

  • GET: Retrieve data from the server.

  • POST: Send data to the server to create a new resource.

  • PUT: Update an existing resource on the server.

  • DELETE: Remove a resource from the server.

• Click the + button below the method field to configure the header and body. For these type of fields, you may need to read the API docs of the API or web service of the third parties.

  • Headers: are key-value pairs that provide additional information to the server, such as authentication tokens or content type. Add any necessary headers by entering the key (e.g., Authorization, Content-Type) and the corresponding value.

  • Body: For methods like POST and PUT, you’ll need to define the body of the request, which contains the data you want to send to the server.

Require confirmation

Requiring a confirmation on the execution of the action can give users the chance to reconsider and avoid accidental taps.

You can also customize the confirmation message or use the default one.

Completion

In the settings of completion, you will configure

• The message on succession to your users can be a way to communicate as well as engage with your users, elevating the user experience with your app.

• Checkbox to enable the Confetti interaction like a celebration for the succession, making the experience more fun and rewarding.