Boomi moves the data. Verirow checks the result.
A Boomi process can finish successfully while individual records are still missing, duplicated, or different in the target system.
Your existing Boomi process stays responsible for the sync. Verirow only checks whether the final Source and Target data match.
Set up Boomi verification in five steps
Connect the system containing the original records before the Boomi process moves them.
Connect the destination that should contain the completed Boomi result.
Select a stable identifier that represents the same record in both systems.
Choose the values that must be correct after the Boomi process finishes.
Save the reconciliation so the same verification can run again after future Boomi processes.
Connect the systems Boomi is moving data between
Verirow does not need to become part of the data-moving logic. It only needs read access to the Source and Target records used for reconciliation.
The records before the Boomi process transforms or moves them.
The records that should exist after the Boomi process completes.
Use an endpoint that returns the records required for the verification.
Reconciliation generally requires read access, not write access.
Match the same business record on both sides
Verirow needs one identifier that exists in both Source and Target.
order_idinvoice_idcustomer_idexternal_idskuIf Boomi transforms the field name during the process, the business value still needs to represent the same record on both sides.
A changing status, timestamp, description, or generated value is usually not a safe record key.
Save the Boomi reconciliation once
Once Source, Target, matching key, and comparison fields are correct, save the configuration as a reusable check.
Shopify Source + NetSuite Target + order_id + status, quantity, total.
That saved check becomes the verification definition you can run manually or trigger after a Boomi process.
Run Verirow after the Boomi process completes
The cleanest workflow is to trigger the saved Verirow check only after Boomi has finished writing the relevant target data.
The normal integration process finishes.
A protected request starts the saved verification.
Verirow independently reads and reconciles both systems.
If the target system processes records asynchronously, trigger Verirow only after those records are expected to be available.
What Verirow can reveal after Boomi
The Source and Target record match.
The expected record exists on one side but not the other.
The record exists, but one or more compared values differ.
The selected identifier appears more than once where it should be unique.
Common Boomi verification issues
Boomi succeeded but Verirow shows Missing
Check whether the target write completed before Verirow ran, and confirm the same matching key exists on both sides.
Most records show Different
Review field mappings and any transformations performed by the Boomi process. The Source and Target values may be semantically equivalent but formatted differently.
Verirow runs too early
Add the verification trigger only after the target data is committed and available to the API Verirow reads.
The same ID appears as Duplicate
Confirm the selected record key is truly unique. If it is, the duplicate may represent a genuine target data problem.
The connection cannot load records
Recheck API URL, authentication, permissions, Records Path, and the endpoint response structure.
Boomi + Verirow questions
Does Verirow replace Boomi?
No. Boomi remains the integration engine. Verirow runs after the Boomi process to independently verify the result.
When should Verirow run?
Run Verirow after the Boomi process has completed and the target system has finished receiving the records you want to verify.
What does Verirow verify after Boomi?
Verirow compares source and target records using a shared record ID and the fields you choose to compare.
Can a Boomi process succeed while the data is still wrong?
Yes. A successful process confirms the integration flow completed, but it does not by itself prove that every target record arrived with the expected values.
Do I need to change my Boomi integration?
Not necessarily. You can keep your existing integration architecture and add Verirow as a separate verification step after the process.
What should I use as the record ID?
Use a stable identifier that exists in both systems, such as order_id, customer_id, invoice_id, external_id, or another business key.