How do I send handwritten cards from my CRM?

#Choose a connection for your CRM

#The pattern that works, in order

1. Decide what the trigger is, precisely

   Deal moves to closed-won is a trigger. Deal updated is not — it will fire on every note, and every fire is a card and a credit.

2. Confirm the CRM record actually carries a postal address

   This is where most integrations fail. Sales CRMs are full of contacts with an email, a phone number and no street. Check the field coverage before you build anything.

   You’ll know it worked when You can name the CRM fields that map to line1, city, state and zip for the majority of the records you intend to trigger on.

3. Test the sending route

   Create an inbound hook or use your chosen connector. Send one request with your own address to check the complete path. This creates a real paid card. Use a stable idempotency key so a retry cannot create a duplicate.

   curl -X POST https://scribblecards.com/api/v1/hooks/whk_YOURTOKEN \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Dana Okafor",
       "line1": "88 Colin P Kelly Jr St",
       "city": "San Francisco",
       "state": "CA",
       "zip": "94107",
       "message": "Thanks for four great years, Dana."
     }'

   You’ll know it worked when A 201 with a card code, and the card visible under Orders.

4. Move to the API when you need control

   Use POST /api/v1/cards when you need to choose the design per card, set an arrive_on date, or read the status back later. Create a key under Integrations with only the scopes you need.

5. Decide how you learn a card was mailed

   Under Integrations, use Webhooks to your system → Add endpoint and subscribe to card.mailed. Verify the signature on each request.

   You can also poll GET /api/v1/cards/{card_code} and check mailed_at. Use the card code returned by the send.

   You’ll know it worked when The delivery log on the Integrations screen shows HTTP 200 against your endpoint for a test delivery.

6. Sync the address book, if you need lists

   If you want to run automations off CRM data — birthdays, renewal dates — push contacts in with POST /api/v1/contacts and always send an external_id. See keeping contacts in sync for the pitfall.