Make & n8n Integration

Make vs n8n

Both Make (formerly Integromat) and n8n are visual automation platforms that connect VideoNest to other tools via multi-step workflows. They're well-suited for more complex logic than Zapier — including branching conditions, data transformation, and looping. n8n can be self-hosted for teams that need to keep data on-premises.

Connecting VideoNest

Both platforms connect to VideoNest via its REST API. You'll need your VideoNest API key to authenticate. See API Authentication for how to generate one.

In Make, use the HTTP module to call VideoNest API endpoints. In n8n, use the HTTP Request node with Bearer token authentication.

Setting up Make (formerly Integromat)

1. In Make, create a new Scenario and click the + to add a module.
2. Search for HTTP and select Make a request.
3. Set the URL to the VideoNest API endpoint (e.g. https://api.videonest.co/v1/videos).
4. Set Method to the appropriate HTTP verb (GET, POST, etc.).
5. Under Headers, add Authorization with value Bearer YOUR_API_KEY.
6. For POST/PATCH requests, set Body type to Raw, Content type to application/json, and provide the JSON payload.

Example scenario: Monitor an RSS feed for new articles → extract video URL from each item → call POST /videos to import into VideoNest with the article title as the video title.

// POST /videos payload mapped from RSS item fields
{
  "title": "{{item.title}}",
  "description": "{{item.summary}}",
  "channel_id": "ch_abc123",
  "source_url": "{{item.enclosure.url}}"
}

Setting up n8n

1. In your n8n workflow, add an HTTP Request node.
2. Set the URL to the target VideoNest API endpoint.
3. Set Authentication to Header Auth. Add header name Authorization and value Bearer YOUR_API_KEY.
4. Set Method and configure the request body as JSON for write operations.
5. Use n8n expressions ({{ $json["field"] }}) to map values from upstream nodes into the request.

Example workflow: Webhook trigger receives a payload from a CMS → HTTP Request node calls POST /videos on VideoNest → second HTTP Request node calls POST /feeds/:id/publish to push the feed immediately after upload.

Advanced patterns

Error handling: Both Make and n8n support conditional routing based on HTTP response status. Route on a non-2xx response to a notification step (email, Slack) or a retry queue. Check the status field in the VideoNest response body for application-level errors.

Conditional routing: After calling GET /videos/:id, branch your scenario or workflow on the status field — proceed only when status === "ready", and route to an error handler if status === "failed".

Pagination: When using GET /videos to retrieve large libraries, loop through pages by incrementing the page query parameter until the returned data array is empty.

When to use Make, Zapier, or n8n