When you want to pull or revert an integration, you must review any changes between your current and remote versions. Various features, including references, difference (diff) screens, and conflicts, help you analyze how your changes affect your integration.
Note
You need Manage access or above to review changes within a pull or revert.
The Review Changes screen displays all differences between your current and remote integration. Use the features below to analyze changes, identify conflicts, and prepare for the merge.
Conflicts arise when identical resources are modified between the current and remote integration. You'll run into a conflict if:
-
The current and remote integration names don't match:
-
Amazon – NetSuite integration
-
NetSuite – Amazon integrations
-
The same hook has edits on the same line
-
-
The resource names don't match:
-
Get Amazon sales vs Get sales from Amazon
-
-
The same hook has edits on the same line.
Conflicts can be introduced when multiple users are working on the same integrations. To resolve them, edit either one of the integrations to match the other, then merge and pull.
You can use Refresh to review any changes to your integration in real time. The refresh button works best if you're using two integrator.io webpages; one for editing and making changes to an integration and the other for reviewing merge data in real-time. This way, you can update an integration and see its effects on your merge.
This list displays all the flows containing a reference in your account. For example, an export (Export all Salesforce leads) could be used in multiple integrations, like Salesforce – NetSuite and Salesforce – Acumatica.
Important
Any modified references (such as imports and exports) are changed for all integrations and flows. If you modify a reference you must check this to ensure that it isn't modifying anything in a different integration.
The Review Changes screen lists every export, import, flow, and script affected by your pull or revert, grouped by resource type, with an Action label indicating whether each will be updated, added, or removed.
Warning
Lookup cache data is not stored or managed in Integration Lifecycle Management (ILM). Although references to the lookup cache are included (like in mappings and transformations), ILM does not support lookup cache data.
Important
In your JSON data, imports (including lookups) and exports are called pageProcessors and pageGenerators (PP and PG), respectively. This applies if you are inspecting the raw JSON diff — most builders can ignore this.
Warning
Modifying a resource in one integration will modify it throughout all your integrations. Check your references before making changes that might affect other integrations.
This change includes new, modified, and deleted resources. Notice that the Action is available for each change (removed, update, new).
If components you expect to see as Action: Update appear as Action: Removed and Action: New instead, see Troubleshooting in Pull changes from one integration to another.
In this situation, you're deleting an export shared between multiple flows. Exports are not linked to a single integration since they can simultaneously be used in multiple integrations. If an export is removed from a flow, it won't be deleted from your account. Instead, references to it in the flow are removed. Always check your references to ensure you're not deleting or editing a resource used in multiple flows or integrations.
Scripts are commonly used in multiple integrations at once. If a script is removed from a flow, it won't be deleted from your account. Instead, references to it in the flow are removed.
Warning
Modifying a script in one integration will modify it throughout all the integrations you use. Check your references before making changes that might affect other integrations.
In this example, you've removed an existing script from a current integration and then you're pulling the changes. The script isn't deleted from your entire account, but it is deleted from the flow.
-
Navigate to the hook you want to delete from your flow.
-
Select your script, then select None.
-
Save the hook.
-
Create a pull from the remote integration to your current integration.
-
Verify that the script has been deleted.
In this situation, you've modified, and then deleted, an existing script and modified a second script in a different flow. It's important to remember that this script is not going to be permanently deleted from your account. Instead, you've deleted it from your flow and modified it in another.
The first script you modified and then deleted is highlighted in red to show that it was removed from your flow.
The deleted changes in your second script are highlighted in red, and the updates are highlighted in green.
A broken component ID linkage between Sandbox and Production can cause the Review Changes panel to show existing components as Action: Removed and Action: New instead of Action: Update during a pull revision. This typically appears when pulling changes from Sandbox to Production — existing exports, imports, or flows are listed twice: once as Action: Removed and again as Action: New (or as Action: Deleted paired with Action: New for flows) — rather than the expected single Action: Update entry.
This is different from components that were intentionally deleted or added. If you see the same component name appearing as both Removed and New in the same pull preview, that is the signal that something has gone wrong.
This typically happens when multiple significant structural changes are made in the Sandbox integration between pull revisions — such as renaming exports or imports, recreating components, or making several large changes at once. After enough changes accumulate, the platform loses the ID-to-ID mapping between the Sandbox and Production components.
Do not proceed with a pull that shows this pattern. Continuing may delete flows, create duplicates, and leave your Production integration in an inconsistent state that is difficult to recover from.
-
Stop and do not delete your existing Production integration. It may share components with other integrations or clones. Deleting it prematurely can cause additional data loss.
-
Create a fresh clone of your Sandbox integration into the Production environment.
-
Test the new clone by making a minor change in Sandbox and pulling to the new clone. Confirm the pull preview shows Action: Update — not Removed/New — before proceeding.
-
Use the new clone as your Production integration going forward.
Important
Re-cloning resets the integration's revision history in the target environment. Previous revision history will not carry over to the new clone.
Make small, incremental changes in your Sandbox integration between pull revisions. Avoid making multiple large or structural changes — renaming, recreating, or significantly modifying several exports, imports, or flows at once — before pulling. Smaller, more frequent pulls reduce the risk of ID mapping issues.