Playbook · Get your deals in

Keep a CRM in step

Customer Magic connects to no CRM, on purpose: your assistant already does. This playbook has it carry what changed on one side to the other, and stop to ask when the two disagree.

Say this to your assistant

Keep my CRM and Customer Magic in step. Start by asking me which records and which fields, and show me what would change before you write anything.

Works in any assistant connected to Customer Magic. Not connected yet?

You need

Your CRM or sheet connected to the same assistant
A decision on which deals belong in both: one pipeline or list, not everything

You end with

Each shared deal exists in both places and knows the other’s id
What you did on the board shows up in the CRM, and the other way round
A short list of the few things only you can decide

What happens, in order

01
It proves both connections work
One real record read from each side. If either fails, it stops there.
02
You agree the rules once
Which records, which fields, which direction, and who wins when both changed. A sensible default: the CRM owns contact details, the board owns the next step and the history.
03
The first run pairs everything up
CRM records come onto the board, board deals you choose go into the CRM, and each side stores the other’s id.
04
Every later run moves only what changed
The board keeps a record of every change and who made it. Your assistant reads what is new since last time, applies it, then brings the CRM’s changes back.
05
You get three numbers
Pushed, pulled, and left for you. Where both sides changed the same field, you see both values and choose.

What it will never do

Delete a record on either side
Pick a winner silently when both sides changed
Write its own changes back round in a circle

Good to know

Which CRMs does it work with?: Any your assistant can read and write. The playbook is the same; only the connection differs.
Does it run on its own?: If your assistant can run things on a schedule, yes. Otherwise say “sync my CRM” whenever you want it done.
What if my assistant forgets where it stopped?: It starts again from the beginning. Nothing is duplicated; it only takes longer.

The whole playbook · 119 lines

Read what your assistant reads

This is the file itself, section by section. It names the exact actions your assistant takes on your board, in the order it takes them.

Agree the map before the first write. Which records, which fields, which direction, and which side wins when both changed.
Never delete on either side. A deal dropped on the board is a status change in the CRM at most, and only if the person asked for that.
Never pick a winner silently. When the same field changed on both sides, show both values and ask.
Every paired deal carries an `externalId`, written as system:id (attio:rec_8f2, sheet:row-14). It is the only thing that makes a second run safe.