Should I poll or use a webhook to pick up changes?
Polling asks every X minutes if anything is new, a webhook pushes the change into your flow. Webhook is almost always faster and cheaper, but not every source offers it.
Try this first
- 1Check first whether the source API offers webhooks. If yes, pick it. Latency is seconds instead of minutes and you pay no quota for empty checks.
- 2Polling can make sense when the source has no webhook or when you are throttled on pushes. Don't set the poll interval lower than needed, every run is a task.
- 3When polling, store a cursor (last-seen id or timestamp) so you only fetch new records and don't trigger 1000 duplicates.
- 4Webhook flows need an endpoint that is always live. Plan a fallback poll once per hour to catch missed webhooks.
- 5Do the math in tasks or operations: 1 webhook a day is near free, polling every minute is 43,200 runs per month.
When to bring us in
Unsure whether webhook plus fallback poll fits your SLA, we can set up the pattern for you.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.