Articles in this section

Pull changes between integrations

A pull moves tested changes from one integration into a directly related clone, for example from a development integration into production. Use a pull to promote changes through your environments, keep clones in sync, or bring changes made in one clone into another. A pull has three stages: create the pull, review the changes, and merge.

Prerequisites:

  • You have Manage access to the integration in both environments, or you're an account owner or administrator. See Manage user roles & permissions to an account.
  • The two integrations are directly related. You can pull only between an original and its clone. You can't pull across two separately created clones. A clone installed from a ZIP file isn't linked to its original, so you can't pull between them.
  • Only one of the two integrations has changed since the last pull. If you change both, the next pull between them can succeed, but any pull after it fails at merge. Between pulls, change only the original or only the clone.
  • No other revision is in progress. You can run only one revision operation at a time. See Work with revisions.

To create a clone, see Clone an integration for Integration Lifecycle Management (ILM). For what a pull carries, see ILM supported resources and limits.

Direct relationships

If you clone Original to create A, clone A to create B, and clone B to create C, you can pull between Original and A, A and B, or B and C. You can't pull between Original and B, or between Original and C.

Pull relationships between an original integration and its clones.

To plan pulls across development, QA, and production, see Developing with integration lifecycle management.

Create a pull

  1. If your account has more than one environment, select an environment at the top of the page.
  2. Go to Home home-icon.png. Open the integration that receives the changes. This is your current integration.
  3. Go to Revisions, and then select Create pull.
  4. In the Create pull panel, enter the required settings:
    • Description — Enter a description for the pull.
    • Environment — Select the environment that contains the integration you pull from.
    • Integration — Select the integration you pull from. This is your remote integration. The list shows only integrations directly related to the current integration.
  5. Select Next.

If the integration contains an API and you pull across environments, first add version to the ignore list. See Ignore resource fields in a pull.

If the integration contains a webhook that uses authentication, enter its credential the first time. See ILM supported resources and limits.

Review changes

The Review changes panel lists every resource the pull affects, grouped by type. Each resource shows an Action label and a diff of the Before pull and After pull versions.

  1. Check the conflict count at the top of the panel. If it doesn't show 0 conflicts, resolve the conflicts before you continue. See Resolve conflicts.
  2. Expand each resource to see the fields that changed, and confirm every change is expected.
  3. To include changes you made after you created the pull, select before you merge.

If a resource you expect as Update appears as Removed and New, don't continue. This isn't a conflict you can resolve. See Troubleshoot ILM revision and pull issues.

For what each panel feature and action label means, see Review changes within a pull or revert.

Resolve conflicts

A conflict occurs when the same resource has changed in both the current and remote integration since the last pull. You can't continue to the merge until the conflict count shows 0 conflicts.

Conflicts have these causes:

  • Mismatched resource names — You renamed an export, import, flow, or script in one integration but not the other. For example, "Get Amazon sales" in one and "Get sales from Amazon" in the other.
  • Conflicting hook edits — You edited the same line of the same hook in both integrations.
  • A resource removed in one integration and replaced in the other — For example, the remote integration removed an import, and the current integration replaced it. See Troubleshoot ILM revision and pull issues.

You can't resolve conflicts in the Review changes panel. Edit one of the two integrations so the conflicting field matches the other, and then return to the pull.

  1. Note the resource and field that cause the conflict.
  2. Decide which version is correct, the current integration or the remote integration.
  3. Open the integration that needs to change, and edit the conflicting field to match the other integration. For a hook conflict, update the hook in one integration to match the other.
  4. Return to the pull, and select next to the conflict count.

The count returns to 0 conflicts when the fields match. If the conflict still appears, confirm you saved the edit, and refresh again.

Merge changes

Merging is the final step of a pull. It applies the reviewed changes from the remote integration to the current integration. In ILM, a merge completes a pull. It isn't the create-or-update behavior of an import.

  1. In the Review changes panel, confirm every change is correct and the panel shows 0 conflicts.
  2. Select Next. The Merge changes panel opens and lists numbered steps.
  3. If the pull includes an installation bundle, such as a NetSuite bundle or a Salesforce package, complete the steps to install it.
  4. For each new connection step, select Configure, and set up the connection. A new import that uses a new connection adds a connection step.
  5. On the final step, select Merge. Merge stays unavailable until you complete every earlier step.

The pull appears in the revisions list with a Completed status.

Resume, cancel, or pause a merge

Use the Actions menu on the pull row in Revisions. It works whether or not the Merge changes panel is open.

  • Resume a merge — Select Actions elipses-button.png on the pull row, and then select Resume operation. Use this to retry a merge that failed, including a failure while adding resources or configuring a bundle, or to continue a merge you paused.
  • Cancel a merge — Select Actions elipses-button.png on the in-progress pull row, and then select Cancel revision. The canceled pull stays in the revisions list with a Canceled status. If you cancel after a connection was added, integrator.io doesn't delete the connection.
  • Pause a merge — Close the Merge changes panel. Closing the panel doesn't cancel the merge. The pull stays In progress until you resume or cancel it.

To roll back a completed pull, see Revert changes.