API Request with Bit Flows – Automate Any Service Integration

API Request Integration: API Request is an action in Bit Flows that allows you to send GET, POST, PUT, PATCH, or DELETE requests to any API endpoint. Use it to connect and interact with external services, automate data exchange, and build custom workflows directly from your WordPress site.

In this guide, you’ll learn how to integrate Bit Form with the API Request action in Bit Flows. Here, Bit Form acts as the trigger, and the API Request lets you send data to any external service using GET, POST, PUT, PATCH, or DELETE methods.

In this example, we’ll use the POST method to send form data to MailerLite and create a new subscriber.

This beginner-friendly, step-by-step tutorial will help you set up your first custom API automation quickly and easily—perfect for connecting your WordPress forms to third-party platforms or custom endpoints.

Authorization of API Request Integration

To set API Request 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 API Request.

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: Enter the API endpoint URL where the request should be sent. This is the destination that will receive your GET, POST, PUT, PATCH, or DELETE request. Make sure the URL is correct and supported by the external service you’re integrating with.

Here, you’ll also see a “Map Fields” option, allowing you to dynamically build the API endpoint using form data or variables. Additionally, you can enhance your request logic using Flow, Math, String, and System functions.

👉 Learn more about Field Mapping

Method: Select the HTTP method you want to use for the API request. The available options are:

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

Choose the method based on what action you want the API to perform.

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

Choose the content type based on the requirements of the platform you’re integrating with. You should refer to their API documentation for the correct format. Since we’re using MailerLite in this example, we’ll select JSON as the content type.

Available Content Types:

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

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

Common use cases for headers include:

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

You can add multiple headers based on what the API requires. Be sure to refer to the target API’s documentation for the correct header values.

Here, you’ll also see a “Map Fields” option, which allows you to dynamically insert form data or variables into your header values. Additionally, you can enhance your header logic using Flow, Math, String, and System functions.

👉 Learn more about Field Mapping

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

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

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

👉 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—this is especially important for methods like POST, PUT, or PATCH, where you’re sending data to the server. You can add multiple key-value pairs to structure your request payload.

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

For this example, since MailerLite requires the email field, make sure to map the email from your form to the corresponding email field in the request body to ensure successful subscriber creation.

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

Raw Body: The Raw Body option allows you to write your request payload manually in raw text or code format—perfect for sending structured data like JSON, XML, plain text, or any custom format required by the API.

This is useful when:

• The API requires a specific body structure
• You’re working with nested or complex data
• You prefer full control over the request content

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

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 your trigger with an API Request. Now, whenever the trigger event occurs, data will be sent to your specified API endpoint using the method and configuration you’ve set—allowing seamless communication with any external service.

If you need more help or want to explore more integrations, feel free to check out our User Guide.

Check out our easy-to-follow tutorials!

• How to Integrate API Request with Bit Flows