Articles in this section

ILM supported resources and limits

Integration lifecycle management (ILM) carries an integration's configuration through clones, pulls, snapshots, and reverts. It doesn't carry runtime data, credentials, or environment-specific objects. Use this article to plan a clone or pull and to check what to set up before you run flows in the integration that received the changes.

Supported integrations and resources

ILM works with any custom integration you create and any template you install. It supports integrations that contain flows, APIs, tools, and topics. It doesn't support MCP servers.

ILM supports these resources:

  • Flows
  • Exports
  • Webhooks
  • Imports
  • Scripts
  • APIs
  • Tools
  • Lookup caches
  • Topics

A pull carries every change to these resources, including resources added to the remote integration after the clone was created. The exception is any field on an ignore list. See Ignore resource fields in a pull. A clone doesn't carry the revision history of the original. The clone starts its own.

Integration apps don't have a formal backup feature. See Back up an integration with a snapshot.

Lookup caches

ILM carries lookup cache references, mappings, and transformations. It never carries the data stored in a lookup cache. After every pull, merge, or revert, repopulate or re-upload the lookup cache data before you run any flows.

Operation References, mappings, and transformations Cache data
Clone Carried. Carried only when you clone into the same environment, Include data when lookup cache is cloned or downloaded is selected on the lookup cache, and the total size of all lookup caches is under 5 MB. Otherwise the clone contains the lookup cache with no entries.
Pull and merge Carried. A lookup cache added to the remote integration after the clone is a new resource, and the pull creates an empty lookup cache. Not carried.
Snapshot Carried. Never saved in any revision.
Revert Carried. If you revert to a snapshot taken before a lookup cache was deleted, ILM creates an empty lookup cache. Not carried.

In the same environment, you can reuse an existing lookup cache instead of cloning it.

When an operation introduces a new lookup cache, validate the lookup cache manually in the integration where it was introduced before you run any flows.

Topics

ILM carries a topic's configuration (name, description, and retention). It never carries retained messages or cursors. A cursor is the position where a subscription resumes reading. Topic configuration changes appear in the Review changes panel during a pull or revert. Retained messages don't.

  • Same environment — A clone reuses the topic that the original step points to. It never creates a second topic. To publish to a separate topic, open the cloned step and create a topic from the topic picker.
  • Different environment — The first clone or pull into an environment creates the topic there and registers it to the integration. Publish steps and subscriptions (Listen for messages from a topic steps) point to it with no further setup. Later pulls reuse that topic and apply configuration changes.
  • Topic limit — A pull, or a clone into a different environment, fails before it applies any changes if creating its topics would put the target account over its topic limit. The default limit is 20. Topics that already exist in the target environment don't count toward the limit. To fix a failure, see Troubleshoot ILM revision and pull issues.
  • Snapshot and revert — A snapshot includes topic configuration. A revert restores it but doesn't restore messages or change where a subscription resumes. If a step's topic no longer exists, the revert fails.
  • Retained messages and cursors — Subscriptions in a clone start with no cursor, and Start from is set to its default. To process messages already in the topic, set Start from to All retained messages before you turn the flow on for the first time. You can also replay messages afterward.

Connections

ILM doesn't copy connections. You set them up in these places:

  • Clone, same environment — integrator.io preselects the connection used in the original flows. Confirm or change each connection when you configure the clone.
  • Clone, different environment — Select an existing connection in the target environment, or create one.
  • Pull and revert — Each connection that needs setup appears as a step before the operation runs. See Pull changes between integrations and Revert changes.

Set up a separate connection in the clone for each connection in the original integration. Don't reuse one connection for more than one original connection. If two original connections share one connection in the clone and the original integration later removes one of them, a pull from the original fails at merge. To fix a failed merge, see Troubleshoot ILM revision and pull issues.

Webhook credentials

ILM doesn't carry the credentials of a webhook that uses authentication. The first time you create a pull or revert for an integration that contains one, open the webhook and enter the credential for its verification type. You don't need to enter it again unless it changes.

Verification type Credential to enter
Basic Password
HMAC Key (secret)
Secret URL Custom URL token
Token Token
Key (secret) Key (secret)