Make Free 15-minute interval: poll or webhook for a Sume job?

Answer

Use a webhook. Make's pricing page lists a 15-minute minimum interval on Free and 1 minute on Core, so a scheduled scenario that polls a Sume job on Free checks at most four times an hour (60 divided by 15). A webhook tells you the moment the job ends, whatever the plan interval is.

I read the interval as applying to scheduled runs. Test that an instant webhook trigger fires immediately on your plan before relying on it.

Interval facts

Each module action costs 1 credit per the page, so every poll that finds nothing still spends credits.

Cost of polling vs webhook

Polling every 15 minutes for a 2 hour wait is 8 checks (120 divided by 15), each at least one module, so at least 8 credits for one job. A webhook costs the receiving modules once. Sume's docs say poll /v1/jobs/:id/status and honor next_poll_after_seconds, which is usually much shorter than 15 minutes, so a slow poll is a backup, not the primary path.

Submit with mode: "webhook" and a public HTTPS webhook_url. Sume retries delivery up to 10 times, 30 seconds apart, so a short outage will not lose the event. If the event never arrives, one scheduled status read per hour is enough to catch it.

curl https://api.sume.com/v1/jobs/$JOB_ID/status \
  -H "Authorization: Bearer $SUME_API_KEY"

Caveat

Never respond to a stalled run by creating the job again. Reuse the Idempotency-Key, as described in jobs and results.