n8n 2.43.0: resume agents after waiting workflows, with Sume runs
n8n 2.43.0 (pre-release, Oct 6) resumes Preview agents after waiting workflows finish. Pair a long Sume run with one webhook, deduped on request_id.

n8n 2.43.0, listed as a pre-release dated October 6, 2026, includes "Resume Preview agents after waiting workflows finish". If your agent waits on a Sume run that takes minutes, give the Sume request a communication.webhook_url pointing at an n8n webhook and let the run call you back. You get one signed POST per run, so there is no polling loop to keep alive.
What I can and cannot say about n8n
The release notes give one line about this feature. I did not read node-level docs for it, so I am not describing how the resume is configured. Everything below is about the Sume side of the wait.
What Sume sends
A Format run, a scheduled run and an Agent Completion each deliver one terminal event after a run completes or fails: format.run.terminal, action.run.terminal or agent.run.terminal. A run is one agent turn, so the event fires once even when the turn made many clips. The URL must be public HTTPS, and Sume does not follow redirects, so register the final URL.
Handler rules for the n8n side
Use the envelope request_id (equal to run_id) as the dedupe key, since it is stable across retries. Branch on outcome, which is ok, degraded or error, not just on status. A canceled run sends no webhook at all, so if your workflow can cancel, poll status_url afterwards instead of waiting.
Keep a poll as a backup. status_url and result_url stay valid whether or not you use the webhook.
| Run result | Webhook sent | What the workflow should do |
|---|---|---|
| completed, schema satisfied | Yes, outcome ok | Continue with output |
| completed, output not projected | Yes, outcome degraded | Review artifacts and output_error |
| failed | Yes, outcome error | Retry or alert |
| canceled | No | Poll status_url |
Sources
Related posts
More in Integrations
- OpenClaw still lists sora-2 as a configured video provider: fix it
OpenClaw issue 158876: the bundled OpenAI video provider still defaults to sora-2, though /v1/videos returns 404. What to do now, and a Sume video call.
- Plan in Claude Code over MCP, then hand the batch to bulk runs
Use Claude Code with Sume's hosted MCP to prototype one video and read costs, then run the real batch from your backend with Format bulk runs and a spend cap.
- Reels ad: use an existing post or upload a new video? Sume 9:16 file
Meta's Reels ads page offers native video, image ads and existing Reels posts. Which route fits an AI video from Sume, and what file to prepare for each.
- Video generation MCP connector: six questions before you connect
Before you let an agent spend money through any MCP connector, ask six questions. Here are Sume's hosted MCP answers on auth, scopes, idempotency and spend.
Written by Sume