A training editor has three onboarding videos due on Friday. Three notifications that say “video ready” leave her with a sorting job. A useful handoff carries the brief, video link, reviewer and exact question together: “Does the role picker match the release?”
Save the job beside its brief
Install the verified ngram node for n8n, choose the ngram credential, and test with a sample review record your team controls. Create an ngram API key for the credential. Creating videos through the API requires a paid plan and enough credits for the selected model. Start the video from the approved brief. Write the returned job ID into that record before waiting for the result.
Split completion from failure
Use the terminal trigger for video.completed or video.failed. Configure a separate branch for each outcome. On completion, match the job ID to the source and use Get Status to retrieve or confirm the playable result. On failure, save the reason and alert the workflow owner. Don’t mark the record ready for editorial review.
The sample follows one onboarding brief. If your instance cannot accept incoming webhooks, poll the same job with Get Status at a bounded interval. Stop polling when it reaches a terminal state. An event that arrives twice should update one record, not send two review invitations.
Give the editor an action
Use the destination node for the tracker your editor already uses. Map the video URL, source brief, assigned editor and review question. Set the record to Ready for review only after the link exists. An editor can then open it with their normal account and mark the content approved or request a change. Access to the tracking record alone does not guarantee access to the video.
Test the handoff before turning it on
Use one successful test, one failed job and a repeat of the same completion event. Check that the editor sees one actionable record on success and none on failure. If the team only makes an occasional video, a manual handoff using the sharing guide is often easier to maintain.
