Transferring data between WordPress and the external platforms you use is important, but often can take too much time. Whenever there’s any action on site that results in data, that information has to be copied to the other location. Bit Integrations handles these connections through automation.

The plugin lets you build automated workflows that transfer data between WordPress and hundreds of platforms without writing code or performing manual updates. Over the next few minutes, I’m going to go over a lot of the functionality inside the plugin.

Overview: What Bit Integrations Does

Simply put, Bit Integrations creates automated connections between WordPress plugins and external services. When a trigger event occurs on your site (think of someone submitting a form, making a purchase, or enrolling in a course), the plugin sends that data to your chosen platforms through predefined actions.

There are hundreds of platforms to connect with, including support for popular WordPress plugins such as Contact Form 7, WPForms, Elementor Forms, WooCommerce, LearnDash, and LifterLMS. External integrations include CRMs (Zoho, HubSpot, Salesforce), email marketing tools (Mailchimp, ConvertKit, ActiveCampaign), spreadsheets (Google Sheets, Airtable), and communication platforms (Slack, Discord, Telegram).

Each integration uses field mapping to determine which data transfers from WordPress to your external platforms. The plugin supports conditional logic too, which means you can create workflows that only execute when certain actions happen.

Bit Integrations Pricing

The plugin offers both free and premium versions. The free version provides core functionality with limited integrations, while the Pro version unlocks the complete feature set:

• Starter. An Annual plan costs $39 per year for a single-site license, while a Lifetime option requires a one-time payment of $132.
• Agency. If you manage multiple client sites, the Annual tier lets you have all the site licenses you need at $132 per year. The Lifetime plan is $665.

As with all of the Bit Apps tools, the entire functionality is available regardless of the plan you opt for. However, while you can create as many active integrations with the Pro version as you need, the free version limits the number of simultaneous workflows.

Why use Bit Integrations for WordPress automation

WordPress sites often need to communicate with external platforms, and doing this without any automation can create bottlenecks in your workflow.

Bit Integrations can save you time by eliminating repetitive data entry tasks. When someone fills out a contact form, their information flows to your CRM, email marketing platform, and project management tool without you touching it. This automation happens in real-time, which means your external platforms receive updates immediately after the trigger event occurs.

For instance, there are a number of scenarios you’ll look to Bit Integrations for:

• Moving form submissions to CRM systems need user information to enter your sales pipeline. You can configure the trigger, select your CRM as the action, and map the form fields. Then, you can add conditional logic to filter out spam submissions or route high-value leads to specific sales team members.
• Copying WooCommerce orders to email marketing platforms help you build customer segments and trigger automated email sequences. Here, WooCommerce order completion is the trigger, while your email marketing tool is the action. This time, you’ll map customer details along with purchase information.
• Sending course enrollments to communication platforms could see students enroll in LearnDash or LifterLMS courses, which sends notifications to Slack channels or Discord servers. This real-time notification helps instructors prepare for new students and track course popularity.

There’s also a cost efficiency benefit that comes from using a WordPress-native solution rather than external automation platforms. Services such as Zapier charge monthly subscription fees that scale with your usage. Bit Integrations requires a one-time payment or annual renewal at a fraction of the cost while providing similar functionality within WordPress.

How to Use Bit Integrations in 4 Steps

I’m going to show you what Bit Integrations can do by going through a typical workflow. This means the steps will be agnostic to any specific use case, but relevant to all of them.

You’ll need to install and activate both the free and premium versions of Bit Integration. The excellent documentation covers this process in detail, but it’s straightforward if you have previous experience.

1. Creating Your First Integration and Selecting a Trigger

The Bit Integrations Pro dashboard will show all your existing integrations as well as letting you create new ones. On your first visit it will be empty. Click the Create Integration button to start building your first workflow.

The trigger determines what event starts your automated workflow. Bit Integrations supports triggers from hundreds of different sources, services, WordPress plugins, forms, and much more. You simply select it from the grid, as I’ve done with WooCommerce. This brings you to a second screen where you choose (in this case) the task name. The exact selection here will depend on the specific integration you want to make. I’m choosing the automation to trigger when a user submits a review for a product within a WooCommerce store:

From here you can look at selecting the action you want to take after the trigger.

2. Choosing an Action and Mapping Fields

After configuring your trigger you’ll need to select where you want to send the data. As with the Trigger, you’ll choose the desired Action from the grid. I’m opting for a Trello action.

Depending on your choice of Action, you’ll need to fill in some authentication details and integration settings. These can run over a few pages. One page will relate to field mapping, which connects the data from your WordPress trigger to the corresponding fields in your external platform. It determines which information transfers and where it appears in your destination system.

The Form Fields columns display the available fields from your WordPress trigger (such as form fields, order data, or user information). The second column will show the fields available in your destination platform.

In my case, this is information from Trello that I need to select from the drop-down menus. For example, you can map your contact form’s Name field to the Name column value and the Email field to the Email value.

Bit Integrations also supports custom values and static text. If you want to add the same information to every row (such as a source label or timestamp), click the Custom Value option and enter your text. This appears in the field for all submissions.

3. Using Conditional Logic

At the bottom of the settings screen you can find the Conditional Logic checkbox. This lets you control when integrations execute based on specific criteria. This feature helps you create targeted workflows that only run when certain conditions are met.

The interface lets you define rules using comparison operators. You select a WordPress field from the first drop-down menu, choose a comparison operator, and enter or select the value to compare against.

For example, you could create a condition that only sends data to your CRM when the Budget field contains values above a certain amount. Alternatively, you can filter submissions based on which option a user selected from a menu.

Bit Integrations supports multiple conditions within a single integration. You can require all conditions to be met (AND logic) or execute the integration when any condition is satisfied (OR logic). This flexibility lets you create complex filtering rules that match your specific requirements.

4. Saving Your Integration

Finally, once you save your changes, your integration will be live! You can view every integration on the All Integrations screen.

If you read my Bit Flows tutorial, you’ll notice that these two apps appear similar. However, while Bit Flows lets you set multiple triggers and access various ways to connect your actions and triggers, Bit Integrations is more streamlined.

In this instance, you simply connect a Trigger and Action together. Bit Integrations is great for a quick and simple connection. On the other hand, Bit Flows can handle all of your complex needs, workflows, and automations.

Other Functionality Within Bit integrations

Webhooks provide a method to send data to services that don’t have native integrations in Bit Integrations or to trigger actions in other automation tools such as Zapier, Make, or Pabbly Connect.

You can enable this by choosing Webhooks as your destination from the action selection screen. The plugin displays a field where you paste the webhook URL from your destination service.

Most automation platforms will provide webhook URLs in their trigger settings, which you copy into Bit Integrations. You can customize the webhook payload by mapping specific fields or creating custom JSON structures.

In addition, Bit Integrations offers custom triggers and action hooks. This gives you even greater scope to make your automated workflows even more flexible to your needs.

Even though you can consider Bit Integrations a stripped down version of Bit Flows, it doesn’t suffer from a lack of functionality. In fact, it might be the right tool in many of your automation scenarios.

My Final Thoughts on Bit Integrations

Automation is necessary when your manual data transfer processes consume too much time. Bit Integrations (and its more complex sibling Bit Flows) creates connections between WordPress and external platforms without any requiring development skills or external automation services.

The no-code interface makes the plugin accessible to practically everyone who needs automation but doesn’t have dedicated developers on staff. The visual workflow builder provides enough flexibility for most standard use cases while maintaining simplicity if you’re new to automation.

Related articles

Do you have an automation need that Bit Integrations could solve? Share thoughts with me in the comments section below!