-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Sync API for triggers #7
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
Using the Sync API instead of webhooks can prevent flooding Zapier in projects with lots of changes. https://help.zapier.com/hc/en-us/articles/8496181445261#webhook-throttling-0-3
Proposed solution
Analyze if using the Sync API instead (or along with) webhooks is useful.
Additional context
After a quick look, it seems to use the Sync API (in its current shape) requires Zapier storage. That might lead to a clumsy and complicated usage.
Furthermore, the trigger type would change to 'polling' from 'hook'. That might lead to possible delays in processing changes (depending on the user's Zapier plan), but prevents flooding (as mentioned above), because Zapier would poll with an appropriate interval (depending on the user's Zapier plan).
The text was updated successfully, but these errors were encountered: