GetResponse + 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 GetResponse and SEEN using Make’s native GetResponse and SEEN integrations (App), and receive landing page URL and an email thumbnail URL back to GetResponse 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 “Make an API Call” module to send data back from SEEN to GetResponse.

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

Send Data to SEEN

Create a new Make Scenario, and add the “GetResponse” ⇒ “Watch Contacts” module

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

Set the limit of results. The default set by Make is 2.

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 an “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

Extra Arguments:

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

Adding the “first” and “split” functions to the “First Name” field and the “last” and “split” functions to the “Last Name” field ensures that the first name and the last name of the receiver are sent in separate fields, as GetResponse uses a single “Name” field for contacts by default. This method splits every name based on the space, and sends the first part for “First Name” field and the last part for the “Last Name” field.

Remember to modify the payload depending on the personalisations in your film.

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 GetResponse account.

Give the Event a name - in this example “seen”

Add an attribute for the Landing Page URL - in this example “seen_landing_page_url”

Add an attribute for the Email Thumbnail URL - in this example “seen_email_thumbnail_url”

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

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

Create a webhook

Share your webhook URL with SEEN

Add a new “GetResponse” module, and choose the “Make an API Call” option.

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

URL ⇒ /v3/custom-events/trigger

Method ⇒ POST

Body ⇒ You can use the JSON below in this example:

{
    "name": "seen",
    "contactId": "{{1.customer_id}}",
    "attributes": [
        {
            "name": "seen_landing_page_url",
            "value": "{{1.landing_page_url}}"
        },
        {
            "name": "seen_email_thumbnail_url",
            "value": "{{1.email_thumbnail_url}}"
        }
    ]
}

You can now activate both flows to test the connection. You should now see the Event in your test contact.