Zapier Functions shut down Sept 1: move media calls to Sume async

Zapier Functions stopped running on 2026-09-01. Move a media-API step to Code by Zapier and submit a Sume job async or by webhook instead of waiting on it.

4 min readSume
All posts

Zapier Functions stopped running on September 1, 2026, so any Function that called a media API now needs a new home. Zapier points to Code by Zapier, which supports JavaScript and Python. Keep the step small: submit a Sume job and store its id, then let a webhook or a later poll bring the result back.

Dates are from Zapier's deprecation article; the Sume behavior is from Jobs and results and Webhooks. Read 2026-10-01.

What did Zapier announce?

Zapier Functions timeline from its help article, read 2026-10-01.
DateEvent
2026-06-01No new users and no new functions
2026-09-01All functions stop running; the interface is inaccessible
ReplacementCode by Zapier: JavaScript or Python, npm and PyPI packages

How should the replacement step call Sume?

Submit with the default async mode. Sume returns 202 with a job envelope and polling URLs, and the job id is in that first response. Store it: the docs say to store the job id from submit responses so work survives restarts.

If you would rather have a push, send mode: "webhook" with webhook_url, pointing at a Catch Hook in another Zap. Keep status_url polling as the backup.

Why not wait for the result inside the step?

Because sync waits at most 30 seconds, and a video render can outlast that. If the job is not terminal when sync returns, poll; do not resubmit. See AI video API timeouts for the pattern.

What should the migration check?

Confirm the old Function's output field names, since downstream steps may read them. Then send an Idempotency-Key on the submit so a Zap replay does not create a second paid job; the pattern is in idempotency keys for AI video APIs.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume