Bit Integrations vs Bit Flows: Same Company, Different Automation Jobs

Disclosure: Bit Apps builds both Bit Integrations and Bit Flows, and we publish this comparison on the Bit Integrations website. We match each plugin to the automation it fits and do not rank them.

Bit Integrations and Bit Flows are two WordPress automation plugins from Bit Apps, and each one does a different job.

Bit Integrations connects a WordPress plugin trigger, such as a form submission, an e-commerce order, or LMS data, to an external destination platform. Each connection is one integration. Developers can extend it with custom triggers, action hooks, custom actions, custom API connections, and webhooks.

Bit Flows builds multi-step workflows on a visual canvas. One trigger can send data through conditions, routers, loops, delays, data parsers, AI Agent steps, and several actions in a row.

Bit Integrations vs Bit Flows at a glance

For the latest installation counts, ratings, and requirements, check the official WordPress.org listings linked in the table.

Atributo	Bit Integrations	Bit Flows
Developed by	Bit Apps	Bit Apps
Product type	WordPress one-to-one integration plugin	WordPress multi-step workflow automation plugin
WordPress.org listing	Bit Integrations on WordPress.org	Bit Flows on WordPress.org
Instalações ativas	20,000+	2,000+
Rating	4.9 out of 5	4.9 out of 5
First release	2022	January 2025 (beta)
Minimum requirements	WordPress 5.1, PHP 7.4	WordPress 5.8, PHP 8.0

Quick answer: which plugin fits which automation?

Ask one question about your workflow: does any step need the result of an earlier step? If every action can run on the trigger’s data alone, Bit Integrations fits.

If a step needs an earlier step’s output, or your workflow needs AI, a wait, a schedule, or a person’s approval, Bit Flows fits.

Your automation	Plugin that fits
One trigger sends data to one app.	Bit Integrations
One trigger sends data to several apps, and each app works on its own.	Bit Integrations (one integration per app) or Bit Flows (one workflow)
A step uses processed data, AI output, a delay, a loop, or an approval.	Bit Flows
The workflow runs on a schedule, with no event on your site.	Bit Flows

Both plugins have free versions on WordPress.org, so you can test your own workflow in each one before you buy.

What is Bit Integrations?

Bit Integrations is a WordPress one-to-one integration and automation plugin from Bit Apps. It sends data from a WordPress trigger event, such as a form submission or a WooCommerce order, to an action in another platform. 

You can connect WordPress to 335+ platforms, including CRMs, email marketing tools, spreadsheets, LMS plugins, and messaging apps. See the full integrations list of the Bit Integrations plugin.

How a Bit Integration Works

You build each integration in three steps:

1. Pick a trigger. Choose a WordPress plugin, then one of its trigger events. One plugin can offer many events. WooCommerce, for example, offers order creation, order status changes, product reviews, and more.
2. Pick an action. Choose the platform that receives the data, connect your account, and choose the task, such as creating a HubSpot deal.
3. Mapeie os campos. Match each trigger field to a field in the destination platform’s fields. You can add fixed values, custom values, smart tags, and lógica condicional no Bit Integrations that decide whether the integration runs.

Bit Integrations runs each integration at the moment the trigger fires, on the same request. One integration performs one action. To send a form submission to HubSpot and to Google Sheets at the same time, you create two integrations on the same trigger.

The timeline shows the success and failure history of every integration, and you can re-execute a failed run from there. Turn on failure email alerts before you create an integration if you want notices for it.

Developer tools in Bit Integrations

Bit Integrations gives developers five ways past the prebuilt integrations:

• Custom Trigger (Pro): Define your own trigger and send its data into an integration.
• Bit Integrations Action Hook trigger (Pro): Catches an event from any WordPress plugin that fires a hook, including plugins with no prebuilt trigger.
• Custom Action (free): run your own PHP function when a trigger fires, with the trigger’s fields available in your code.
• Custom API (free): send data to any API endpoint, with custom headers, query parameters, and a JSON body.
• Incoming and outgoing webhooks in Bit Integrations: outgoing webhooks (free) send data to any URL, and incoming webhooks (Pro) let external apps send data into WordPress.

Bit Integrations design scope

Bit Apps scoped Bit Integrations around direct connections from the start. The plugin has no visual canvas, no chained steps, and no AI model actions.

Its triggers come from WordPress plugins, and outside apps reach it through webhooks de entrada. That scope keeps each integration to one trigger, one action, and one field map.

