CRM 06 · Connective · API

Connective. Mercury, if they let you.

Ask your Connective BDM or support, in writing, for API credentials that can read clients / opportunities and write custom fields plus an activity. Often this is Mercury / Connective CRM — use whichever they grant. This pack does not invent the URL.

APIv1.0Five TBT fieldsGap default 25 bps$99 AUD once

← All 12 CRMs · Make guide · Zapier guide

Connection type: API. HTTP modules only after they have said yes. Canonical crm value: connective.

Ask in writing first

If the answer is no, stop. Use the Sheets bridge the same week. Do not half-build an HTTP scenario you cannot authenticate.

Opportunity vs client

Current rate, lender and product usually live on the opportunity / loan. The email lives on the client. Your HTTP search should join them, or you run two requests using the URLs they issued. Create the five TBT fields on one object and stay there.

Exclude opportunities still in lodgement or unconditionally approved. This engine is for settled existing clients.

Fields for this CRM

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

PurposeCanonicalThis CRMRequiredCreate?
Contact IDcontact_idcontactIdYesNo
First namefirst_namefirstNameYesNo
Last namelast_namelastNameNoNo
EmailemailemailYesNo
MobilemobilemobileRecommendedNo
Current ratetbt_current_ratecustom.tbt_current_rateYesMap or create
New-money ratetbt_new_money_ratecustom.tbt_new_money_rateYesYES - create or maintain
Loyalty gap (bps)tbt_loyalty_gap_bpscustom.tbt_loyalty_gap_bpsYesYES - create / compute
LenderlenderlenderRecommendedNo
Product nameproduct_nameproductNameRecommendedNo
Existing client flagexisting_clientexistingClientYesMap
Email opt-outemail_optoutemailOptOutYesNo
Loyalty statetbt_loyalty_statecustom.tbt_loyalty_stateYesYES - create this
Last loyalty touchtbt_last_loyalty_touchcustom.tbt_last_loyalty_touchYesYES - create this
Broker ownerbroker_ownerownerIdRecommendedNo
Broker emailbroker_emailset in watch mapperYesSet 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

No dedicated watch file for this CRM. There is no dedicated Connective watch file. HTTP search using the URL they issued → map to the canonical payload → POST to the outreach webhook. Or import the Sheets bridge until access is granted. See 02-notes.md. Everyone still imports the outreach blueprint.

Fallback file: 02-make-blueprints/01e-TBT-Loyalty-Tax-Watch-GoogleSheets-Bridge.blueprint.json.

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 moduleSwap for
7 · Create the broker task — SWAPHTTP request to the task/activity URL they issued. Title {{3.broker_task_title}}, body {{3.broker_task_body}}, linked to contact_id.
8 · Write the CRM note — SWAPHTTP POST a note. Body {{3.crm_note}}.
9 · Stamp loyalty touch — SWAPHTTP PATCH using field-map names (custom.tbt_loyalty_state, custom.tbt_last_loyalty_touch). Confirm with the aggregator. 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.

WhereWhat
Zap A · first moduleWebhooks by Zapier → Custom Request against the search URL they issued (Mercury / Connective CRM, whichever they grant). Filter gap ≥ 25, settled, not opted out. Then POST the canonical payload to Zap B. Map contactId, firstName, custom.tbt_*.
Zap B stepModule
B6 TaskWebhooks → Custom Request. Task URL they issued. Title from broker_task_title.
B7 NoteWebhooks → Custom Request. Note URL they issued. Body from crm_note.
B8 StampWebhooks → Custom Request. Update URL they issued. State = touched, last touch = 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].

Fallback — Google Sheets bridge (01e)

If API access is refused, export settled clients with current rate, new-money rate and gap into the Google Sheet and import 01e the same week.

T Test on yourself before any live send

  1. Create yourself as a settled existing-client test record with a real email you read, a current variable rate, a new-money / retention reference, and tbt_loyalty_gap_bps at or above 25. State due or queued. Last touch empty.
  2. Run the watch (Make scenario 01, or Zap A) with a limit of 1, filtered to only this record.
  3. Confirm the broker email arrives. Confirm you did not get a client email. auto_email_client stays false.
  4. Confirm the broker task, the CRM note (or sheet write-back), and the stamp: state touched, last touch = today.
  5. Run again the same day. The engine must not draft you a second time. Then set state to opt_out and run again — must not draft.

If the stamp fails, stop. Fix it before anyone else is in the set. After the loop is proven on you, you may flip auto_email_client — not before. Read 04-compliance first.