Pipedrive CRM + 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 Pipedrive and SEEN Make’s native Pipedrive integration (App), and receive landing page URL and an email thumbnail URL back to Person’s custom fields.

This example uses the “New Person Event” module in Make, which triggers when a new contact is created, and the “Update a Person” module to send data back from SEEN to Pipedrive.

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

Send Data to SEEN

Create a new Make Scenario, and add the “Pipedrive” ⇒ “New Person Event” module.

Connect your Pipedrive account to Make following the steps provided by Make (this example used the Pipedrive API Token).

Choose your Event Action. This example uses “added”.

Add an HTTP module, and choose “Make an API Key Auth Request”, and fill it out with the following:

Credentials → Add

Under “Key” add “Token {token}” (you will receive your Token from SEEN)

API Key placement → “In the header”

API Key parameter name → Authorization

URL → https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/

You will receive your {campaign_slug} from SEEN to call the correct endpoint.

Body type → Raw

Content type → JSON

Request content:

You can use the code below in this example (you might need to modify the values by dragging and dropping in the MAKE UI):

[
	{
		"first_name":"{{1.current.first_name}}",
		"last_name":"{{1.current.last_name}}",
		"email":"{{1.current.email[].value}}",
		"customer_id":"{{1.current.id}}"
	}
]

Remember to use the “current” values, instead of the “previous” values.

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.

Receive data back from SEEN

Add new custom data fields (Field type ⇒ Text) to the Person level for the landing page URL and the email thumbnail URL.

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

Add a “Webhook” module to the scenario.

Share your webhook URL with SEEN

You can create the webhook data structure manually by using the JSON structure below if you are using the standard payload defined in our documentation. In other cases contact SEEN for the payload structure.

{
        "customer_id": "101",
        "campaign_slug": "onboarding",
        "landing_page_url": "your.subdomain.com/v/12345",
        "video_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/output.m3u8",
        "thumbnail_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/thumbnail.jpg",
        "email_thumbnail_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/email_thumbnail.jpg"
}

Add a new Pipedrive module, and choose the “Update a Person” option.

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

Person ID ⇒ Customer ID (from the webhook module)

SEEN Landing Page URL ⇒ Landing Page URL (from the webhook module)

SEEN Email Thumbnail URL ⇒ Email Thumbnail URL (from the webhook module)

You can now activate both flows to test the connection. You should now see the URL’s in your test Person’s fields.