What is Bit Flows?

Bit Flows is a self-hosted workflow automation plugin from Bit Apps. It runs multi-step workflows inside WordPress, and you build each workflow on a drag-and-drop canvas. 

One trigger can pass data through logic, data processing, AI, and as many actions as the job needs. Bit Flows connects WordPress plugins, SaaS apps, APIs, and AI services from one builder. See the Bit Flows integrations list.

How a Bit Flows workflow works

You place a trigger on the canvas and connect nodes after it. Each node can use data from the trigger and from any node before it. Bit Flows includes these workflow tools:

• Condition and Router: Send data down different paths based on rules.
• Iterator and Repeater: run steps once for each item in a list, such as each product in an order.
• Delay, Schedule, and Date Time: pause a workflow, run it on a timetable, and format or calculate dates.
• Parsers: read JSON, CSV, and XML from API responses or webhook payloads.
• Run Code: execute custom PHP inside a workflow step.
• Respond to Webhook: send a custom reply to the app that called the workflow.
• Custom App builder: Connect any API, webhook, or WordPress action hook that has no built-in integration.

Bit Flows triggers reach beyond WordPress. You can start a workflow from Shopify, Zendesk, Google Sheets, an email inbox (IMAP), a webhook, or a schedule. Ready-made flow templates give you a starting point.

AI in Bit Flows

Bit Flows includes an AI Agent that reads data, makes decisions, and picks the next step in a workflow. Free AI actions cover ChatGPT (OpenAI), Claude, Gemini, DeepSeek, Perplexity, OpenRouter, and Groq.

Bit Flows Pro adds two AI tools. The MCP Client lets the AI Agent use tools from external MCP servers, and Human in the Loop pauses a workflow until a person approves or declines. 

Bit Flows also works as an MCP server, so AI clients such as Claude, ChatGPT, and Cursor can build and run your flows. Read more on the Bit Flows AI Agent page.

How Bit Flows runs workflows

Bit Flows processes workflow tasks through a queue and supports cloud cron, so scheduled workflows don’t depend on WP-Cron alone.

When a step fails, the workflow stops by default. You can set it to skip that step instead when later steps don’t need its output. Bit Flows retries failed workflows, logs every step, and emails you when a task fails.

Why Bit Apps builds two automation plugins

Bit Flows does not replace Bit Integrations. Bit Apps announced both products on December 21, 2021, and planned them as separate plugins with separate pricing, development, and marketing.

Bit Integrations launched in 2022 as a single-step integration plugin. Bit Apps has said since launch that Bit Integrations triggers stay WordPress-based, and that routers, multi-step workflows, and delays belong to a different product. 

Bit Flows released its first beta in January 2025 to cover that multi-step work. You can read the Bit Flows team’s account of why Bit Apps built two automation plugins.

Both plugins ship regular releases with new triggers and actions. Bit Integrations and Bit Flows each have a free version, a Pro version, and a separate license.

Where Bit Integrations and Bit Flows overlap

Both plugins run on your own WordPress server and charge no per-task fees. Both free versions include triggers from WPForms, Contact Form 7, Elementor Forms, WooCommerce, Bit Form, Bit Assist, and Bit CRM. 

Bit Integrations also includes free triggers from Bit Social and sends data to 160 destination platforms on its free version. Bit Flows also includes free triggers from Webhook, WordPress, WordPress Action Hooks, Trello, and ElevenLabs.

Both handle webhooks, custom APIs, WordPress hooks, conditional logic, and custom PHP, and each plugin uses these features in its own way.

Shared feature	In Bit Integrations	In Bit Flows
Webhooks	Incoming (Pro) starts an integration; outgoing (free) sends data out	Incoming (free) starts a workflow; can send a custom reply
API personalizada	A Custom API action sends data to an endpoint	API and HTTP request steps, plus a Custom App builder with cURL import
WordPress hooks	The Action Hook trigger catches hooks from any plugin	A Custom App listens to a WordPress action hook
Lógica condicional	A condition decides whether an integration runs	Conditions and routers split a workflow into paths
Custom PHP	Custom Action runs your PHP as the integration’s action	Run Code executes PHP at any step in a workflow
Logs and recovery	Timeline history, re-execution, failure email alerts	Step logs, retries, re-execution, failure email alerts

That overlap lets you run some jobs in either plugin. Each plugin still builds a different kind of automation: Bit Integrations builds single connections, and Bit Flows builds chains of steps.

