Skip to main content

Integrate SureTriggers with Omnisend

Learn how to integrate SureTriggers with Omnisend

Written by Sarunas

Through SureTriggers, you can integrate Omnisend with hundreds of other apps and automate repetitive tasks. For a full list of integrations, visit this page.


Setup Process

To integrate SureTriggers with Omnisend, follow these steps.

Step 1. Click on your store name in the top right corner → open the Apps tab.

Find SureTriggers and click Connect now.

Then click Copy API Key.

Step 2. Log in to https://app.suretriggers.com/ and go to Apps → click Create New Connection.

Search for and select Omnisend.

Enter an appropriate name for this connection, paste your API key, and click Update Omnisend.

You should now see Omnisend among your connections.

Now, it will be available to be selected when setting up your workflow.

Creating a Workflow

We will create a simple workflow that links Google Forms to Omnisend. This means that whenever a contact completes a form, their contact details will be added to Omnisend. For more information, visit this page.

Step 1. Go to Workflows → click Create New Workflow.

Then, type in a name for your workflow and click Create.

Step 2. Click Add Trigger - this will trigger the workflow.

Now, select the trigger. In our example, it's a specific form from our Google Forms list. Remember to click Fetch Data before saving.

Step 3. Now that the trigger is selected, click the + sign to add an action.

Find Omnisend and select Create Contact or Trigger Custom Event. In our example, we will choose to create a contact.

💡 For more information about custom events, visit this page.

  • Select connection field: select your Omnisend connection.

  • Select type field: email or phone.

    • When entering email or phone, type @ to select an input from your trigger that would give an email or phone, unless you want to use this action on the exact contact that you enter here.

  • Select contact status field: in our example, we selected Subscribed, because we implied consent in the form.

You can map this to a property from your trigger through the @ variable, but it must be specifically subscribed, nonSubscribed, or unsubscribed to avoid issues.

Note: All other properties are optional.

We highly recommend creating a specific tag for this workflow so that you can quickly identify and segment contacts. Be sure to test this action and click Save once done.

Step 4. You can add more actions to this workflow. When you're done, click Publish, and you are all set now.

What Data Is Passed

The integration passes the following contact data:

  • Email address or Phone number

  • First name

  • Last name

  • Address

  • City

  • State

  • Country

  • Country code

  • Zip / Postal code

  • Tags


If you have any questions or encounter issues, don't hesitate to contact our award-winning support at [email protected] or through our in-app chat.

Did this answer your question?