The Review changes panel appears during a pull or revert and lists every resource affected by the operation — integrations, flows, exports, imports, scripts, APIs, tools, and topics — with an action label indicating whether each will be updated, added, or removed. Use this reference to understand what each panel feature does, what the action labels mean, and what to expect for each resource type before you complete a pull or revert in Integration Lifecycle Management (ILM). For the integrations ILM supports, see Supported integrations and resources.
Permission — You have Manage access to the integration, or you're an account owner or administrator. See Manage user roles & permissions to an account.
Panel layout
- Header — The panel title with a help icon, the conflict count (for example, 0 conflicts), the refresh icon, Expand all, Revisions guide (opens in a new tab), and the close icon. During a revert, the header has no conflict count, because reverts never create conflicts.
- Resource groups — Changes are grouped by resource type — for example, Imports, Flows, and Integrations. Select a group heading to collapse or expand it.
- Resource rows — Each resource row shows the resource name, its Action label (for example, Action: New or Action: Update), References, and an expand icon that opens the diff in a full-size view.
- Diff — A side-by-side comparison labeled Before pull and After pull (Before revert and After revert during a revert). Removed lines are highlighted in red and added lines in green.
- Collapsed lines — Unchanged lines between changes are collapsed behind Expand N lines … links. Select a link to show those lines.
- Footer — Next continues to the next step: for a pull, it merges the changes or opens the Merge changes panel; for a revert, it opens the Revert changes panel. Close closes the panel.
- References — References on each resource row, to the left of the expand icon, shows the integrations and flows that use that resource.
Panel features
Conflict count
The conflict count at the top of the panel shows how many conflicts the pull contains. You can't continue a pull until the count returns to 0 conflicts. Reverts never create conflicts, so the count doesn't appear during a revert. To learn what causes conflicts and how to clear them, see Resolve conflicts.
Refresh
The refresh icon next to the conflict count reloads the panel to reflect any changes made to the integration since the pull or revert was initiated. Changes made after you initiate a pull aren't shown in Review changes until you select the refresh icon, so refresh before you merge to include them in the pull. It's most useful when you have the integration open for editing in one browser tab and the Review changes panel open in another — you can make a change, switch tabs, and select the refresh icon to see the effect on the pending merge immediately.
Expand all
Select Expand all to expand every resource row at once. By default, resource rows are collapsed. After you select it, Expand all changes to Collapse all, which collapses every row again.
References
Select References on a resource row to see every integration and flow in your account that uses that resource. For example, if the pull includes an export called "Export all Salesforce leads," the References list shows every integration and flow that uses that export.
Important: Modifying a shared reference — an import, export, or other shared component — changes it across all integrations and flows that use it, not just the one you are pulling into. Always check the References list before completing a merge to confirm you are not unintentionally modifying resources in a different integration.
Warning: When you open a shared resource to edit it, a Proceed with caution banner appears at the top of the editor showing how many places use it. Select Used by in the banner to review all references before saving changes.
Action labels
The Action label on each resource row in the Review changes panel indicates what will happen to that resource when the pull or revert completes. The definitions below use pull terms: the current integration is the one you're changing, and the remote integration is the one you're pulling from. During a revert, the comparison is between the integration's current state and the selected revision.
| Action | What it means |
|---|---|
| Update | The resource exists in both the current and remote integration. The remote version contains changes that will be applied to the current integration. |
| New | The resource exists in the remote integration but not in the current integration. It will be added to the current integration when the pull or revert completes. |
| Removed | The resource exists in the current integration but has been deleted from the remote integration. It will be removed from the current integration when the pull or revert completes. |
| Deleted | A flow has been removed from the remote integration. Used specifically for flows; functionally equivalent to Removed for other resource types. |
Important: If a resource you expect as Action: Update appears as Action: Removed paired with Action: New, don't proceed with the merge; see Unexpected Removed and New actions in Review changes.
Resource scenarios
Updated resources
When a resource has been modified in the remote integration, it appears with Action: Update. The panel shows the specific fields that changed — for example, an export whose HTTP method was changed from POST to GET, or whose relative URI was updated to include a date variable. Each change is shown with a few surrounding unchanged lines for context; longer runs of unchanged lines are collapsed behind Expand N lines … links.
New resources
When a resource exists in the remote integration but not in the current integration, it appears with Action: New. The full resource definition will be added to the current integration when the merge completes. If the new resource uses a connection that doesn't exist in the current environment — for example, a new import that uses a new connection — the merge adds a connection step. You configure the connection in the Merge changes panel before the merge can complete. See Merge changes for details. During a revert, connection steps appear in the Revert changes panel instead. See Revert changes.
Removed and deleted resources
When a resource has been removed from the remote integration, it appears with Action: Removed (or Action: Deleted for flows). Completing the merge removes the reference to that resource from the current integration's flows. It doesn't delete the resource from your account, so exports, imports, and scripts that other integrations use keep working. Always check the References list before completing a merge that includes deletions.
Mixed actions in one pull
A single pull can include resources with different action labels simultaneously. Each resource is listed independently with its own action label. Review each resource row before merging to confirm the full set of changes is expected.
Review API changes
When a pull or revert diff includes API changes, an APIs group appears in the Review changes panel. Each API entry shows field-level diffs — individual fields are highlighted as added, updated, or removed, rather than showing the entire API as a delete-and-add pair.
Note: If a pull or revert would introduce a route, method, and version combination that already exists in the destination integration, integrator.io automatically increments the API version (for example, v1 becomes v1.1) to avoid a conflict.
Note: When you pull between environments, the panel can show an API version change even if no API changes were made; see API version difference blocks a pull.
Scripts
Scripts behave differently from other resources in the Review changes panel because they are commonly shared across multiple integrations and flows.
- Removing a script from a flow removes the reference to that script from the flow — it does not delete the script from your account.
- Modifying a script in one integration modifies it in every integration and flow that uses it. Check the References list before merging any script changes.
- When a script is both modified and removed in the same pull, the panel shows the deletion highlighted separately from the modification. The script is removed from the flow but not from your account.
Notes and constraints
- Lookup cache data is not managed by ILM. Lookup cache references appear in Review changes, but cache data doesn't; see Lookup caches.
- Topic messages aren't managed by ILM. Topic configuration changes appear in Review changes, but retained messages don't; see Topics.
-
Flow diffs use JSON names for flow steps. In a flow's JSON diff, exports appear under
pageGeneratorsand imports underpageProcessors.