Key differences between Bit Integrations and Bit Flows

Bit Integrations builds one connection per integration, while Bit Flows builds workflows where each step can use the result of the step before it.

Dimension	Bit Integrations	Bit Flows
Automation unit	Integration: one trigger to one action	Workflow: one trigger to any number of connected steps
Builder	Three-step setup: trigger, action, field map	Drag-and-drop visual canvas
Trigger sources	WordPress plugin events, plus incoming webhooks (Pro)	WordPress events, SaaS apps, webhooks, email, and schedules
One event to several apps	Yes, one integration per app	Yes, inside one workflow
A step uses an earlier step’s output	Não	Sim
Flow control	Not included	Router, iterator, repeater, delay, schedule
Data processing	Field mapping, smart tags, conditional login, field concatenation	JSON, CSV, and XML parsers, date and time tools, array and math functions
AI	Not included	AI Agent, AI model actions, MCP Client (Pro), Human in the Loop (Pro)
Execution	Runs on the request that fires the trigger	Queue-based processing with cloud cron

Chained steps

Bit Integrations and Bit Flows differ most in how steps connect. Every Bit Integrations integration reads from the trigger and writes to one destination, so one action can’t use another action’s result. 

In Bit Flows, each node can read what earlier nodes produced. A Bit Flows workflow can create a record in one app, take the new record’s ID, and send that ID to the next app.

Trigger sources

Bit Integrations starts from WordPress: forms, WooCommerce, LMS plugins, membership plugins, and other plugin events. Outside apps can send data in through an incoming webhook (Pro). 

Bit Flows adds native triggers from SaaS apps such as Shopify and Zendesk, plus email and schedule triggers, so a workflow can start without any event on your site.

Instant execution and queued processing

Bit Integrations runs an integration on the same request that fires the trigger. When a visitor submits a form, the data reaches your CRM as part of that submission.

Bit Flows places workflow tasks in a queue and runs them in the background, away from the visitor’s page request. A single form-to-CRM sync suits instant execution, and a workflow with five API calls and an AI step suits the queue.

Hosting requirements

Bit Flows needs PHP 8.0 or higher, and Bit Integrations runs on PHP 7.4 and up. Check your host’s PHP version before you plan a Bit Flows workflow on an older site.

Who each plugin is built for

Pick by the job you need done. Workflow shape matters more than skill level.

Who uses Bit Integrations

• Site owners, bloggers, and small businesses who want form entries, orders, or sign-ups to land in a CRM, spreadsheet, or email list.
• Freelancers who set up the same few connections on client sites.
• WooCommerce and LMS site owners who sync customers, orders, and enrollments.
• Developers who need a direct connection plus a hook, a PHP function, or a custom API call.
• Anyone who wants affordable WordPress integrations without learning a workflow builder.

Who uses Bit Flows

• Businesses that run multi-step processes, such as order handling, lead routing, or support triage.
• Teams that want AI to read, classify, or write inside a workflow.
• Developers who work with APIs, webhook payloads, and structured data.
• Users who connect several apps in one process, including apps outside WordPress.

Bit Flows users include non-technical people too. One WordPress.org reviewer, a county fair organizer, uses Bit Flows Pro to send exhibitor invoices after finding Zapier hard to use.

Agencies

Agencies can run both plugins across client sites: Bit Integrations for direct syncs, Bit Flows for client processes with branching or AI. 

Bit Integrations and Bit Flows both sell single-site and unlimited-site plans with lifetime deals. Bit Flows also imports and exports flows, so you can reuse one workflow on several client sites.

What the adoption numbers tell you

Bit Integrations has about ten times as many active installations as Bit Flows. It has been on the market since 2022, about three years longer, and it serves the larger group of users who need direct connections.

Both plugins hold a 4.9 rating on WordPress.org. Read the install counts as a sign of audience size, and judge fit by your own workflow.

Workflow complexity compared

Bit Integrations covers the first three levels of workflow complexity, and Bit Flows covers all five. You need Bit Flows from level 4 up.

Level	Workflow shape	Exemplo	In Bit Integrations	In Bit Flows
1	One trigger to one app	A WPForms submission creates a HubSpot contact	One integration	One trigger node and one action node
2	One event to several apps, each independent	A Contact Form 7 entry goes to Google Sheets, Mailchimp, and Slack	Separate integration per app	One workflow
3	Route by trigger data	WooCommerce orders over $500 create a HubSpot deal; smaller orders go to Google Sheets	Conditional logic on each integration	A router in one workflow
4	A step uses an earlier step’s output	A webhook sends an order, and the workflow parses it and adds a row for each line item	Not supported	Parser and iterator
5	AI, waiting, or human approval	A support form goes to an AI Agent for triage, waits for approval, then sends a reply	Not supported	AI Agent and Human in the Loop

