n8n Form Trigger: Respond When and a long Sume video job

Set the n8n Form Trigger's Respond When option to Form Is Submitted when the form starts a Sume video job, and deliver the video afterwards by email, a second form page, or a message. The other choice, Workflow Finishes, keeps the submitter's response pending until the whole workflow ends, and a Sume video, avatar-video or face-swap job often runs longer than the 30 seconds a Sume sync wait can hold.

The n8n side below is from the Form trigger docs (read 2026-10-02); the Sume side is from Jobs and results.

What does Respond When change?

n8n describes two settings. Form Is Submitted sends the user a response as soon as they submit. Workflow Finishes waits for the workflow to complete first, and if the workflow errors it tells the user there was a problem submitting the form.

Why not wait for the video inside the form?

Sume's docs state that the 30-second wait_timeout_seconds cap bounds how long the HTTP request blocks, not how long the job takes, and that video, avatar-video and face-swap jobs routinely do not finish inside it. A 2xx on submit means the job exists and paid work is in flight; it does not mean the video is ready. Holding a browser on the form page for that duration ties the user's experience to a workflow run, and a failure at the end shows up as a form error even though the paid job may still complete.

The pattern Sume documents instead is: submit with async, keep the job id, then either poll GET /v1/jobs/{id}/status until terminal is true or take a webhook-mode callback. n8n's Wait node and a second webhook workflow handle that part; see the Wait node post.

How do I pass campaign details into the form?

The Form Trigger supports Hidden Field elements, and n8n says you can set their values with query parameters on the production URL. The docs note that query parameters only work in production mode, not in test mode, and that special characters in names or values must be percent-encoded. A link such as .../form/my-form?campaign=spring can therefore carry a campaign id into the workflow without showing it on the page.

Who should be allowed to submit?

The trigger's Authentication setting offers Basic Auth, n8n User Auth, or None. With n8n User Auth, only users signed in to that n8n instance can load or submit the form, and unauthenticated submissions get a 401. Each submission on this workflow can start a paid Sume generation, so pick the setting that matches who may spend credits.

Keep one more habit from Sume's docs: send an Idempotency-Key on the submit request, built from something stable in the form data, so a retry of the same submission returns the original job instead of billing a second one.