What Verirow actually does
An integration can report success even when the final data is incomplete or wrong. Verirow checks what happened after the integration finishes.
Verirow reads both sides, identifies the same records, compares the fields you care about, and reports anything that does not match.
Verirow does not replace Boomi, Workato, Make, Zapier, your custom API, or another integration platform. It verifies the result they produced.
Your first verification in 5 steps
Connect the system containing the original records.
Connect the system that should contain the synced data.
Select the field that identifies the same record on both sides.
Choose the values that must match after the sync.
Review OK, Missing, Different, and Duplicate results.
Set up Verirow with your integration platform
Verirow uses the same reconciliation model across platforms, while the automation and trigger flow can differ by integration.
Verify source and target data after a Boomi process completes.
Open Boomi guide →WORKATOWorkato + VerirowRun post-recipe reconciliation after a Workato workflow.
Open Workato guide →MULESOFTMuleSoft + VerirowVerify source and target data after a MuleSoft flow completes.
Open MuleSoft guide →Connect the two sides you want to compare
Open Connections and create the systems Verirow needs to read.
Example: Shopify orders before they are sent to an ERP.
Example: the matching orders created in NetSuite.
Use the endpoint that returns the records required for the comparison.
Use this when the API returns records inside a nested JSON property.
Tell Verirow which records belong together
Verirow needs one key that represents the same logical record in Source and Target.
order_idcustomer_idinvoice_idexternal_idskuThe best key is stable, present on both sides, and unique for every record being compared.
Names, timestamps, descriptions, or fields that can change are usually poor record identifiers.
Choose what must be identical
You do not need to compare every property. Select the fields that matter for the business outcome of the sync.
status: "paid"status: "paid"quantity: 4quantity: 4total: 129.00total: 120.00In this example the record exists on both sides, but total is different, so Verirow reports the record as DIFFERENT.
Run the reconciliation
Open Run Check, choose Source and Target, configure the record key and comparison fields, then start the verification.
Verirow checks the records and summarizes what matched and what needs attention.
Understand every status
The same record exists on both sides and all selected fields match.
Verirow found the record on one side but not on the other.
The record exists on both sides, but at least one selected value does not match.
The same record identifier occurs more than once where it should be unique.
Save repeatable verification workflows
When you repeatedly compare the same systems, save the check once instead of configuring it from scratch each time.
Source + Target + record key + comparison fields saved as one reusable verification.
Verify without manually checking every sync
Once a verification setup is saved, Verirow can become part of the operational workflow instead of a one-time manual audit.
Your normal workflow moves the data.
The saved comparison checks Source against Target.
Focus attention on records that did not reconcile.
Keep evidence of what happened
Run history lets you return to previous checks instead of treating every verification as a disposable result.
- See previous verification runs.
- Review counts and reconciliation outcomes.
- Open a run and inspect individual discrepancies.
- Use alerts to surface failed verification outcomes.
Give Verirow only the access it needs
Verirow needs to read the records required for reconciliation. Your integration platform remains responsible for moving or updating the actual data.
Prefer credentials limited to the endpoints and data needed for verification.
Reconciliation normally requires reading records, not modifying them.
Automated verification should use authenticated or protected trigger mechanisms.
When a check does not look right
My connection test fails
Check the API URL, authentication details, permissions, and whether the endpoint can be reached. Confirm the endpoint actually returns records.
Verirow loads zero records
Inspect the API response structure. If records are nested, verify the configured Records Path points to the array that contains them.
Everything appears as Missing
The most common cause is an incorrect record key or IDs represented differently between Source and Target.
I see unexpected Different results
Verify that the mapped fields represent the same business value and check whether formatting, data type, or transformed values differ between the two systems.
I see Duplicate records
Check whether the selected key is truly unique. If it should be unique, the duplicates may represent a real data-quality problem in Source or Target.
Common Verirow questions
Does Verirow move or sync my data?
No. Verirow is the verification layer. Your existing integration platform moves the data; Verirow independently checks the result.
What systems can I compare?
Any supported source and target that Verirow can read through a configured connection. The important part is that both sides expose the records you want to compare.
What should I use as the record ID?
Use a field that uniquely identifies the same logical record on both sides, such as order_id, customer_id, external_id, invoice_id, or SKU when SKU is truly unique.
Do field names need to be identical?
Not necessarily. What matters is that Verirow knows which source field corresponds to which target field.
What does MISSING mean?
The record was found on one side but not the other. For a normal source-to-target sync, this often means a record expected in the target did not arrive.
What does DIFFERENT mean?
The record exists in both systems, but one or more fields you selected for comparison contain different values.
What does DUPLICATE mean?
The same record identifier appears more than once where Verirow expects it to be unique.
Does a successful integration run mean the data is correct?
Not necessarily. A successful run tells you the integration workflow completed. Verirow checks the actual records afterward.
Can I reuse the same reconciliation setup?
Yes. Save the configuration as a Saved Check so you do not have to configure the same source, target, key, and comparison fields again.
Can Verirow run automatically?
Yes. Saved checks can be used for recurring verification and integration-triggered verification where those options are configured.