Level 1 in each plugin: WPForms to HubSpot

In Bit Integrations, you choose WPForms como gatilho, pick your form, choose HubSpot’s Create Contact action, and map the name and email fields. The integration runs each time someone submits the form. The WPForms automation walkthrough shows each screen.

In Bit Flows, you place a WPForms trigger node on the canvas, connect a HubSpot node, and map the same fields. You get the same contact in HubSpot, plus a canvas you can extend later. If the job stays at level 1, you won’t use the extra tools.

Level 5 in Bit Flows: a WooCommerce order workflow

Say your store wants to treat high-value orders differently. In Bit Flows, the workflow runs like this:

1. A new WooCommerce order starts the workflow.
2. A condition checks the order total.
3. The AI Agent classifies the customer from the order details.
4. A router sends the order down a path based on the AI result.
5. Actions email the customer, notify your team in Slack, and update Google Sheets.

Each step depends on the one before it. The router needs the AI result, and the AI step needs the order data. 

Bit Integrations can’t build this workflow, since its actions can’t read each other’s output. It can still run the parts that need no chain, such as copying every order into Google Sheets.

Which plugin fits this workflow?

Match your automation to a row below. Rows marked “Either” work in both plugins.

Workflow	Plugin that fits	Por quê
WooCommerce order to Google Sheets row	Bit Integrations	Free trigger, free action, one destination
Gravity Forms submission to Brevo subscriber	Bit Integrations	A direct connection; Gravity Forms is a Pro trigger
Elementor form to Mailchimp, only when the consent box is ticked	Bit Integrations	Conditional logic on the integration
Form submission to your own PHP function, such as a license key generator	Bit Integrations	Custom Action runs your function on the free version
A theme’s custom do_action hook to a CRM	Either	Bit Integrations Action Hook (Pro) or a Bit Flows Custom App
New WooCommerce product, AI-written description, product update	Bit Flows	The update needs the AI output
Shopify order to a CRM	Bit Flows	Native Shopify trigger; Bit Integrations can receive it only through an incoming webhook (Pro)
LearnDash course completed, email now, follow-up three days later	Bit Flows	Needs a delay
Nightly summary of the day’s form entries	Bit Flows	Needs a schedule instead of a site event
New lead, manager approval, then a CRM deal	Bit Flows (Pro)	Needs Human in the Loop

Use Bit Integrations when

• Your automation sends a WordPress trigger to one action, or to several apps that don’t depend on each other.
• You want to set up each connection in three steps, without a canvas.
• Your data should reach the destination on the same request that fires the trigger.
• You need a hook, a PHP function, or a custom API call on a direct connection.
• Your site runs PHP 7.4, or you want the lower-cost plugin for direct syncs.

Use Bit Flows when

• A step needs data that an earlier step produced.
• Your workflow needs AI, a delay, a schedule, a loop, or a human approval.
• The trigger lives outside WordPress, such as Shopify, Zendesk, or an email inbox.
• You need to parse JSON, CSV, or XML from an API or webhook.
• You want a whole business process in one workflow you can see and edit.

Use both when

• Your site needs quick direct syncs and at least one multi-step process.
• You already run Bit Integrations and a new workflow needs chained steps or AI. Build that workflow in Bit Flows and keep your existing integrations.

Bit Integrations vs Bit Flows for developers

Choose by where your custom logic lives. If it fits in one PHP function or one API call at the end of a single integration, Bit Integrations handles it with Custom Action or Custom API. 

If your logic needs steps between calls, such as reading an API response before the next request, Bit Flows handles it.

Custom Action, Custom API, and outgoing webhooks work on the free version of Bit Integrations. Three developer features need Bit Integrations Pro: Custom Trigger, the Action Hook trigger, and incoming webhooks.

Bit Flows includes custom apps on its free version and adds developer tools that Bit Integrations doesn’t offer:

• JSON, CSV, and XML parsers and array functions to read and reshape API responses.
• Run Code to execute PHP at any step of a workflow.
• A Custom App builder with cURL import, plus import and export to move custom apps between sites.
• Respond to webhooks, so a workflow can answer the app that called it with custom data.
• An MCP server, so AI tools such as Claude, ChatGPT, and Cursor can build and run flows.

