Architecture
- 01IntakeQ webhook
- 02Make.com
- 03IntakeQ API
- 04Route by form type
- 05Deduplicate
- 06Monday.com CRM
The problem
Patient intake had to land in a Monday.com CRM in real time, routed by form type. The scenario was running, but one form type was silently failing to sync and dates were importing as invalid values.
What I built
- 1
The scenario captures the IntakeQ webhook, pulls the full record through the IntakeQ API and routes it by form type before creating or updating the patient on the correct board.
- 2
Two-key deduplication — email first, phone as fallback — so returning patients update their existing record instead of creating duplicates.
- 3
Fixed the routing bug where one form type silently failed to sync.
- 4
Converted and validated the API's Unix-timestamp dates so only clean dates reach the CRM, and renamed every module so the logic is readable.
Result
Reliable, hands-off patient intake: no manual data entry, no duplicate records, and every form type syncing correctly.


