AI creation with a reusable foundation
Start with a story, develop visual scenes, work with script and voice, and apply branding. A reusable template carries that creative direction into audience-specific campaigns rather than starting each customer moment from an empty page.
Personalization connects recipient attributes and audience rules to scene or voice variations, dynamic script values and scene inclusion. Read the audience personalization guide for the controls and default behavior.
Automation within the workflow
Repeatable workflows connect template selection, recipient preparation, supported generation operations and campaign schedules. Keep readiness checks, permissions and any required approvals explicit when automation advances a step.
Automation does not remove the need to prepare media, confirm eligible recipients or configure delivery. Available operations depend on the release and workspace; the public API contract is the authority for a particular integration.
Integrated delivery, with recipient-level outcomes
Bring audiences, eligibility, batches and schedules into the campaign workspace. Use the channels configured for the workspace and inspect delivery outcomes for the recipients involved.
Generation and delivery are different milestones. A video can be rendered without a message being sent; an accepted send is different from a confirmed delivery. Keep those states distinct when building a customer journey or reporting its results.
to a delivery outcome.
- Creative readyGenerated output
- Campaign readyEligibility + schedule
- Delivery stateRecipient outcome
API, MCP and webhooks: three ways to connect
- REST API
- Let your application call documented operations with authorized workspace access. Discover capabilities, work with supported templates and campaigns, and inspect jobs or results.
- MCP
- Connect a compatible AI assistant to permitted workspace operations. The public Streamable HTTP endpoint is
https://engage.shuffll.com/mcp. - Export webhooks
- Notify your endpoint when an export event happens. Configure event types and map the payload into the format your downstream workflow expects.
Application → REST API → Engage workflow
AI assistant → MCP → Authorized operations
Export event → Webhook → Your next systemExport events that can drive the next step
The export webhook configuration supports three selectable event types. Organization defaults can be overridden for an individual order, and payload mapping selects the event and recipient fields to send.
recipient_exported- A recipient’s personalized video export completes and result URLs arrive.
recipient_failed- A recipient’s render fails.
all_exported- The order reaches its all-recipients-exported milestone.
These are export notifications, not proof that a viewer received or watched the video. Match event handling to your business workflow and keep delivery or engagement reporting separate. Confirm endpoint configuration and enabled events for the rollout.
QUESTIONS, WITH CONTEXT
Go one question deeper.
Explore the details that matter for this part of the workflow.
The connected platform
How the creative and operational pieces belong together.
Why describe Engage as a one-stop shop?
The workspace connects creative development, audience-specific variations, campaign preparation and configured delivery. REST API, MCP and export webhooks connect supported parts of that process to surrounding systems. The exact available steps depend on the workspace and release.
Where does AI creation fit into the campaign?
It helps build the creative foundation: scenes, scripts, media and voice. Audience rules can then select appropriate variations in the workspace. Review the creative and default versions before using them in the campaign.
What can remain reusable between campaigns?
Creative templates, brand direction and a planned rule structure can provide a repeatable foundation. Recheck the recipient data, media readiness, eligibility and configured delivery for each run instead of assuming a previous campaign’s setup fits every new audience.
Connecting the next system
Choose an interface for the role it plays.
How do REST, MCP and webhooks differ?
REST lets an application call supported operations. MCP makes permitted operations available to a compatible assistant. Workspace export webhooks notify a configured receiver about export milestones. They complement each other but do not imply identical configuration or release coverage.
Does every workspace feature have a public API operation?
No. The documented API V1 is narrower than the workspace. It covers a fixed-video campaign workflow and excludes video personalization, full creative authoring and message sending. Build against the published operation contract.
Does a completed video mean the customer received it?
No. Export completion, message sending, confirmed delivery and viewer response are distinct milestones. Inspect the relevant records in the configured workflow before attributing a delivery or campaign outcome.
This guide describes workspace capabilities and documented implementations. Availability depends on deployment, workspace configuration and the integration contract. Confirm the required features for your rollout with Shuffll.
Public API + MCP documentation ↗