# Webhook Idempotency — Lookup Cache? **URL:** \ **Category:** Integrator.io\ **Created:** [July 8, 2025, 8:03pm UTC](https://connective.celigo.com/t/webhook-idempotency-lookup-cache/4957 "2025-07-08T20:03:21Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\ **Post date:** [July 9, 2025, 7:52pm UTC](https://connective.celigo.com/t/webhook-idempotency-lookup-cache/4957/5 "2025-07-09T19:52:13Z")
Alternatively, what system are you importing orders to? You could try using the composite API for your import and then not need to do anything with lookup cache. The composite API lets you do a lookup before making a create or update call. So you could make the lookup part of the composite API fetch against the destination system to see if it already exists there, and if so, you just ignore the record. For this, I would set the page size to 1 on the export (since the composite API does all lookups first, then does the update/create operation). You’d probably also need to set concurrency to 1 on your connection so that everything processes sequentially. If you’re going to NetSuite or Salesforce, then those have built-in "how to find existing record" options on the import configuration. ![The image is a screenshot of an "Edit Import" interface in Oracle NetSuite, showing options for updating employee records, with specific fields for import settings and operation details. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/8/85de2c85de48eccf2e5760e8e65b1e381fdc287b.png) Here is an example setup I use for Jira: ![An interface screen showing settings for importing records with HTTP method configuration, including creating new records via a POST request to an Atlassian API. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/7/75e970c53ecab70e3fe324ef84e622f213ab80ee.png) ![The image shows a user interface for editing an HTTP import, with options for creating new records and identifying existing records, and a pop-up for configuring an HTTP GET request for a resource endpoint. (Captioned by AI)](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/5/5083a5d74682bb674eaf9bed4284cc1c147cf26a.png) --- _[View the full topic](https://connective.celigo.com/t/webhook-idempotency-lookup-cache/4957)._