- Use chat for unresolved creative choices.
- Use automation for a predictable trigger and stable inputs.
- Keep review and failure handling in the workflow.
A marketing team has two requests on Monday. One is a launch video whose presenter and pacing are undecided. The other is an onboarding clip for each approved customer handoff. Both need a video. Only the second has a useful trigger.
Choose chat when the brief changes as you work
In the first request, someone must decide which presenter fits the brand, how long the story should run and what the final frame should say. Use ngram’s MCP integration to review those choices while the brief stays in the conversation.
The illustrated Claude example follows one Tidepath launch brief. The marketer chooses a presenter and caption style, checks the quote, approves the plan and reviews the preview. That discussion is valuable because the next decision depends on what the person just saw.
Choose an event when the fields already tell the story
For the onboarding request, define the trigger as “handoff approved.” Require the customer-facing task, a source page and the account owner. Send those fields to a create action once. Keep the returned video ID with the record. Route a completed result to the owner and a failed result to the person responsible for the workflow.
The illustrated Sheets workflow below shows how a row could supply a brief. It is a design example. Run your own test row before enabling the automation.
Zapier suits a team that already keeps the approval trigger and follow-up there. n8n is useful when the team needs conditional routing or operates its own workflow. Neither connector removes the need to review what gets sent to the customer.
Decide where a person belongs
A stable trigger can still produce a bad draft if the input is incomplete. Send a missing source back to the request owner before creation. If a customer-specific detail changes how the story should be told, pause at the brief and use chat for that decision. After creation, check the output before distribution.
For the next request, ask what would have to change in a working automation. If the answer is “only these three fields,” reuse it. If the answer is “the audience, story and evidence,” a conversation is likely the shorter path.
You just read it. Now watch it.
ngram turns this post into a short explainer video: scenes, voiceover, and motion graphics included.






