Skip to main content
Bit Integrations logo

Bit Integrations

Connects WordPress plugins and external platforms through direct trigger-action automations, field mapping, conditions, webhooks, Custom API, reusable connections, and execution logs.
AutomationRecommendedFreemium
Visit Plugin
Last Updated: October 15, 2026

Plugin Health & Stats

Checked 1 day agoSource: WordPress.org
Active installs
20,000+Official WordPress.org tier
WP.org rating
4.9/5160 ratings
Version
2.11.1Current repository release
Last updated
1 day agoNov 16, 2026
Total downloads938,476
Tested with WP7.1.4
Requires WP5.1+
Requires PHP7.4+
Support resolved (2 mo.)0 of 1 (0%)
Plugin age4 years, 10 months
Updates observed7
Tracking sinceSep 12, 2026

Historical overview

364-day WordPress.org history
Download trendDaily package downloads · last 90 days
7d8,633 30d28,698 90d92,232 Peak day5.7KOct 6
Aug 19Sep 17Oct 17Nov 16
Active version adoptionCurrent usage share
2.10 39.6%2.11 25.5%other 19.2%2.8 8.1%2.7 7.6%

Quick take

Bit Integrations is a WordPress-native automation connector built for direct data transfer between plugins and external apps. Its strongest use case is straightforward automation such as sending a form submission to Google Sheets, syncing WooCommerce data to a CRM, creating a subscriber in an email platform, or passing WordPress events to another service through a webhook or API.

I would choose it when the automation can be expressed cleanly as a trigger, an action, field mapping, and optional conditions. If one trigger needs a long chain of branches, loops, delays, AI decisions, or approval steps, Bit Flows is the more natural product from the same company.

Best for: WordPress sites that need frequent direct integrations between forms, eCommerce, LMS, CRM, email, spreadsheets, webhooks, and external APIs.

Current release reviewed: 2.10.8, released October 12, 2026.

Active installs: 20,000+ on WordPress.org.

Free version: Yes. Free includes working triggers and actions, while Pro unlocks the complete premium event and integration catalog.

Paid pricing: Current promotion starts at $35/year for one site or $99 lifetime for one site.

Bit Integrations features at a glance

AreaWhat Bit Integrations can doAvailability
Trigger-to-action automationStart from a WordPress plugin event and send data to another WordPress plugin or external platformFree and Pro, depending on the exact event
Field mappingMatch incoming trigger fields to destination fields, custom fields, and supported dynamic valuesCore feature
Conditional logicRun an integration only when field values meet AND/OR rules and comparison operatorsCore feature
Smart TagsInsert date/time, logged-in user, post, author, site, visitor, and boolean values into supported mappingsCurrent versions
WebhooksReceive external webhook data or send data to an outgoing webhook with parameters, headers, body values, and dynamic pathsAvailable in supported workflows
Custom APIConnect services through GET, POST, PUT, PATCH, and DELETE requests with API key, bearer-token, or basic authenticationAdvanced integration capability
ConnectionsAuthorize an app once and reuse the same saved credentials across multiple integrationsCurrent connection manager
Timeline logsInspect successful and failed runs, search/filter logs, and re-execute previous integration attemptsCurrent versions
Failure alertsEmail the site administrator when an integration failsAvailable in settings
Unlimited transfersPaid plans do not use a per-task or per-record billing modelPaid plans

The setup model is deliberately simpler than a workflow canvas

A Bit Integrations automation starts by choosing what event should trigger the integration. That could be a form submission, WooCommerce event, LMS activity, CRM change, webhook request, or another supported WordPress event. You then choose the destination app and action that should receive the data.

This design is easier to manage when the business rule is direct. For example, when a WC Affiliate event occurs, send selected fields to Google Sheets. You do not need to draw a flowchart to express that relationship. The trade-off is that this is not intended to replace a workflow orchestrator when the automation has many dependent steps.

Field mapping is the part that determines whether the automation is actually reliable

The trigger and action names are only the beginning. The real setup work is deciding which source field should populate each destination field. Bit Integrations exposes trigger data on one side and the selected action’s fields on the other so you can map the values explicitly.

This matters most when destination fields are required, when the receiving app expects a specific data type, or when custom fields are involved. Recent versions have also improved nested trigger labels and added Smart Tags for values such as current date/time, logged-in user data, post information, site details, visitor information, and true/false values.

I would always test the mapping with a real submission before depending on it. A successful authorization does not prove that the correct email, product ID, user ID, amount, or custom field is reaching the destination.

Conditional logic keeps direct integrations from firing on every event

Conditional logic lets you decide whether an integration should run based on the incoming data. Supported operators include equality, null checks, contains, starts with, ends with, and numeric comparisons, while AND and OR logic can combine several rules.

For example, a CRM action could run only when a lead selects a particular service, or a spreadsheet action could run only when an order exceeds a value threshold. This is still a direct trigger-to-action model, but it prevents the destination from receiving data that does not belong there.

Custom API and webhooks extend the plugin beyond native connectors

A large integration catalog is useful, but every business eventually has a service that is not in the list. Bit Integrations can send data through outgoing webhooks or build a Custom API request when the external service exposes an endpoint.

Custom API supports common HTTP methods and authentication approaches including API key, bearer token, and basic authentication. You can configure an endpoint, headers, query values, request body, raw JSON, and mapped fields. Current releases also support dynamic URL path variables, making it easier to target endpoints where an ID or resource name is part of the path.

Webhook and API flexibility also raises the security bar. The official documentation warns that webhook access should be restricted and monitored. API credentials should use the least privilege required, and any externally supplied payload should be treated as untrusted data.

The new connection manager reduces repeated authorization work

