From customer event to video moment: build the handoff.

Choose a customer moment, not another calendar slot

A useful video workflow starts with a meaningful event: a booking confirmation, a new account, an approaching milestone or a period of inactivity. The event explains why the message should exist.

Document the source system, the permitted audience and the next step before choosing the creative. Your CRM, booking system or application remains the source of customer context; Engage adds a creative and video-production layer.

Make the integration handoff explicit

Your application or automation maps customer context to a supported workflow. REST is a programmatic interface; MCP gives a compatible assistant access to authorized operations. Neither label establishes that every workspace action is available in a given API release.

• Receive the event and check that the recipient belongs in the journey.
• Select the configured template, creative version and required recipient data.
• Invoke the operations supported by the chosen interface.
• Read the generation result or handle a documented workspace export event.
• Pass usable output to the configured messaging or application experience.

Keep output, sending and delivery as separate states

A video result can exist before a message has been sent. A provider accepting a message is different from confirmed delivery, and delivery is different from a person watching the video. Preserve these distinctions in the workflow and reporting.

The documented fixed-video API V1 manages supported campaigns, recipients, jobs and results. It does not send campaign messages or manage customer webhook subscriptions. Workspace export webhooks are a separate documented surface.

Let export notifications describe export outcomes

The workspace export contract includes recipient_exported, recipient_failed and all_exported. Use the webhook guide for the available payload, mapping and endpoint configuration. These events describe video export; they do not establish email delivery or viewer engagement.

For an application integration, define how repeated notifications and downstream failures will be handled. Keep your own record of the stage that completed before requesting a retry. The integration should make failures inspectable, rather than counting every request as a customer exposure.

Run a small, observable journey first

Start with representative test recipients, including missing values and an ineligible case. Confirm the prepared output, permissions, timing and channel behavior.

Then agree on a baseline, conversion definition and observation window. A useful pilot answers a specific business question; it does not need an invented conversion promise. Expand only after the entire handoff is understood.