I've just tried a Lookup Cache for the first time and thought I'd share a bit of feedback and why I'm not using them. I read all the help documents so I feel like I have a good sense of what is possible, but I could have missed something. They are account wide, all Integrations. This can be good o…

Hi Steve, Thank you for trying out Lookup Cache and for sharing your feedback—it’s really valuable. Here are some updates based on your points: Scoping Lookup Caches: We recognise the need for scoping Lookup Caches to specific integrations rather than making them account-wide. This capability is…

@priyankakoundal - I am still getting familiar with the lookup cache, but curious what the advantages are to using the lookup cache vs static mapping when there are only a "few" mappings? I guess I always thought the "bang for the buck" for lookup cache was when I had a multitude of mappings that ne…

That would for sure be one use case. What I would also use it for is to save API calls for certain data. For example, I would create a lookup cache of all my items so that I can reduce API calls by avoiding always having to do a dynamic mapping for items. I probably would do the same thing for custo…

I'm still learning this as well. Are we now able to basically replicate the lookup step within the lookup cache feature as if we were building the lookup step within the flow like normal or is that what is coming in March?

@chrishuovinen - Its available now, but as Steve mentioned it requires you to load a CSV. I think the enhancement that is coming is where you can do the mappings in the UI (for example if you only have a few mappings) rather than always needing to load the CSV.

It depends on what use case you're trying to solve. In my example of using it for items, what I would do is make a flow that pulls items from your master item system (NetSuite or PIM or something else), then upsert those items into a lookup cache you've made. I would then schedule that flow to run o…

In my case it's reduction of duplicate static maps. We map the same few values in 4 or 5 flows (NetSuite Location to 3PL Warehouse). defining in this in one place is a perfect use of a Lookup Cache.

Hi @priyankakoundal , Great response, I'm glad my concerns are already on the radar and will keep an eye out for subsequent updates.

@tylerlamparter are there any plans to natively support fail-over to a full dynamic lookup when the cache fails to yield a result? It would be powerful to hit the cache for a lookup and in the event there isn't a match, automatically continue with a dynamic lookup and automatically add the result of…

That would definitely be nice, and I'm not sure if @priyankakoundal has it on her radar yet. You could do this by having individual lookup steps and then branching the flow off to make a different lookup when the first lookup against the cache yields no results. Individual lookup steps can get cumbe…

Lookup Cache - Hmmm

Integrator.io

tylerlamparter (Tyler Lamparter) November 7, 2025, 4:42am 19

Replied on the main thread

Topic		Replies	Views
Optimizing Flow Performance: Replacing Per-Record Lookups with Lookup Cache Integrator.io lookup-cache	2	83	January 6, 2026
Are Lookup Caches not supported by ILM? (Update: No, they aren't) Integrator.io lookup-cache	6	185	March 17, 2025
How to use a Lookup Cache for large dataset mappings Integrator.io builders-hub , lookup-cache	0	99	February 28, 2025
Webhook Idempotency — Lookup Cache? Integrator.io	9	160	July 10, 2025
Programmatic Access to Lookup Caches Integrator.io javascript , lookup-cache	6	213	August 7, 2025

Lookup Cache - Hmmm

Related topics