Version 2.10.0 introduced a centralized connection manager. Instead of authorizing the same service separately every time, you can save a connection once and reuse it across integrations. The manager shows linked integrations and allows connection editing from one place.

Version 2.10.2 also changed credential presentation so API keys, tokens, and secrets are hidden behind dots with an explicit reveal control. OAuth callbacks now return through a dedicated site callback URL, which improves compatibility with providers that reject less specific redirect URLs.

Timeline logs are important once integrations become business infrastructure

Bit Integrations records execution history so you can see whether a transfer succeeded or failed. The current Timeline supports server-side status filtering, search, configurable columns, re-execution, and nested re-run history.

A security change in 2.10.7 also matters here: when an administrator re-executes a log, the integration now runs as the user who made the original submission rather than inheriting the administrator’s identity. That reduces the chance that a retry gains permissions the original event did not have.

Settings can automatically remove old logs after a defined retention period and can email the administrator when an integration fails. I would enable failure alerts for any integration tied to lead capture, orders, billing, memberships, or other business-critical data.

Bit Integrations Free vs Pro

The free plugin is a real integration product, not just a UI demo. It includes supported free triggers and actions, mapping, conditions, and direct automation workflows. Pro unlocks the complete paid trigger/action catalog and advanced integrations that are marked Pro throughout the official changelog and documentation.

The practical way to decide is to write down the exact trigger and exact action first. Two apps can both appear in the catalog while the event you need is only available in Pro. Check the event-level availability before designing the rest of the automation.

CapabilityFreePro
Direct trigger-to-action integrationsYes, supported free eventsYes
Field mappingYesYes
Conditional logicYesYes
Timeline/loggingYesYes
Premium plugin triggers/actionsLimitedYes
All paid integration eventsNoYes
Unlimited data transfersSubject to free event coverageYes, no task-credit billing
Support and updatesCommunity/free channelIncluded with paid license

Bit Integrations pricing

Pricing checked October 15, 2026. Starter Annual is currently promoted at $35/year for one site, with $39 displayed as the regular price. Starter Lifetime is $99 one time during the current promotion, with $132 shown as the regular price.

Agency Annual is currently $99/year for unlimited sites, with $132 displayed as the regular price. Agency Lifetime is currently promoted at $299 one time for unlimited sites, with $665 shown as the regular price. Paid plans include all features and unlimited data transfers; the main difference is site allowance and annual versus lifetime licensing.

Bit Integrations vs Bit Flows, Uncanny Automator, and AutomatorWP

Bit Flows is the obvious alternative when you need a visual multi-step process with routers, loops, delays, AI Agent, MCP, or Human in the Loop. Bit Integrations is simpler when the job is mainly moving data from one event to one destination.

Uncanny Automator and AutomatorWP are broader WordPress automation platforms with recipe-style workflows and large ecosystems. Bit Integrations differentiates itself through its direct integration model, extensive connector catalog, API/webhook tooling, and paid plans that advertise unlimited data transfer rather than task credits.

Production checklist before relying on an integration

  • Confirm the exact event: verify the trigger and action you need are available in your Free or Pro plan.
  • Test with real data: send an actual form, order, membership, or CRM event and inspect the destination result.
  • Verify required mappings: check email, IDs, amount fields, custom fields, and data types before enabling the integration.
  • Use conditions deliberately: make sure an AND/OR rule does not silently block legitimate records.
  • Protect credentials: use least-privilege API keys and revoke connections that are no longer needed.
  • Review the Timeline: inspect the first live executions and enable failed-integration email alerts.
  • Plan log retention: choose a retention period that balances troubleshooting needs with database growth.

PluginSuggest verdict

Bit Integrations is strongest when WordPress automation is fundamentally about dependable data transfer. The trigger-action model stays easier to understand than a large workflow graph, while field mapping, conditions, Smart Tags, webhooks, Custom API, reusable connections, logs, and retries provide enough depth for serious integrations.

I would shortlist it for WordPress businesses that connect forms, WooCommerce, LMS plugins, CRMs, spreadsheets, email tools, and external APIs at meaningful volume. I would choose Bit Flows or another workflow-first tool when the process itself, rather than the data transfer, requires many sequential decisions and branches.

Bit Integrations FAQs

Is Bit Integrations free?

Yes. Bit Integrations has a free WordPress.org version with working triggers and actions. Pro expands the available premium events and integration coverage.

What is the current Bit Integrations version?

The current WordPress.org release is Bit Integrations 2.10.8, released October 12, 2026.

Does Bit Integrations charge per task or data transfer?

Paid plans currently advertise unlimited data transfers and do not use a per-task credit model.

Can Bit Integrations connect an app that has no native integration?

Yes. Outgoing webhooks and Custom API requests can connect compatible external services that provide webhook endpoints or APIs.

Can I rerun a failed integration?

Yes. Current Timeline functionality supports re-execution and keeps nested rerun history so you can review previous attempts.

How is Bit Integrations different from Bit Flows?

Bit Integrations is optimized for direct trigger-to-action data transfer. Bit Flows is a visual multi-step workflow builder with branching, loops, delays, AI Agent, MCP, and human approval tools.

How much does Bit Integrations Pro cost?

As checked October 15, 2026, the current promotion starts at $35/year or $99 lifetime for one site. Unlimited-site pricing is $99/year or $299 lifetime during the current promotion.

Similar Plugins

Best ValueFreemium

Build WordPress-native automations with triggers, actions, filters, dynamic tags, logs, AI-assisted workflow creation, and optional specialist add-ons.

Editors ChoiceFreemium

Build multi-step WordPress automations with a visual workflow canvas, AI Agent, routers, APIs, webhooks, MCP, human approvals, logs, and hundreds…

Community Reviews

0 community reviews
Log in or create an account to write a review.
No published community reviews yet.