Before you start
Three things from MsgVibe
API key
Create one under Dashboard → API keys. It starts with mvk_live_ and is shown once.
Design ID
Open a design in the template gallery. Its ID is the last part of the studio address.
Brand kit ID
Save your logo and colours once on the Brand kits page and copy the kit's ID.
Scenario 1
Create a video
Any trigger, then one HTTP module.
- 1In Make, create a scenario and add your trigger, for example Shopify → Watch Orders, Google Sheets → Watch New Rows or HubSpot → Watch Contacts. Run it once so Make knows the fields.
- 2Add the module HTTP → Make a request and fill it in:
URL
https://api.msgvibe.com/v1/videosMethod
POST
Headers
Name
Authorization, valueBearer mvk_live_…(your API key)Body type
Raw
Content type
JSON (application/json)
Request content
The JSON below
Parse response
Yes
- 3Paste this as the request content. Replace the two IDs, then replace the sample words with fields from your trigger (click a value and pick the field from Make's panel).Request content (JSON)
{ "templateUniqueId": "YOUR_DESIGN_ID", "brandKitId": "YOUR_BRAND_KIT_ID", "aspectRatio": "9:16", "currency": "USD", "promotion": { "title": "Thank you, Sarah!", "subtitle": "Order 1042 is on its way", "offerText": "Use THANKS10 for 10% off your next order", "cta": "Shop again" }, "sharePage": { "headline": "Sarah, thank you for your order", "button": { "kind": "link", "label": "Shop again", "url": "https://yourstore.com" }, "recipient": { "name": "Sarah Lee", "email": "sarah@example.com" } }, "externalId": "order-1042" } - 4Click Run once. The answer has
video.idandstatus: queued, and 1 credit is used. Turn the scenario on.
Scenario 2
Get the finished video, views and clicks
MsgVibe calls a Make webhook when something happens.
- 1Create a second scenario with the trigger Webhooks → Custom webhook. Click Add, name it, and copy the address Make shows.
- 2In MsgVibe, open Automations → Connected hooks. Choose the event Video ready, paste the address and click Add hook.
- 3Back in Make, click Run once, then make one video with scenario 1. Make receives the event and learns its fields:What MsgVibe sends
{ "event": "video.completed", "data": { "id": "vid_1791306844787a1b2c3d4_0", "status": "done", "outputUrl": "https://www.msgvibe.com/v/0118el0bon/thank-you-sarah.mp4", "shareUrl": "https://www.msgvibe.com/w/aB3dE5fG7h1", "externalId": "order-1042", "metadata": { "name": "Sarah Lee", "email": "sarah@example.com" } } } - 4Add what should happen next, for example Gmail → Send an email to
data.metadata.emailwith the page linkdata.shareUrl, or Shopify → Update an order with a note. Turn the scenario on. - 5For sales alerts, add more hooks the same way with the events Video viewed and Button clicked. Each fires the first time a person opens their page or clicks its button.
Other ways to connect: Zapier app · n8n · Shopify thank-you video · API reference
FAQ
Questions
Is there a MsgVibe app inside Make?
Not yet. You use Make’s own HTTP and Webhooks modules, which work with any API. Set-up takes about ten minutes and you only do it once per scenario.
What does it cost?
MsgVibe uses 1 credit per video; a failed video is refunded. Make counts one operation per module run, on your Make plan.
How long does a video take?
About a minute. The HTTP module answers at once with the video id and the status queued; the finished link arrives through the Video ready hook.
Can Make run something when a lead watches the video?
Yes. Add a hook for Video viewed or Button clicked in MsgVibe Automations, pointing at a Make custom webhook. Each fires once per video page.
My scenario made the same video twice. How do I stop that?
Add an Idempotency-Key header with a value that is unique per order or lead, for example the order number. A repeat with the same key returns the first video and is not charged again.
