n8n workflow with footage.one
Integrate footage.one into n8n workflows — via MCP Client Tool with OAuth2 or directly via the REST API with API token.
Two approaches
MCP Client Tool (with OAuth)
n8n supports MCP natively via the MCP Client Tool node. The auth flow runs via OAuth: a one-time browser login during setup configuration; n8n manages tokens automatically thereafter.
Configuration:
| Field | Value |
|---|---|
| Endpoint URL | https://mcp.footage.one/mcp |
| Transport | HTTP Streamable |
| Authentication | OAuth2 (via n8n credentials) |
On first use, n8n opens the OAuth flow to footage.one. After a successful login, all MCP tools (search_assets, list_albums, add_keywords_to_asset, …) are available in the workflow.
REST directly (with API token)
If you don't want an interactive OAuth flow — e.g. because a service account pattern is needed — use the HTTP Request node with the REST API instead:
| Field | Value |
|---|---|
| URL | https://app.footage.one/api/asset/... |
| Method | depending on the operation (GET, POST, PATCH, DELETE) |
| Headers | apiKey: YOUR_API_TOKEN |
Token from your account. See REST API Quickstart for specific endpoints.
Example workflow: auto-tagging on storage import
- Webhook Trigger — receives notification from the storage provider (e.g. new file in S3)
- MCP Client Tool:
import_storage_items— imports file - AI Agent with MCP Client Tool — tool selection:
generate_description,get_keyword_suggestions - MCP Client Tool:
add_keywords_to_asset— save keywords - MCP Client Tool:
add_assets_to_album— asset into target album
In the purely REST-based variant, HTTP Request nodes replace the MCP Client Tool — the logic remains identical, because MCP tools map 1:1 to REST endpoints.