Integrate Pabbly Connect with Omnisend

Pabbly Connect is the integration software to pass data between different business tools and services. Pabbly Connect is an integration platform through which you can connect different applications within a few clicks. It has over 1000 apps, including Google Forms, Google Drive, and many more.

Integrate Omnisend seamlessly with over 3000 applications, enabling the transmission of any desired contact data to Omnisend.

In Omnisend, go to Apps → Search for Pabbly Connect → Click Connect now → Copy API Key.

Navigate to Pabbly's Dashboard tab → click Create Workflow and name your workflow as you see fit.

Find a trigger for the workflow; in our example, we will use WooCommerce.

Select a trigger action; this will contain data that can be passed to Omnisend. In our example, we will use newly created orders.

Follow the instructions to properly set up the trigger. In our case, we need to create a new order for a proper webhook response.

If you do not see correct or enough data in the response, click Re-Capture Webhook Response and take the action needed for the trigger. In our example, it's placing a new order. Now that we see the correct data, we can continue to the next step.

For action - find and select Omnisend.

For the action event, you can choose to Create Subscriber or Update Subscriber.

Once the action event is selected, click Connect and add the Omnisend API Key you created earlier.

For the email field, you can select a specific or dynamic email from a trigger event. In our example, we use the email used to place an order.

Before mapping custom data, you need to select the identification channel - email and/or phone number. In our example, we select both channels, so we enable 'Map' and enter "email,phone" for identifier type and "email,sms" for identifier channel.

When mapping properties, select the trigger action's data point that would match the contact's information in Omnisend. In our example, we chose 'Billing Email' for the contact's email and 'Billing Phone' for the contact's phone.

For status, we chose 'non-subscribed' because we did not ask permission to subscribe. The status date is optional - if not provided, the status date will be automatically filled with the current date-time. We also added a subscription source, so it would be easier to understand where the subscription status comes from in Omnisend. Below, you can see what our example looks like so far.

First and Last names are self-explanatory, while for tags, we add a specific data point from our trigger event and a static one for easier segmentation in Omnisend.

'Send Welcome Email' will allow you to trigger welcome automation in Omnisend if 'True' is selected; if you don't want this created contact to trigger welcome automation, select 'False.'

Follow the same rules for other fields. When you reach 'Custom Properties,' you can map any other data to customers you did not find in previous fields. For example, we want customers to add 'Shipping method' and 'Payment method' as custom properties.

Once done, click Save & Send Test Request, and you should receive a similar response.

The test contact should have been created/updated in Omnisend with all mapped properties if everything was set up correctly. If not, you can follow the response values to see if any errors are present and can be corrected.

Step 6. In Omnisend, check the box I have completed all the steps and click Confirm.

Once Pabbly is set up and connected, you will be able to pass these properties to Omnisend: