B2B · CRM SyncMake · Monday · Affinity3 parallel branchesBased on a project I built

Two CRM systems. One version of the truth — without double entry.

Case study by Achiya Cohen, founder of Achiya Automation

One team works in Monday, another in Affinity — and the data has to stay identical. A sync system in Make with real business logic: it doesn't just copy changes, it checks all the boards, validates conditions and updates only when it really needs to.

How it's builtSee the results
3
Parallel branches in the main scenario
↔
Two-way sync
Log
Updates and exceptions
Before & After

Two systems = two versions of the truth One system, two-way sync

Before
  • One team updates in Monday, another team in Affinity
  • Double entry creates repeated work
  • Each system a different truth — errors, arguments
  • No way to know what the real status is
After
  • A change in Monday triggers an update in Affinity according to rules
  • A change in Affinity triggers an update in Monday according to rules
  • Business logic handles the conflicts
  • Logs and exceptions make discrepancies visible for review
2 flows I built

Here's how it works inside

A description of each flow, with identifying details removed.

FLOW · 01

A company moves group in Monday → checks → update in Affinity

The main scenario runs three parallel branches. When a company is moved to a different group in Monday, the system doesn't rush to update: it checks the company's state across all the other boards, applies the business rules (including special conditions that must not be overridden), and only then updates the record in Affinity — including sending an automatic email when needed.

Monday webhookMulti-board checksBusiness rulesAffinity API
Screenshot of the Make scenario. What happens: 1. A company moved group in Monday 2. It's checked across the boards 3. It's found in Affinity 4. Stage updated, email if needed
FLOW · 02

Status change → data pull → sync

When a company's status changes in Monday to a new stage, the scenario pulls the company details, packages them into the required structure and updates the matching fields in Affinity. Its rules determine which fields update and which exceptions need review.

Monday triggerJSON transformArray aggregationAffinity update
Screenshot of the Make scenario. What happens: 1. A status changed in Monday 2. The company is found in Affinity 3. The latest status is checked 4. The stage in Affinity is updated
Results

The numbers you feel every day

↔
Two-way updates
Changes move between systems according to the sync rules
Check
Conditions before update
The logic checks the boards before making a change
Log
Exception review
Updates are retained so discrepancies can be found

Do you have two systems that don't talk to each other too?

CRM, ERP or spreadsheets — if the team copies data between systems, a sync can be built with rules, logs and exception handling.

Let's talk on WhatsAppLeave your details

Want a system like this? Check out our WhatsApp bot service or our pricing & plans.
Let's talk?