Bit Integrations vs Bit Flows for beginners

Both plugins work without code. They differ in how many ideas you learn before your first automation runs.

In Bit Integrations, you learn four ideas: trigger, action, field mapping, and an optional condition. The setup screens take you through them in order. One integration does one job, so you can check it at a glance.

In Bit Flows, you learn the canvas, nodes, the links between nodes, and how a node reads data from earlier nodes. Bit Flows describes itself as beginner-friendly, and its templates and test runs help you start. 

Those extra ideas pay off once a workflow needs more than one step. For a single form-to-CRM connection, you would learn them and not use them.

To start for free, see the free triggers and actions in Bit Integrations, or try both plugins on a live demo site.

AI automation: Bit Integrations vs Bit Flows

Bit Flows is for AI automation from the Bit Apps. Bit Integrations has no AI model actions, and the AI Agent, MCP Client, and Human in the Loop belong to Bit Flows alone.

Use this rule: if a model needs to read, classify, write, or decide inside your automation, build that automation in Bit Flows. Common AI workflows in Bit Flows include:

• Lead qualification: an AI Agent reads a form message, judges the lead, and routes it to the right CRM or sheet.
• Support drafts: a model drafts a reply to a support request, and a team member approves it before it goes out.
• Product content: a new WooCommerce product triggers a model that writes the description and updates the product.

Bit Integrations vs Bit Flows pricing

Bit Integrations costs less at every matching tier, and Bit Flows includes more in its free version. The table shows the current discounted prices on each official pricing page, with list prices in brackets. Each plugin includes all its features on every paid plan.

Plano	Bit Integrations	Bit Flows
1 site, yearly	$35/year ($39)	$59/year ($99)
1 site, lifetime	$99 ($132)	$159 ($299)
5 sites, yearly	Not offered	$99/year ($139)
5 sites, lifetime	Not offered	$299 ($599)
Unlimited sites, yearly	$99/year ($132)	$129/year ($249)
Unlimited sites, lifetime	$299 ($665)	$499 ($999)

Fontes: Preços Bit Integrations, Bit Flows pricing.

Free versions compared

• Bit Integrations free: free triggers from WPForms, Contact Form 7, Elementor Forms, WooCommerce, Bit Form, Bit Assist, Bit Social, and Bit CRM; most action platforms; Custom Action, Custom API, and outgoing webhooks; unlimited integrations with those triggers and actions.
• Bit Flows free: unlimited multi-step workflows and tasks; every workflow tool, including the AI Agent; free triggers such as WPForms, Contact Form 7, Elementor Forms, WooCommerce, webhooks, and WordPress; free actions such as Google Sheets, ChatGPT, Claude, Gemini, and WhatsApp.

Value by workflow type

• Direct syncs: Bit Integrations does the job at a lower price. A Bit Flows license would buy tools you won’t use.
• Chained steps or AI: Bit Flows can do the job, and its free version lets you build and test before you pay.
• Five client sites: Bit Flows has a matching plan. Bit Integrations moves from one site to unlimited sites.
• Both plugins: the Bit Apps Agency Lifetime Bundle includes Bit Integrations, Bit Flows, and other Bit Apps products for $1,449 ($3,726).

Using Bit Integrations and Bit Flows together

Você pode run Bit Integrations and Bit Flows on the same WordPress site, and Bit Apps fully supports that setup. One practical split: Bit Integrations handles direct syncs such as form-to-CRM and order-to-sheet, and Bit Flows handles processes with branches, waits, or AI.

Give each job one home. If both plugins listen to the same WPForms form and both send it to HubSpot, you get two contacts for every submission. When you rebuild an old integration as a Bit Flows workflow, turn off the old integration first.

Each plugin needs its own license. Adding Bit Flows leaves your Bit Integrations license and integrations as they are.

Conclusão

Bit Integrations and Bit Flows handle different automation jobs on the same WordPress site. Choose Bit Integrations when each action can run on the trigger’s data alone.

Choose Bit Flows when steps need each other’s results, or when AI, timing, or approval enters the process.

Install Bit Integrations ou Bit Flows free from WordPress.org and test your own workflow in each. For tools outside Bit Apps, read Bit Integrations x Zapier e Bit Integrations vs Uncanny Automator.

Perguntas frequentes