<aside>
In the following example, we will be sending customer data to Seen for video generation, and receiving a unique video player link and personalised email thumbnail back to Bloomreach Engagement for distribution. This example uses a Webhook action node in a Bloomreach Scenario to send data to Seen, and an Omniconnect Transformation to receive the result back and write it to the customer record — ready to use across email, SMS, and in-app campaigns. No third-party middleware is required.
If you have multiple video campaigns with Seen, repeat the process to connect Bloomreach with each one.
You can reach out to your Customer Success Manager at Seen for assistance.
A Project needs to be created and published in the Seen Platform prior to setting up the integration.
</aside>
In Bloomreach Engagement, navigate to Data & Assets → Integrations → + Add new integration, select HTTP Authentication, and configure it as follows:
https://next.seen.io/AuthorizationBearer {your Seen API token}secret<aside>
You can create an API token in your Seen Platform workspace under Settings → API.
</aside>
Navigate to Campaigns → Scenarios → + New scenario and add a Webhook action node. Configure it as follows:
https://next.seen.io/v1/projects/{PROJECT_ID}/data<aside>
You can find your Project endpoint in the Run tab of your Seen Platform Project.
</aside>
POSTJSON {
"id": "{{ customer_ids.registered | default(customer_ids.cookie) }}",
"first_name": "{{ customer.first_name | default('') }}",
"last_name": "{{ customer.last_name | default('') }}"
}
<aside>
Remember to modify the payload to match the variables used in your Seen Project. All fields must match property names defined in your Seen Project.
</aside>
201 Created and triggers video generation in Seen.Seen Callback. Copy the generated Omniconnect URL — this is the callback target you will configure in Seen.POSTapplication/json{{ }} placeholders with the dynamic output references available in the Seen webhook editor: