Pipedrive. Persons, then hashes.

← All 12 CRMs · Make guide · Zapier guide

Connection type: Native. Sign in with the Pipedrive company that holds Persons. Settings → Data fields → Person. After each field is saved, open it and copy the hash.

Person email is an array. Map email[0].value. Phone is the same — prefer the number marked mobile.

Fields for this CRM

Create the ones marked YES. Map the ones you already store. Do not invent a second current-rate field.

Purpose	Canonical	This CRM	Required	Create?
Contact ID	contact_id	id	Yes	No
First name	first_name	first_name	Yes	No
Last name	last_name	last_name	No	No
Email	email	email	Yes	No
Mobile	mobile	phone	Recommended	No
Current rate	tbt_current_rate	YOUR_CURRENT_RATE_HASH	Yes	Map or create
New-money rate	tbt_new_money_rate	YOUR_NEW_MONEY_HASH	Yes	YES - create or maintain
Loyalty gap (bps)	tbt_loyalty_gap_bps	YOUR_GAP_HASH	Yes	YES - create / compute
Lender	lender	YOUR_LENDER_FIELD_HASH	Recommended	No
Product name	product_name	YOUR_PRODUCT_FIELD_HASH	Recommended	No
Existing client flag	existing_client	YOUR_EXISTING_CLIENT_HASH	Yes	Map
Email opt-out	email_optout	YOUR_OPTOUT_HASH or unsubscribed	Yes	No
Loyalty state	tbt_loyalty_state	YOUR_STATE_FIELD_HASH	Yes	YES - create this
Last loyalty touch	tbt_last_loyalty_touch	YOUR_TOUCH_FIELD_HASH	Yes	YES - create this
Broker owner	broker_owner	owner_id	Recommended	No
Broker email	broker_email	set in watch mapper	Yes	Set in the watch

Full translation and notes: 05-templates/CRM-Field-Map.csv. Gap is in basis points. Example: current 6.40 and new-money 5.90 is a 50 bps gap. Default watch threshold is 25 bps.

Make — watch file to import

Import 02-make-blueprints/01c-TBT-Loyalty-Tax-Watch-Pipedrive.blueprint.json.

Import this file. Sign in. Open Settings → Data fields, copy the hash for each custom field, and replace every YOUR_*_HASH in module 1 and the HTTP mapper. Then import the outreach blueprint.

Everyone also imports 02-make-blueprints/02-TBT-Loyalty-Tax-Outreach.blueprint.json. Import outreach first so you have the webhook URL. Walkthrough: MAKE-Setup-Guide.html.

Make — last-step swap

On the outreach scenario, modules 7, 8 and 9 are HTTP placeholders labelled SWAP. Replace them. The middle (consent, gap gate ≥ 25 bps, OpenAI, broker Gmail) does not change.

Outreach module	Swap for
7 · Create the broker task — SWAP	Pipedrive → Create an Activity (task). Subject {{3.broker_task_title}}, note {{3.broker_task_body}}, linked to the Person id.
8 · Write the CRM note — SWAP	Pipedrive → Create a Note (Person). Content {{3.crm_note}}.
9 · Stamp loyalty touch — SWAP	Pipedrive → Update a Person. Write the hashed state field = touched and the hashed last-touch field = today. Do not skip.

Stamp body (use this CRM’s field names from the table):

{
  "tbt_loyalty_state": "touched",
  "tbt_last_loyalty_touch": "{{formatDate(now; \"YYYY-MM-DD\")}}"
}

Zapier — first module and last three

Zapier cannot import a Make blueprint. Build two Zaps by hand. Full click-path: ZAPIER-Setup-Guide.html. This page is the CRM-specific first and last steps only.

Where	What
Zap A · first module	Schedule by Zapier (daily 09:00) + Pipedrive Find Person / Get Persons in a Filter named Loyalty Tax — Due. Then Webhooks by Zapier → POST to Zap B. Paste the custom-field hashes into the JSON keys that the field map marks YOUR_*_HASH.

Zap B step	Module
B6 Task	Pipedrive → Create Activity. Subject from broker_task_title, note from broker_task_body, Person = contact_id.
B7 Note	Pipedrive → Create Note on that Person. Content from crm_note.
B8 Stamp	Pipedrive → Update Person. Hashed state field = touched, hashed last-touch field = today.

Zap A then POSTs the canonical keys (see the field-map Canonical column) to Zap B’s Catch Hook. Leave auto_email_client as false. Replace [YOUR BROKER EMAIL], [YOUR FIRST NAME], [YOUR BUSINESS NAME].

• Keep the generic name in the field label so the rest of the pack still reads. The API is the hash.
• Leave auto_email_client as false. Default is email the broker, not the client.