Albato Integrations with Bit Flows – Automate SaaS Platform Actions

Albato Integrations: Albato helps you solve even the most complex automation problems, allowing you to build ecosystems across dozens of apps and platforms.

In this guide, you’ll learn how to integrate Bit Form with Albato, where Bit Form acts as the trigger and Albato is the action endpoint. Once the setup is complete, every time someone submits your form, the data will be automatically sent to Albato to trigger a connected automation or workflow.

This beginner-friendly, step-by-step tutorial will help you set up your first integration smoothly—making it easy to connect your WordPress forms with Albato for efficient data flow and automation.

Authorization of Albato Integrations

To set Albato as an action in Bit Flows, first open your Bit Flows Dashboard, then either create a new flow or open an existing one. In the Flow Builder, click the plus (+) icon to add an action. From the list of available apps, search for and select Albato.

After selecting your preferred action, the next step is to choose an event. For example, in this case, we’ve selected the “Make a Request” event.

After selecting the action event, a new popup will appear where you can connect with your API endpoint.

If you’ve already created a connection to the service you want to GET, POST, PUT, PATCH, or DELETE data from, simply select it from the “Select Connection” dropdown. If not, click on “Add Connection” to create a new one. This step is optional.

Request URL: Here, you need to enter your Albato Webhook URL.

To get this:

1. Log in to your Albato account.
2. Create a new automation or open an existing one.
3. Choose Webhook as the trigger event.
4. Albato will generate a Webhook URL for you.
5. Copy that URL and paste it into the Request URL field in Bit Flows.

Method: Select the HTTP method you want to use for the API request in Albato. This defines how the data will be sent to the external service and what action will be performed.

Available options:

• GET – Retrieve data from an external service
• POST – Send new data to create a resource
• PUT – Fully update an existing resource
• PATCH – Partially update an existing resource
• DELETE – Remove a resource

Choose the method based on the action required by the API you’re integrating with. Here , we’ll choose the POST method to send form data and trigger the workflow.

Content Type: After selecting the Method, a new field called “Content Type” will appear. This defines the format of the data being sent in the Albato.

Choose the content type based on the requirements of the platform you’re integrating with. Always refer to the API documentation to ensure you’re using the correct format.

For this integration, choose JSON as the content type to send structured data.

Available Content Types:

• JSON
• Form-Data
• Encoded Form
• Text
• HTML
• XML

Headers: Headers are optional key-value pairs you can add to your API request to send extra information to the server. To add a header, click the “+ Add” button and enter the key and value as needed.

Common headers include:

• Authorization (e.g., API keys or tokens)
• Content-Type (e.g., application/json)
• Accept (to specify the expected response format)

You can add multiple headers depending on the API’s requirements. Always check the API documentation for the correct header values.

Here, you’ll also find a “Map Fields” option, which lets you dynamically insert form data or variables into your header values. You can also use Flow, Math, String, and System functions to customize your headers further.

👉 Learn more about Field Mapping

Query Params: Query parameters are key-value pairs added to the end of the URL to send extra data to the server. They are most commonly used with GET requests but can be applied with other HTTP methods depending on the API.

In Bit Flows, you can add multiple query parameters by clicking the “+ Add” button. Each parameter will automatically be appended to your API request URL.

You can also use the “Map Fields” option to dynamically insert values from your form submissions. Additionally, you can use Flow, Math, String, and System functions to customize these parameters.

👉 Example:
https://api.example.com/users?status=active&role=admin

Body: The Body section is where you define the main content of your API request—especially important for methods like POST, PUT, or PATCH, where you send data to the server. You can add multiple key-value pairs to build your request payload.

You’ll also see a “Map Fields” option here, which allows you to dynamically insert data from your form fields or system values into the request body. You can further enhance this using Flow, Math, String, and System functions for more advanced control.

Make sure your body format matches the Content Type you selected (e.g., JSON, Form-Data, etc.).

Raw Body: The Raw Body option lets you manually enter your request payload as raw text or code—ideal for sending structured data like JSON, XML, plain text, or any custom format required by the API.

This is especially useful when:

• The API requires a specific or complex body structure
• You’re working with nested or detailed data
• You want full control over the exact content sent

You’ll also find a “Map Fields” option here, allowing you to dynamically insert data from your form fields or system values into the raw body. You can further enhance the payload using Flow, Math, String, and System functions for advanced customization.

First, enable the Raw Body option to manually enter the request payload in your desired format.

Now, map the data dynamically using field variables. Check the example below for guidance.

{
  "first_name": "Mr.  {variable}",
  "last_name": "{variable}",
  "email": "{variable}",
  "address": {
    "city": "{variable}",
    "country": "{variable}"
  }
}Copy

Once you’ve finished these settings, you can either click the “Test Run” button to check if the integration is working correctly or simply close the popup to complete the setup.

You also have the option to test the full flow. You can either click “Listen Response” and then run the trigger event (e.g., submit the form), or use existing data to test the integration and make sure everything works correctly.

After completing all the steps, click the “Logs” icon at the top-right corner of the Flow Builder to view your integration logs. Logs help you verify if the trigger and action worked correctly and make it easier to spot and fix any issues.

That’s it! You’ve successfully set up an automation in Bit Flows to connect Bit Form with Albato. Now, whenever someone submits your form, the data will be automatically sent to Albato to trigger your connected workflow.

This setup helps you automate data transfer, improve efficiency, and streamline your processes with ease. If you need further assistance or want to explore more powerful integrations, feel free to check out our comprehensive User Guide.

Check out our easy-to-follow tutorials!

• How to Integrate Albato with Bit Flows