Omnisend + Make – SEEN Documentation

Prerequisites:

MAKE plan with enough monthly Ops to support the volume of contacts.

This guide will help you set up a trigger-based integration between Omnisend and SEEN using Make’s native Omnisend and SEEN integrations (App), and receive landing page URL and an email thumbnail URL back to Omnisend as a custom event trigger.

This example uses the “Watch New Contacts” module in Make, which triggers when a new contact is created and the “Trigger a Custom Event” module to send data back from SEEN to Omnisend.

This example uses the profiles first name and last name as the personalisations, and their email address as their ID.

Send data to SEEN

Create a new Make scenario, and add the “Omnisend” ⇒ “Watch New Contacts” module.

Connect your Omnisend account to Make following the steps provided by Make.

You can modify the limit, but keep in mind that the rate limit for SEEN’s API is 1000 calls per hour

Choose “Where to start”.

In this example we choose “From now on”

Add a “SEEN - Create a video” module, and fill it out with the following:

Create a Connection:

Add the Token you have received from SEEN.

Add the Campaign Slug you have received from SEEN.

Standard fields:

Add the standard fields you will be sending in. Note that both First Name and Customer ID are mandatory fields

Add Email to the Customer ID field in this example

Extra Arguments:

If you use additional data fields in you video, you can map them by using Key-Value pairs under Extra Arguments.

You can now create some test contacts and run the scenario once.

If everything worked as intended, you can now activate the scenario to run in your preferred time intervals

We recommend short intervals to get the film to new contacts as soon as possible.

Receive data back from SEEN

Create a new Custom Event in your Omnisend account using this endpoint.

In this example we use “SEEN” as the “systemName”.

You can use Postman or another similar service to call the API.

Trigger the Custom Event once using this endpoint to create a structure.

You can use the JSON structure below to create the structure

{
"email": "Email address of your test contact", 
"fields": {
"thumbnail_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/email_thumbnail.jpg", 
"landing_page_url": "your.subdomain.com/v/12345"
					}
}

Create a new Make scenario to send data back from SEEN to Omnisend.

Add a “SEEN - Watch for created video” module to the scenario.

Click on “Create a Webhook” and name your webhook.

Share your webhook URL with SEEN

Add a new “Omnisend” module, and choose the “Trigger a Custom Event” option.

You will be able to reuse the Omnisend connection you created in the first step, so no need to re-authenticate.

On the “Event ID” field, choose “SEEN”

You will see your fields in the bottom

Map “Landing Page Url” to “SEEN Landing Page URL”

Map “Email Thumbnail Url” to “SEEN Email Thumbnail URL”

Map “Customer ID” to “Email”

You can now turn on the Scenario, and test the full integration. You should now be able to see the Custom Event on the Contact page.