Zapier & Make.com
Integrate footage.one into no-code automation tools such as Zapier or Make.com — via REST and API token.
Overview
Zapier and Make.com currently do not support MCP. Instead, use the REST API with an HTTP module (Make) or Webhook / Code step (Zapier).
Auth
API token from https://app.footage.one/account. Send per request as a header:
apiKey: YOUR_API_TOKEN
Make.com — example module
| Field | Value |
|---|---|
| Module | HTTP > Make a request |
| URL | https://app.footage.one/api/asset/albums |
| Method | GET |
| Headers | apiKey: YOUR_API_TOKEN |
| Parse response | Yes |
The response contains _links to all sub-endpoints — follow-up modules build on those hrefs.
Zapier — Webhook by Zapier
- Trigger: Zapier-specific (e.g. new row in Google Sheets)
- Action:
Webhooks by Zapier > Custom Request- Method:
POST - URL:
https://app.footage.one/api/asset/albums - Headers:
apiKey: YOUR_API_TOKEN - Data: JSON payload with album data
- Method:
Note
REST + token is robust, but not an "agentic" setup — the workflows are statically wired. For AI-driven automation, prefer n8n with MCP.