n8n 3.0 Execute Sub-workflow drops URL and file: Sume sub-workflow

In n8n 3.0 the Execute Sub-workflow node no longer loads a sub-workflow from a Local File or a URL; the remaining sources are Database and Define Below (n8n 3.0 breaking changes, read 2026-10-02). If your Sume submit-and-wait logic lives in a JSON file or at a URL, import it as a workflow and call it from the database.

What changes

The node page still lists all four sources as of the read date; the 3.0 page is the one that says two go away. The release date is given only as October 2026.

A Sume sub-workflow that survives the upgrade

Put one thing in the sub-workflow: submit a Sume request and return the job id. Do not make it wait for the video. A Sume submit returns 202 with the job id and status_url in the default async mode, so the sub-workflow finishes in under a second.

The node's Wait for Sub-Workflow Completion option then costs nothing, and the parent can park on a Wait node resumed by a signed Sume webhook.

Steps

• Import the sub-workflow JSON through the editor, so it gets a database ID.
• In the parent, set Source to Database and choose it by ID.
• Pass the prompt and an Idempotency-Key in as input items, and return job_id.
• Keep the signature check in the parent or in the webhook receiver, not in the sub-workflow.

Where this does not help

The sub-workflow does not change how long Sume jobs take. For a list of items, a Sume bulk run queues up to 100 Format runs in one call, which is usually better than looping a sub-workflow once per item.