Skip to main content
POST

Endpoint

Use this endpoint to launch an Overlap clipping workflow from an existing template.
Find workflowId in the workflow URL: https://portal.overlap.ai/workflows/{workflowId}/trigger.

Authentication

Generate an API key from the workflow trigger screen in the Overlap portal. Overlap-Workflow-Channel is optional; omit it to use the current workflow runtime.

Request Body

Required fields are companyId, workflowId, and url. Every other field is optional and overrides the saved template only for this run.

Fields

Workflow Runtime Channel

By default, requests run on the current workflow service. To use the pinned stable service for a run, add:
Only current and stable are accepted. Any other value returns INVALID_WORKFLOW_CHANNEL without storing or dispatching the run. The response echoes the applied channel in the same header. The channel is routing metadata and is not passed to workflow nodes as input.

Workflow Runtime Channels

See channel behavior, complete request examples, responses, and errors

Google Drive Source URLs

You can use a Google Drive video as the url value when triggering a workflow. Before sending the request, verify both of these requirements:
  1. Use a direct Google Drive file link. The URL should include /file/, for example https://drive.google.com/file/d/FILE_ID/view?usp=sharing. Folder links, preview links, and other Drive URLs that do not include /file/ are not supported source-file links.
  2. Make the file accessible to Overlap. Either set the file to public access, or share it directly with the Overlap service account: [email protected].
If the Drive file is private and is not shared with that service account, the workflow may trigger successfully but fail when Overlap tries to download the source video.

Override Behavior

Overrides only apply when the referenced workflow contains the matching node. For example, subtitleConfig is ignored if the workflow does not include a subtitles node. For advanced integrations, use nodeConfigs, nodeConfigOverrides, or actionConfigs to update action node configuration directly. Supported node keys include find_clips, convert_to_vertical, add_subtitles, add_broll, add_music, add_watermark, apply_branding, add_title_overlay, and other workflow action nodes. If a workflow contains the target node but the override shape is invalid, the request returns an INVALID_NODE_CONFIG error.

Node Config Overrides

See frontend-configurable override fields and per-node examples

Response

  • triggerId - Save this value and poll GET /workflow-results/{triggerId}.
  • status - Usually pending immediately after triggering.
  • message - Human-readable confirmation or context.
The Overlap-Workflow-Channel response header reports current or stable, matching the runtime selected for the run.

Processing Time

  • Horizontal clips: about 3 minutes per hour of input video.
  • Vertical clips: about 10 minutes per hour of input video.
  • Actual runtime varies by workflow configuration, video length, and video complexity.

Get workflow results

Poll for status and retrieve generated clips with your triggerId