What it can do
- Publish or schedule videos, photos and text from any Make scenario – after a form entry, a new file in Dropbox or Google Drive, or on a schedule.
- Receive results with Make's "Custom webhook" trigger: one event per platform with the post URL or the error.
- Keep Upload-Post scenarios: change the URL and the key, leave the rest as it is.
Honest note: we do not have our own app in Make's directory. The HTTP module "Make a request" covers every endpoint of our API.
Limits
- The limits of your plan apply (requests per minute, uploads per month).
- Make has its own limits for file size and run time per scenario run depending on your Make plan. For large videos send a public URL instead of the file.
- Synchronous uploads can take up to a minute; use
async_upload=trueand a webhook if your scenario must finish quickly.
Setup
- In our app create an API key under API & webhooks.
- In Make add the module HTTP → Make a request:
- URL
https://my-video-automation.com/api/upload, methodPOST - Headers:
Authorization=Apikey YOUR_KEY - Body type: Multipart/form-data
- Fields:
user= your profile name,platform[]=youtube(one field per platform),title, andvideoas a text field with the public video URL – or as a file field with the file from a previous module - Optional:
scheduled_date,timezone,async_upload - Tick "Parse response"
- URL
- Run the scenario once and check
request_idorjob_idin the output. - For results: new scenario with Webhooks → Custom webhook, copy the address, add it in our app under API & webhooks → New webhook, then click Send test event so Make learns the data structure.
More: webhooks, API and keys.
FAQ
Do I need a paid Make plan?
No for our side; the HTTP module is available on all Make plans. Make's own operation limits apply.
How do I post to several platforms?
Add platform[] once per platform in the multipart fields.
Can Make wait for the result?
Better not: use async_upload=true and handle the result in the webhook scenario.