Note
The Lookup caches feature is only available to Professional and Enterprise plan users. You can request an upgrade by reaching out to your Celigo account manager.
A lookup cache is a resource that stores info in the Celigo platform (integrator.io) for quick access in lookups. All lookup caches registered within an integration are shown under the Lookup caches tab.
If you've created a lookup cache from within an integration it is automatically registered with that integration; however, if you haven't, then you should register it. When you register a lookup cache with an integration,
-
it's easy for users to find and manage it.
-
It's easy for users with custom permissions to an integration to access and view or use it, rather than when it's outside the integration. Only account owners, administrators, or users with manage all permissions can access all lookup caches in an account.
-
it preserves linkage history for cloning/Integration Lifecycle Management (ILM), without accidentally breaking active flows.
-
It becomes automatically available to any script, flow step, or tools under that integration. No additional manual linking is required when mapping or scripting.
-
It automatically generates an alias ID or you can create a meaningful alias enabling its immediate use.
If multiple exports and imports across integrations use a given lookup cache, any registered lookup cache will give access to the exports and imports referencing that lookup cache. This means that a user with access to integration A can get access to individual exports and imports used in integration B and C, if exports and imports within integration B and C use/reference a lookup cache that has been registered with integration A.
Note
Lookup cache registration is applicable to flows in an integration. This feature does not apply to integration apps and standalone flows (those not attached to an integration). To attach a standalone flow to an integration, open the integration, navigate to the Flows tab, and click Attach flow.
You can register lookup caches created outside an integration:
-
From the Home page, select an integration.
-
In the page that opens, click Lookup caches.
-
In the top right corner of the Lookup caches tab, click Register lookup caches. The Register lookup caches window opens.
-
Check the box next to the lookup cache that you want to register with the integration, then click Register. The newly registered lookup caches are listed on the integration’s Lookup caches tab, and are now available to use in any flow within the integration.
Any user with access to the integration can use these lookup caches in flows within this integration. Or, based on their permissions they can reference them in other integrations.
Any lookup cache that is created within an integration is automatically registered with the integration, and available to use in any of its flows.
When you create a flow in an integration and select lookup caches for tools, then the selected lookup caches are automatically registered with the integration while saving the flow,
A lookup that is registered with an integration becomes available to all users with access to the integration.
-
Open an integration and click the Lookup caches tab.
-
Click the Actions overflow (...) menu for that lookup cache and select Deregister lookup cache.
You can reference lookup caches more reliably using aliases, instead of internal IDs. Like connections and other resources, assign meaningful aliases to lookup caches in integrations, making references easier to read, maintain, or use across environments. When a lookup cache is registered, whether manually or automatically, integrator.io generates a meaningful alias ID for it so you can start using it immediately. You can update the alias later if required.
-
Use lookup cache aliases in scripts
-
Use lookup cache aliases in integration lifecycle management operations such as clone, snapshot, revert, pull, or merge, so references remain stable when integrations move between environments.
For more information on aliases, see Create and manage aliases to reference resources.