Demonstrate an integration without skipping the handoff

Record the connected accounts, permissions, enabled integration and any manual setup before the demonstrated action. Distinguish configuration from routine use. A preconnected account may be a reasonable starting point, but it must not be presented as a connection that requires no setup.

This guide concerns a workflow in the reader’s software. It does not assert that Animro connects to either tool, imports their data or executes the integration. The demonstration uses supplied assets and verified behavior.

The fictional example transfers a sample request from Tool A to Tool B. It is a planning model, not a supported integration claim. Use a harmless sample object and avoid live credentials in the captured configuration.

• Source: request A-104; title “Sample label review”; requester “Example coordinator.” Capture the actual source fields.
• Mapping: source title becomes destination task name. Requester becomes the destination request-contact field only if that mapping exists; do not guess a similarly named field.
• Trigger: the user chooses the verified Send action, or the documented configured event occurs. Identify whether the trigger is manual or automatic.
• Transfer: show actual queued, failed or completed feedback. Shortened waiting requires an explicit editing cue.
• Destination: inspect B-208 and compare its name and request-contact value with A-104. Include the source reference if the product creates one.

A single well-explained field often communicates the handoff better than a wall of mappings. Keep required hidden mappings in the prerequisite note and show any transformation that affects the selected value. For example, joining first and last name is different from copying a single full-name field.

If the destination changes a value, explain the verified rule or mark it as unresolved. Do not silently replace the screenshot with a cleaner match. The film should help the viewer understand the real boundary between systems.

A “Sent” toast proves only the state that the actual product defines. Inspect the destination when the promise is successful transfer. If destination access is unavailable, bound the claim to submission and say what remains unverified.

For training, add the supported retry path and how duplicates are handled, using current product documentation. For an introductory film, state any important manual step and reserve recovery detail for a separate resource. Never turn one successful sample into a reliability guarantee.