Activepieces wait for webhook: resume URL as Sume webhook_url

Yes, you can use the resume URL of an Activepieces WEBHOOK waitpoint as the webhook_url of a Sume job. The paused run resumes when Sume POSTs its terminal event (job.completed, job.failed or job.canceled), and the event body is available to the next step. Keep status polling as the backup the Sume docs require.

Waitpoint facts are from the Activepieces architecture page and limits page; Sume facts from Webhooks, read 2026-09-30.

What does a WEBHOOK waitpoint do?

Per the waitpoints page, a WEBHOOK waitpoint resumes on any HTTP call to its resume URL, and the call's { body, headers, queryParams } is surfaced to the piece as ctx.resumePayload. Since 0.88.0 (2026-08-12) any waitpoint can carry a deadline. The limits page puts the paused flow lifetime at 30 days on Cloud.

What will Sume send, and how often?

Sume sends terminal job events only, one POST per outcome, and no progress deliveries. The URL must be public HTTPS. Non-2xx responses and network errors are retried.

Can the resume URL verify Sume's signature?

Not by itself. Sume signs the raw JSON body with HMAC SHA 256 over <timestamp>.<raw_body> and sends x-sume-webhook-timestamp and x-sume-webhook-signature. A bare resume URL accepts any call, so anyone who learns the URL could resume your run. The waitpoint payload includes headers, so verify the signature in a following step before trusting the result, and fetch the job with the saved id if it fails.

What if the callback never arrives?

Ten refused attempts leave a failed delivery and a job that still reached its real terminal state. Set a waitpoint deadline shorter than the 30 day lifetime, and on timeout read status_url rather than resubmitting. You can also redeliver the real terminal event with POST /v1/jobs/{job_id}/webhook/redeliver.