Datagran.io AI Ads Workflow Demo

Make a similar video

Datagran shows ad creation, metrics connections, a voice agent, follow-up and human decisions. Short copy beside screens breaks a longer automation workflow into readable steps.

Your goal: Make a roughly 50–60-second workflow demo showing where automation acts and where people decide. This work belongs to the Claude Opus 5.5 video collection. Select Claude Opus 5.5 in an AI coding tool that supports it and submit the assets and requests below in stages. The model plans, writes and edits code; the actual project handles preview/export. Voice and music need suitable tools or supplied audio.

The request specifies a business flow without publishing a framework. Validate step relationships in a shot list before choosing a production workflow.

Prepare your assets

• A workflow map, actual screens for each step and demo data.
• Trigger conditions, actions, approval points and final outcome.
• Brand assets, shareable metrics and audience language.

Put files in a directory AI can read, such as assets/, and explain each filename and purpose. Specify ratio, duration and publishing destination. If you supply only a URL, ask what content is accessible before assuming any functionality.

Replace elements for your product

Element in the sample or creator brief	Your replacement
Ad creation and attribution	Your workflow start and data sources
Voice agent and follow-up	Your automated actions
Humans decide	Your human approval point
Analytics dashboard	Your outcome screen

For sales CRM, show incoming lead, assignment, follow-up, human quote approval and summary; for hiring, show intake, screening, scheduling and human interview decisions.

Do not present an animated workflow as proof of live execution; show actual approval and exception behavior.

Start with this shot plan

This is an editorial draft, not a frame-by-frame reconstruction. Approve assets and copy for each scene, adjusting durations to the information load.

1. 0–7s: establish the user task.
2. 7–18s: create the task and connect data.
3. 18–33s: execution and follow-up.
4. 33–45s: human approval or exception handling.
5. 45–55s: result dashboard and brand.

Make it with AI in four steps

Editorial suggestion; not reproduction-tested. Fill in brackets and approve each preview before continuing. The creator’s film is not a downloadable project template.

1. Check assets and plan shots.

I am using Claude Opus 5.5 to make a video for [my product].
Goal: Make a roughly 50–60-second workflow demo showing where automation acts and where people decide.
Audience: [people]. Ratio and duration: [requirements]. Assets: [directory].
Read my product brief, identity and assets. List confirmed features and missing files.
Use the draft above to plan visuals, short headings, asset files, durations and transitions.
Do not present an animated workflow as proof of live execution; show actual approval and exception behavior.
Provide the shot list before producing the full film.

2. Make one sample. After approving the plan and file paths, send:

The shot list is approved. Preview an execution result entering a human-review card and check who acts and who decides.
Production approach: The request specifies a business flow without publishing a framework. Validate step relationships in a shot list before choosing a production workflow.
Check dependencies and assets in this environment and provide the actual preview method.
Identify missing tools, models or audio rather than presenting placeholders as finished work.
Deliver this sample preview first, then list the files needed for the full film.

3. Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:

Complete the other shots using the approved sample's visual rules.
Do not present an animated workflow as proof of live execution; show actual approval and exception behavior.
Match headings, actions and audio cues. If audio is unavailable, provide a silent preview first.
Keep product name, logo, screen assets, colors and final action in easily editable configuration.
Provide full playback and key transition stills, identifying unfinished parts.

4. Review and export. Check copy and assets on a phone, then send:

Apply the approved changes and export, retaining editable source and asset references.
Provide this project's actual export command, prerequisites and output file location.
Check final MP4 duration, ratio, text clipping and audio instead of relying only on browser preview.
Deliver a contact sheet and list remaining limitations.

Revise the film and fix problems

Name the shot and change instead of requesting vague improvements that reset approved pacing:

Replace the voice-agent scene with [my automated action], keeping human review. Track the same demo task through arrows and avoid unsupported integrations.

For a 9:16 version, recompose headings, the main subject and final action. Preview the new layout rather than cropping the sides. To shorten the film, remove secondary shots or sentences before retiming.

• The workflow feels disconnected: retain the same task label or ID across scenes.
• Metrics imply actual performance: mark demo values and remove unsupported sales figures.

Creator source and reproduction limits

The post names Opus 5.5; the page retains the request for Datagran ads, metrics, agents, follow-up, human participation and analytics without a runnable project. View the original post.

Visual descriptions come from the collected video; production details come from the stored request and post. They do not constitute testing of the current product. Shot plans, adaptations and expanded requests are editorial suggestions and have not been generated or tested. Supply your own assets and production environment when the original project is unavailable.