A configured recording trigger sends its URL to n8n, which creates an OpusClip API project. A verified completion webhook adds the result to a human review queue.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For creating short webinar candidates.
Other editors need different automation; verify API access and human review. Choose one for editing a reviewed video draft; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Editable story comes before automated clip volume. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Confirm media rights, output specifications and exports. Do not assume project interchange or equivalent API support.
Reviewed 2026-10-21. This page applies a shared comparison for “editing a reviewed video draft” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
You review clips before publishing.
Watch out for
Keep the human approval step: You review clips before publishing.
Starter prompt
Goal: Create a repeatable clipping queue for recordings you have permission to reuse. Tools involved: n8n, OpusClip. I will review clips before publishing. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.
Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
Gemini
To verify
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
n8n: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; OpusClip: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked
n8n supports authenticated webhooks and HTTP requests. OpusClip’s create-project API accepts a supported video URL and can send a signed completion webhook through conclusionActions. You must configure the recording platform’s event or provide the URL manually; publishing a recording alone does not trigger n8n. This proposed workflow has not been executed.
Pro Beta and Max have a 900-credit/15-hour monthly API allowance per workspace, with a 10-credit minimum per API project. Core endpoints allow 30 requests/minute per key; concurrent project caps are separate. A monthly-cap response is 403, while rate/concurrency limits return 429. Confirm account API entitlement before building.
Set it up
Confirm speaker consent, reuse rights and source-link access. Do not make a confidential recording public just to import it.
Configure an authenticated production n8n webhook or manual start. Validate the URL and retain a recording ID so retries do not create duplicate clipping projects.
Call the create-project endpoint with credentials stored securely, the desired brand/curation settings and a completion webhook. Save the returned project ID and record failures separately.
At the completion endpoint, verify the signature against the exact raw request body plus salt using the documented secret. Opus uses the organization’s first-created API key for signing. Reject malformed signatures and replayed salts/signatures; the timestamp alone is insufficient because it is not signed.
Queue retries with backoff for rate/concurrency errors, but stop and alert on exhausted monthly allowance. Test failed imports, duplicate callbacks and missing completion events.
Review clips for captions, misleading cuts, rights and brand fit before publishing manually. Save approved exports: projects normally expire after 30 days unless auto-save applies.
The callback’s signature verifies origin and integrity, not editorial quality. This recipe does not enable automatic social posting.