Runway

Runway

Agent-callable tools for Runway generative media (https://api.dev.runwayml.com/v1): generate images and video from text or an image, edit/restyle and upscale existing media, animate a character from a driving performance, generate speech, sound effects, voice conversions and dubs, and run Runway's one-shot marketing "recipes" (product ads, campaign images, UGC, product swap, ad localization). Every generation is asynchronous — the generate/audio/recipe tools return a task id and you poll getTask for the finished asset URLs (or pass wait: true to block until the job finishes). Generated asset URLs expire in 24-48 hours, so download and rehost them promptly.

Independent, unofficial connector for Runway. Not affiliated with, endorsed by, or sponsored by Runway. "Runway" is a trademark of its owner, used only to identify the service this connector works with.

When to use this

• Generate visual media — make an image (generateImage), a video from an image (generateVideoFromImage) or from text (generateVideoFromText), restyle a video (editVideo), upscale an image or video (upscaleImage / upscaleVideo), or animate a character (animateCharacter).
• Generate audio — text-to-speech (generateSpeech), sound effects (generateSoundEffect), voice conversion (convertVoice), dubbing (dubAudio), or voice isolation (isolateVoice).
• Run marketing recipes — one-shot higher-level jobs: generateProductAd, generateCampaignImages, generateMarketingImage, swapProduct, generateProductUgc, generateMultiShotVideo, localizeAd.
• Track jobs and account — check a job with getTask, stop one with cancelTask, and read credits / concurrency limits with getOrganization / getCreditUsage.

Setup

This is an agentskills.io skill.

If the connector has not been installed as a skill yet, install it first with npx skills add zapier/connectors --skill runway (or your harness's own skill-install mechanism), then continue here. Installing the skill copies these files, not dependencies. Before running the CLI, a local MCP server, or zapier-sdk auth commands, run npm install --omit=dev here once. Importing the published package as a dependency in your own project instead? That npm install already resolves everything — see references/use-as-sdk.md.

Want the actual repo source instead — to browse references/, run this connector's tests, or hack on it? See README.md for a scoped git clone.

The connector runs on Node.js 22.18+. Pick the reference that matches how you're running it, and load it before doing anything else:

Scripts

All scripts use the single connection runway. The generate, audio, and recipe tools are asynchronous — they return a task id (poll getTask), or accept wait: true to block until the job reaches a terminal state.

Disambiguation & refusals

Task ids passed to getTask / cancelTask come from the generate/audio/recipe tools' own output — there is no name-based lookup to disambiguate. Watch instead for jobs this connector deliberately does not cover; say so and stop rather than substituting another tool and reporting success:

• Uploading local files / raw bytes. There is no upload tool. Every asset input takes an HTTPS URL or a data URI — host the file and pass its URL. Don't claim a local path was uploaded.
• Avatars, custom voice management, documents/knowledge, realtime sessions, saved workflows. These separate Runway products are out of scope; this connector covers the generation core plus marketing recipes only.
• Permanent deletion beyond a task. cancelTask cancels/deletes a single generation task; there is no bulk or account-level delete.
• Per-model pricing. The API exposes no price catalog. getCreditUsage reports actual spend after the fact and getOrganization reports limits — neither quotes a per-generation price up front.

If asked for any of these, tell the user it's unsupported and stop.

Auth

Every shape passes auth as one connection selector, not the secret — a [<resolver>:]<value> string. Every connector accepts zapier:<connection-id> (Zapier-managed auth — routes through Zapier's auth, retries, and governance layer); some also accept one or more direct-token resolvers (naming and count vary per connector) — check this connector's own resolvers rather than assuming. The <resolver>: prefix is optional; a bare value goes to the first resolver that claims it — a UUID-shaped bare value always claims zapier:. Each script declares the connections it needs and the resolvers each accepts. The exact syntax for passing a connection (and how to see this connector's resolver list) differs by shape — see the reference you loaded above.

Checking what's already configured first? Don't dump environment values to do it — env or env | grep <name> prints the value along with the name, leaking a live credential into the transcript if one is set. Check names only (env | cut -d= -f1 | grep -i <name>) or test a known name directly ([ -n "$VAR_NAME" ]).

No connection yet? Pick one — and follow the reference's own flow to obtain it; never just ask the user for a connection id or token as if they already have one memorized:

Output format

Every script returns a { data, meta } envelope:

• data — the script's result (the shape its outputSchema declares; see the reference you loaded above for how to inspect a script's exact schema in your shape).
• meta.outputDataValidation — what validating data did:
  • { skipped: false, droppedPaths: null } — validated, nothing removed.
  • { skipped: false, droppedPaths: [...], instruction } — validated, but those paths were stripped from data: fields the script returned from the API that the outputSchema doesn't declare. If you need them, re-run with output validation skipped.
  • { skipped: true } — validation was bypassed; data is the raw, unchecked script output.

Reading dropped fields / skipOutputDataValidation. To receive the raw, unvalidated result, opt out of output validation (the exact syntax differs by shape — see the reference you loaded above). Input validation is never skipped.

Trimming the result / filterOutputData. To shrink a large result down to the fields you need, pass a jq expression that post-processes data (again, exact syntax per shape). The jq runs against data only, NOT the { data, meta } envelope, so write it rooted at data (run the script's --help — or your shape's equivalent — to see its output schema). The transformed value replaces data, meta is preserved, and the result is NOT re-validated against the output schema.

References

Load the matching reference file before working in that area: