Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Problem Summary:
I have a Kisi-Kenko integration where Kenko's polling trigger has access to ~1000 historical JSON objects via API. When I initially turned on the Zap, it only processes new events going forward and completely ignores all the existing historical data that the polling trigger can access.

Technical Details:

  • Integration: Kisi + Kenko (custom polling trigger)

  • Data: ~1000 JSON objects already exist in the system

  • Issue: Zap only triggers on new events, not existing data

  • Trigger Type: Polling (not webhook)

What I Expected:
The polling trigger should process all available data when first activated, including historical records.

What Actually Happened:
Only new events created after turning on the Zap are being processed. All pre-existing data is being ignored despite being accessible through the API.

What I've Tried:

  • Manually testing the trigger (shows sample data correctly)

  • Verifying the API returns historical data

  • Checking Zap configuration and field mappings

Questions:

  1. Is this Zapier's standard deduplication behavior preventing historical data processing?

  2. Are there workarounds to process existing data through a polling trigger?

  3. Should the integration partner (Kenko) implement date-based filtering in their polling trigger?

 

Any insights on how polling triggers handle historical data or suggested solutions would be greatly appreciated!

HI ​@tanisha_0810 

Zaps work while turned ON for new data going forward.

If you want to access and process existing historical data, then you would need to likely configure a different Zap that uses the app API (if available) to fetch those records and process those records.

Using app APIs in Zaps is an advanced approach.

Options for using app APIs in Zaps: 

 

If you are trying to handle an array of items, then you can use the Looping Zap app: https://zapier.com/apps/looping/integrations#help

NOTE: Looping Zap app has a MAX of 500 loop iterations.

 

You may have to explore different approaches such as downloading the data into a CSV file, then uploading to process the data.

Check out the Files by Zapier Zap app: https://zapier.com/apps/files-by-zapier/integrations#triggers-and-actions

Reply


Terms & Conditions