Who this is for: Teams explaining a data handoff between their tools.
What to prepare
- Setup requirements
- Source and target field definitions
- Transfer-state evidence
- Destination record
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
State the setup
Show a neutral setup card naming connected accounts, permissions and any manual prerequisites.
On screen:Configured sample accounts
- 02
8–17s
Inspect the source
Show A-104 with Request title: Sample label review and keep the source identity visible.
On screen:Source: Sample label review
- 03
17–28s
Map one field
Use the actual mapping control to connect Request title to Task name, preserving field labels.
On screen:Request title → Task name
- 04
28–36s
Save the mapping
Show the verified commitment action and configured state.
On screen:Mapping saved
- 05
36–45s
Trigger the transfer
Show the actual manual or configured trigger and observed pending feedback. Identify shortened waiting.
On screen:Transfer requested
- 06
45–55s
Inspect the destination
Open the supplied destination record and compare Task name with the source value.
On screen:Destination: Sample label review
- 07
55–60s
Close with scope
Hold the matching value and state the precise verified result.
On screen:One sample field verified at destination
Make it your own
- Mapping pair
- Supply exact source and destination fields, sample values and any transformation rule.
- Setup and trigger
- Identify configured accounts, required mappings and the actual manual or configured event.
- Transfer proof
- Use observed pending and destination states, narrowing the ending if arrival is unverified.
Prepare mapping evidence
Supply field definitions, required additional mappings and the real trigger. State whether the film begins after authentication or connection setup. Do not show credentials in the configuration captures.
Adapt the handoff
For a transformed value, show the rule and resulting value rather than a direct-copy arrow. A 30-second cut can begin with a saved mapping, but must state that prerequisite and still verify the destination if arrival is promised.
Review transfer claims
A saved mapping and a submitted job are not automatically proof of arrival. If destination evidence is missing, narrow the ending to the observed state. Do not infer reliability, compatibility with every field or an Animro import capability from this illustrative workflow.
Review checklist
- Prerequisites are explicit.
- The selected value is traceable through mapping.
- Arrival claims match destination evidence.