ZapBounce and Celigo
Celigo synchronizes systems of record, typically an ERP against a CRM or a commerce platform. That two-way flow creates a specific problem for any derived field.
A verdict written into one system and not the other will be overwritten on the next sync, and nobody will notice because the field will simply be empty again.
A one-sided field gets overwritten by the next sync
Celigo flows map fields between systems. A verdict written into the CRM but absent from the ERP mapping is either wiped on the next sync or excluded from it, and neither is obvious from the flow definition.
That produces a field that is populated after a verification run and empty a week later, which reads as a verification failure and is a mapping one.
The fix is to decide which system owns the verdict and map it explicitly in both directions, or exclude it from the sync deliberately.
How the data moves
Decide which system owns the verdict
One of them. A field written by two systems with no owner is a field that flips depending on which sync ran last.
Map it explicitly, or exclude it explicitly
Both are valid. What fails is leaving it out of the mapping and assuming it survives.
Verify in the flow before the record is written
A Celigo flow can call an HTTP endpoint mid-flow, so the verdict can be attached before the destination record exists.
Use the batch endpoint for the initial clean
The one-off backfill is a batch job rather than a flow, and the flow handles ongoing records.
Setting it up
- Choose the system of record for the verdict field and create it there.
- Add the field to every relevant Celigo flow mapping, in both directions or explicitly excluded.
- Add an HTTP step in the flow that verifies before the destination record is written.
- Run a one-off batch clean of existing records outside the flow.
- Add an error path so a failed verification does not silently write an unverified record.
- Re-check the mapping after any flow change, since a new field is easy to omit.
Celigo: common questions
Why does my verdict field keep emptying?
Almost always a Celigo mapping that excludes it, so the sync writes the source system's empty value over it.
Which system should own the verdict?
The one where marketing or sales acts on it. The verdict is only useful where somebody reads it.
Where does the initial clean run?
Outside the flow, as a batch job. The flow handles new and changed records from then on.
Check a Celigo export today
100 free checks a month, no card. Unknown results and duplicates are never billed.