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:
-
Is this Zapier's standard deduplication behavior preventing historical data processing?
-
Are there workarounds to process existing data through a polling trigger?
-
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!
