Media2URL
Zapier integration in development

Turn Zapier files and URLs into Media2URL links

A Zap can receive a file from another app, send it to Media2URL, and pass a useful link to the next step. The planned integration is designed to support file uploads, public URL imports, asset lookup and management, and account usage checks.

The Zapier integration is still in development and is not available to install from Zapier. This guide describes the planned workflow; it does not mean the app has been approved, listed, or released.

Read the API documentation Ask about the integration

What a Zap will do

The integration is being built around everyday file handoffs. A trigger from a file, email, form, or content app can start the Zap; Media2URL then returns fields that are easier to map into the next action.

Connect a source and map the result

When the app is available, start with a Zap that already receives the right file or link. Keep the first version small so you can test each handoff before adding filters or later actions.

  1. 01 · Connect Media2URL

    Use a dedicated API key

    The planned connection uses a Media2URL API key created from the developer dashboard. Save it in Zapier’s connection field. Do not use your Media2URL password or put a key in a normal action field.

  2. 02 · Choose an action

    Upload a file or import a URL

    Use Upload File when the previous Zap step provides a file field or file pointer. Use Import URL when it provides a public file URL; Media2URL fetches and validates that source on its servers.

  3. 03 · Test the action

    Check the returned asset fields

    A successful test is designed to return an Asset ID, Direct URL, Share URL, and the temporary expiry details when the server marks an asset as temporary. Map only the fields the next step needs.

  4. 04 · Continue the Zap

    Choose the link for its destination

    Map the Direct URL when another app needs the media file itself. Choose the Share URL when a person should open a viewing page. A short test in the destination app confirms which format it accepts.

Planned asset and account actions

Uploading is only one part of a useful file workflow. The planned actions use Media2URL API v1 to manage assets already owned by the connected account and report the current account capabilities.

Upload File and Import URL

Create an asset from a Zapier file field or ask Media2URL to fetch a public URL safely.

Get Asset and Find Asset

Retrieve an owned asset by ID or find a matching filename, then map its current links.

Delete Asset and Replace Asset

Remove an asset your account owns, or replace its content while keeping the managed URL when your plan allows it.

Usage

Check current account capabilities and the remaining shared hosted-publication trial allowance.

Know when a temporary link fits

Eligible Free accounts use one shared account-wide hosted-publication trial across Media2URL integrations. Connecting Zapier does not add another allowance. The current API trial permits up to three successful hosted publications in total, for PNG, JPG, or JPEG images up to 2 MiB each; trial links expire after 48 hours. Check the account’s current Usage response and plans and pricing before building a workflow around those limits.

Previous qualifying publications through the website or another integration can reduce the remaining trial. A temporary link is for short-lived testing or handoffs, not for a production workflow that needs the same asset to remain available.

Persistent hosting and replacement

An eligible paid plan can allow persistent hosting, larger files, and replacement of an existing asset while preserving its managed URL. The API checks the account’s active entitlement; Zapier cannot change that limit.

Keep files and credentials safe

Connect only an API key created for the integration and keep it in Zapier’s credential storage. Do not paste it into prompts, ordinary action fields, shared Zap notes, or logs. Revoke a key from the developer dashboard if it is exposed.

Only upload files you have permission to use. For Import URL, treat the source as untrusted: Media2URL applies server-side checks, including protection against private-network and other unsafe targets. The action is not intended to make an internal address public.

Review the Security Center, Privacy Policy, Acceptable Use Policy, and Terms of Service before connecting account data to an automated workflow.

Questions before you build

Can I install the Media2URL app in Zapier now?

Not yet. The integration is in development and is not available in Zapier’s app directory. The REST API documentation describes the existing API for accounts that already have access.

Do I need a Zapier file or can I use a URL?

The planned Upload File action accepts a file field from an earlier Zap step. Import URL is for a public source URL that Media2URL can fetch and validate.

Which link should I map downstream?

Choose Direct URL when the destination needs the file response. Choose Share URL when someone should open a browser page to view the asset.

Choose a Media2URL tool for the file

If you are preparing a file outside Zapier or want to see the current browser workflow, start with the tool that matches the file you handle most often.

Explore Media2URL