Zapier – SEEN Documentation

⚠ Pending update: This guide was originally created for API 1.0 (Now Legacy), adjustments may be necessary if you are using via API 2.0. For the latest information please refer to SEEN API 2.0 - Authorization & SEEN API 2.0 - Create Data or contact us.

Create a Zapier account here: https://zapier.com/

Firstly, select your Trigger. This is what connects any of your platforms to Zapier.

In order to format a request and send to SEENs API, you need to select the Action called “Custom Request in Webhooks by Zapier”.

In the first step, called “App & event”, make sure you have selected “Webhooks by Zapier” and Event type “Custom Request”.

In the “Action” step, enter the following:

Method - POST

URL - https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/ where {campaign_slug} is replaced by a string provided by SEEN for your campaign(s) specifically.

Data Pass-Through - No value needed.

Data - here’s an example of a payload, but please note that it may need to include more values based on your specific campaign setup. SEEN will inform you of any changes needed.

Please note that based on the “Trigger” you’ve setup above, you will have the option to select placeholders in the below fields.

Please check our general API documentation for further information

[
    {
        "first_name": "{first name}",
        "last_name": "{last name}",
        "email": "{email},
        "phone": "{phone number}",
        "customer_id": “{customer id}”,
        "extra_args": {
            "company": “{company name}”
        }
    }
]

Unflatten - Select “Yes”.

Basic Auth - No value needed.

Headers - Add the following:

Header name “Authorization” and value “Token {string}” where {string} will be provided by SEEN for your campaign(s) specifically.

Header name “Content-Type” and value “application/json; charset=utf-8”

Now you can go to the “Test” step and test your action. If you get green ticks on all 3 steps, it was successful 🎉