Update an onboarding lesson from its SOP
Follow the training owner’s request from the source mention to the row. Generate again after the approved procedure changes.
Keep the request, source and finished video together in the ngram Videos database. Use an onboarding SOP, a release brief or the content of the row itself. When the source changes, generate a replacement from that same row.
Follow the training owner’s request from the source mention to the row. Generate again after the approved procedure changes.
The Brand Kit release brief supplies the source. Add video to names the Sales enablement page where the finished video should also appear.
Read Error, share the source with ngram and retry the same row. Check the destination permission separately if the video belongs on another page.
The connected workspace uses the linked ngram account’s credits. Every Notion plan can use the connection. Notion AI credits are not required.
Open Connect Notion in ngram and select the pages it may read. Pages inside the selected pages are included. After you return to ngram, look for ngram Videos at the top of your Private section in Notion.
In Topic, name the audience and task. In Source page, type @ and select a Notion page. Leave it blank to use the row page itself. Optionally set Length in seconds, Aspect ratio or an Add video to page mention.
Generate starts the request without another confirmation. Action clears when ngram picks it up. Watch Status move from Preparing to Generating and use Progress and Notes to follow what the row is doing.
At Ready, open Video or the player at the top of the row page. If you chose Add video to, check that page too. After a source revision, set Generate again on the same row and review the replacement when ready.
Choose the workspace connection for work that returns to the same source, row or destination.
ngram reads the shared source page and accessible pages inside it. Notes identifies pages read, omitted material and adjustments to the requested length.
Action starts or stops a request. Status and Progress belong to ngram. The ngram project field opens the project after it starts, and Video contains the result when ready.
Use an @-mention in Add video to for a second destination. The video is also added at the top of the row page. When Notion cannot store the file, it can play from ngram instead.
Set a monthly credit limit on the linked workspace. Generate again after changing a source, angle, length or destination. The new version replaces the earlier video ngram added when it is ready.
Use the database when the same people maintain the source and need to review the result. For a single public page with no recurring row, paste its link into the converter.
A team changes the handoff rule. The training owner approves the revised page, regenerates the existing row and checks the instruction before telling the next cohort.
See the explainer playbookProduct marketing can use an approved release page as the source and a partner page as the destination. Keep both pages shared with ngram and review the Ready video on the partner page.
See the changelog playbookWhen the row reports an inaccessible source, add ngram to that page’s Connections and retry Generate. The team does not need to make its internal SOP public on the web.
See the help center playbookA Notion row is the request and delivery location. Open the linked ngram project when you need more control over the video itself.
Use visuals to explain a relationship described in the source.
Explore featureCheck the pronunciation of names and procedural terms in the resulting project.
See featureUse the approved SOP or release page to review the script.
See featureRevise the footage when the finished lesson skips a necessary step.
See featureExplain a change that benefits from a labeled diagram.
See featureCheck captions for instructions readers need to recognize.
See featureReview the project’s visual identity when a release video is customer facing.
See featurePrepare another language version for a different learner audience.
See featureA URL or pasted passage can be enough for one video. Choose the connected Notion workflow when the job needs shared pages, row status and delivery back into the workspace.
Use these Studio tools after reviewing the row result. They are separate from the Action menu in Notion.
Give the row to someone who understands the source, can check access and can review the finished video before sharing it with the intended audience.
Explain an approved technical page to an audience that needs the change in plain language.
Keep a release brief and its reviewed video in one workspace record.
Refresh a customer onboarding lesson when its procedure changes.
Choose the integration based on where the approved source lives and where you want the result to appear.
Use GitHub when the evidence belongs to a pull request, issue or release in the repository.
Explore the GitHub AppUse a Zap when an event in another application needs to start and route the video request.
Explore ZapierCreate from a conversation when someone still needs to discuss the brief and review creative choices.
Explore MCPStart from the public page already open in the browser for a one-off brief.
Explore the Chrome extensionNotion connection Workspace row | Notion converter One public page | MCP Chat request | Zapier App event | |
|---|---|---|---|---|
| Start | Action → Generate | Paste a public URL or text | Ask the assistant | Run the approved trigger |
| Source | Shared page or row content | Single page or pasted material | Source supplied to the client | Fields mapped from the trigger |
| Result | Video and status in the row | Project in ngram | Project returned to chat | Configured next step |
| Update | Generate again on the same row | Review or revise the project | Request a revision | Start another approved run |
FAQ
Still curious? See integrations and automation
Choose the pages ngram may read, then open the example row in ngram Videos and give it one audience and task.