Media2URL

Media2URL integrations

Quick answer

Media2URL integrations connect files from your workspace or automation workflow with hosted links. Choose your platform below for setup instructions, supported operations, permissions and availability. Each section explains the connection method and account limits that apply.

In this article5 sections · Jump to what you need
Official Google Workspace Add-on

Create in Google Workspace. Publish anywhere with Media2URL.

Keep Google Drive for internal collaboration, storage, and editing. Use Media2URL to publish selected Drive files as clean external direct links, permanent QR codes, temporary shares, and managed URLs that update seamlessly as your files evolve.

Free to install from the Google Workspace Marketplace. Connect your existing Media2URL account to publish single files, export Google Docs and Slides to PDF, or batch publish entire folders with one click.

Connect Google Workspace View Plans & Entitlements
Hero Workflow

Update your Drive content. Keep the exact same link and QR code.

Avoid broken links, outdated email attachments, and reprinting physical QR signage. Media2URL gives your Google Drive files a persistent external publication layer.

1

Select File in Drive

Choose any image, PDF, audio, video, Google Doc, or Slides presentation in Google Drive.

2

Publish with Media2URL

Open the Media2URL side panel to generate a high-speed Direct CDN URL, Share Link, and QR code.

3

Share & Print QR

Embed the direct link in websites, customer emails, documentation, or print the QR code on physical signs.

4

Publish Latest Version

When the Drive file is modified, click Publish Latest Version. The managed URL and QR code stay identical.

Permanent QR Delivery

Generate crisp PNG QR codes linked to your stable Media2URL CDN URL. Perfect for restaurant menus, event programs, packaging, and classroom resources that require recurring content updates.

Docs & Slides PDF Export

Seamlessly convert native Google Docs, Google Slides, and Google Sheets into clean external PDFs without creating messy intermediary Drive sharing links.

Same-URL Updates & History

Update external assets on demand while maintaining full version history in Media2URL. Roll back or inspect previous iterations whenever needed.

Drive Multi-Select Batching

Select multiple Drive files at once to inspect publication status, publish collections in bulk, and receive unified link and QR output summaries.

Temporary Share Packs

Publish time-sensitive files with authoritative server-backed expiration (1 hour, 1 day, 7 days, 30 days, or custom) and clear expiration timestamps.

Enterprise Security

Multi-stage file signature verification, Cloudflare edge delivery, secure per-user token isolation, and strict Google API Limited Use compliance.

Free Installation with Flexible Plans

The Media2URL Google Workspace add-on is completely free to install. Free accounts can use our shared hosted trial to test publishing workflows.

Free Hosted Trial

Free
  • ✓ 3 lifetime hosted trial publications across Media2URL integrations
  • ✓ 48-hour temporary asset retention
  • ✓ Up to 2 MB per file (PNG / JPG)
  • ✓ Direct CDN URL, Share Page, and QR preview
  • ✓ Single file inspection & selection in Drive

Paid Subscriptions

Pro / Business
  • ✓ Permanent, persistent cloud hosting
  • ✓ Same-URL updates (Publish Latest Version)
  • ✓ Native Google Docs, Slides, and Sheets PDF publishing
  • ✓ Large file uploads (up to plan storage limits)
  • ✓ Multi-selection batch publishing
  • ✓ Custom delivery domains & workspace collaboration
Compare all Media2URL plan features and pricing →

Frequently Asked Questions

Does Media2URL replace Google Drive?

No. Google Drive remains where your team creates, edits, and collaborates internally. Media2URL is where you publish files for external use — delivering direct CDN links, customized share pages, QR codes, and versioned asset delivery without requiring your audience to have a Google account.

How does the same-URL update workflow work?

When you publish a Drive file (like a menu, product brochure, or presentation handout), Media2URL generates a stable managed URL and QR code. Later, when you update the file in Google Drive, clicking 'Publish Latest Version' refreshes the content while keeping the exact same managed URL and QR code intact.

Can I export Google Docs, Slides, and Sheets as PDFs?

Yes. When you select a Google Doc, Google Slides deck, or Google Sheet in Drive, Media2URL exports the native document to a high-quality PDF and publishes it as a direct CDN link or viewer page with an instant QR code.

What Google Drive permissions does Media2URL request?

Media2URL adheres to Google's strict minimal-privilege security model. It only requests 'drive.file' (access only to files you explicitly select or open with the add-on) and 'drive.addons.metadata.readonly' (to show contextual information in the Drive sidebar). It does NOT request full access to your entire Google Drive.

Is the Google Workspace add-on free to install?

Yes. The Google Workspace add-on is free to install from the Google Workspace Marketplace. Eligible free accounts can use Media2URL's central global trial (up to 3 lifetime hosted publications, 48-hour retention, 2 MB limit). Persistent hosting, larger file limits, same-URL version replacement, and multi-file batch publishing require an active Media2URL paid plan.

Do QR codes expire if the Drive file is modified?

No. QR codes generated by Media2URL point directly to your stable managed Media2URL URL, not an expiring Google Drive session link. When you update the published version, the QR code on your printed signs, packaging, or documentation continues working without any changes.

Related File Delivery Tools

PDF to LinkPublish PDFs externally or generate shareable viewer pages.Image to LinkConvert Drive photos and diagrams into direct CDN links.File to LinkHost documents, presentations, or general files.Screenshot to URLTurn captured visual assets into permanent links.Audio to LinkDeliver external audio podcasts and voice notes.Video to LinkHost and share MP4 videos without Google Drive viewer friction.

Platform References

Media2URL homepageAll Media2URL toolsREST API v1 documentationPlans and pricingSecurity CenterPrivacy PolicyTerms of ServiceContact Media2URL Support
Official Notion Integration

Turn Notion media and documents into permanent Media2URL links

Connect Notion directly to Media2URL. Seamlessly convert temporary Notion file links into permanent CDN direct URLs, insert Media2URL hosted assets into Notion pages, and write live URLs into Notion database properties with a single click.

Media2URL is free to connect to Notion. Eligible free Media2URL accounts can use a small temporary hosted trial shared across Media2URL integrations. Persistent hosting and advanced asset workflows require an eligible Media2URL plan.

Open Notion Integration View API Documentation

Supported Notion Workflows

Media2URL is designed around clean, practical media and document workflows inside Notion.

1. Notion to Media2URL

Select any authorized Notion page or database item. Media2URL inspects images, files, or PDFs, securely imports the file into high-performance R2 storage, and generates reusable Direct & Share URLs.

2. Media2URL to Notion

Choose an existing Media2URL asset from your library and insert it into a Notion page as an image block, PDF embed, file link, or bookmark.

3. Database URL Automation

Publish media associated with a Notion database record and automatically write the permanent direct link back into a chosen URL property.

Account Features & Commercial Model

Media2URL is free to connect to Notion. Free accounts can test workflows with temporary publications, while paid plans unlock permanent hosting and advanced asset management.

Free Capabilities

  • • Connect and disconnect Notion workspaces
  • • Browse authorized Notion pages and databases
  • • Universal Global Lifetime Free Trial (3 publications, 2 MB max, 48-hr retention)
  • • View trial status and delete owned assets anytime

Paid Capabilities

  • • Permanent asset hosting without expiration
  • • Same-URL asset replacement (preserve existing links)
  • • Version history, rollback, and asset organization
  • • Custom delivery domains, higher limits, and team collaboration

Frequently Asked Questions

How does the Notion connection work?

Media2URL uses official Notion OAuth 2.0. You authorize Media2URL to access only the specific Notion pages or databases you select. Media2URL then allows you to inspect media blocks, host them as direct CDN URLs, or insert existing Media2URL assets into your Notion workspace.

Why convert Notion file URLs to Media2URL direct URLs?

Notion-hosted file URLs are signed temporary links that expire after a period of time. By importing media to Media2URL, you generate a permanent, high-performance Direct URL or Share URL suitable for public websites, apps, embeds, and cross-platform sharing.

What capabilities and permissions are requested?

Media2URL requests read content (to inspect media blocks and database items) and insert/update content (to write direct URLs to database URL properties or append image/file blocks). Media2URL does not request broad workspace admin access or unnecessary user email permissions.

Is the Notion integration free to use?

Media2URL is free to connect to Notion. Eligible free Media2URL accounts can use a small temporary hosted trial shared across Media2URL integrations (up to 3 lifetime publications, 48-hour retention, 2 MB limit). Persistent hosting, larger file support, custom domains, and same-URL asset replacement require an eligible Media2URL plan.

What is same-URL replacement?

For eligible paid plans, when you update a media block in Notion and replace an existing Media2URL asset, Media2URL creates a new version history entry while keeping the managed direct delivery URL unchanged. Embedded images and links across the web update automatically.

How do I disconnect my Notion workspace?

You can disconnect your Notion workspace anytime from the Media2URL connection dashboard or from your Notion workspace settings. Disconnecting revokes access tokens and prevents future synchronization while safely preserving your previously published Media2URL files.

Make Integration

Turn Make scenario files and URLs into Media2URL links

Connect your Make scenarios directly to Media2URL. Upload binary files from Google Drive, Dropbox, or webhooks, safely import remote files by URL, manage hosted assets, and update existing media while keeping the same direct delivery URL.

Media2URL for Make is free to install and connect. Eligible free accounts receive a small temporary hosted trial to test workflows, while ongoing production automation and asset replacement use your existing Media2URL subscription.

Get Make API Key Read API v1 Docs

Practical Make Workflows

Media2URL acts as the hosted media layer inside your Make automation scenarios. Common production patterns include:

  • Google Drive → Media2URL → Google Sheets: Watch a Drive folder for new files, upload each binary buffer to Media2URL, and record the generated Direct URL in a spreadsheet.
  • Dropbox / Webhook → Media2URL → Email / Slack: Receive user-submitted files from web forms or Dropbox, host them instantly, and email client-friendly Share URLs.
  • AI Image Generation → Media2URL → WordPress: Generate media via OpenAI / Midjourney / Stability AI, import the remote URL directly into Media2URL, and embed the hosted direct link in CMS posts.
  • File Update → Replace Asset: When an updated document or image is uploaded to cloud storage, replace the existing Media2URL asset so downstream embeds automatically display the latest version without changing URLs.

Step-by-Step Setup Guide

Get your Make integration running in under two minutes using a scoped API key.

  1. 01 · Create Make API Key

    Generate scoped credential

    Go to your developer dashboard and click "Create Make Credential". Copy your secret API key (m2u_live_...).

  2. 02 · Add Connection in Make

    Authenticate your app

    In the Make scenario builder, add a Media2URL module, click "Create a connection", name it, and paste your API key. Make validates the key immediately against /v1/usage.

  3. 03 · Choose Module & Map Data

    Upload file buffer or import URL

    Select Upload a File to map a binary file buffer from an earlier module (e.g. Google Drive download), or Import a File From URL for public URLs.

  4. 04 · Run & Map Outputs

    Pass delivery URLs downstream

    Run the scenario once to generate live output bundles. Map direct_url or share_url into your downstream modules.

Available Make Modules

The Media2URL Make integration includes a dedicated suite of Action and Search modules:

Upload a File

Upload binary file data from a previous Make step and receive hosted delivery links.

Import a File From URL

Safely fetch a public HTTP/HTTPS URL server-side with SSRF protection and store it as a managed asset.

Get an Asset & Search Assets

Retrieve asset metadata by ID, or search your account library by filename with server-side pagination.

Replace an Existing Asset

Upload new content for an existing asset ID while keeping the same permanent direct URL intact.

Delete an Asset

Permanently delete an asset and immediately deactivate all its public and direct delivery links.

Get Account Usage

Inspect account plan status, storage bytes used, API request quotas, and remaining trial publications.

Free Hosted Trial & Paid Plans

The Media2URL Make integration is free to install. Free Media2URL accounts receive a central, shared hosted-publication trial (3 publications lifetime, up to 2 MiB per file, 48-hour retention) shared across all integrations.

Once trial credits are consumed, persistent hosting, larger files (up to 500 MiB), and same-URL asset replacements require an active Media2URL paid plan. Non-publishing operations (such as inspecting account usage, getting asset metadata, and deleting owned assets) remain fully accessible without a paid subscription.

Security & Secret Sanitization

Media2URL uses Make's native secret sanitization to ensure API keys and authorization headers are never exposed in scenario execution logs.

Review our Security Center, Privacy Policy, and Terms of Service for detailed governance guidelines.

Frequently Asked Questions

How does file mapping work in Make?

Media2URL accepts standard Make file objects (containing binary data buffer and filename) from earlier download modules like Google Drive or HTTP GET.

Does asset replacement change my existing direct URL?

No. When using the Replace an Existing Asset module on an eligible plan, Media2URL updates the asset contents while guaranteeing that the canonical direct link remains identical.

Can I retry failed Make executions safely?

Yes. Media2URL supports idempotency keys on creation and replacement actions to prevent duplicate uploads or double charging during automatic scenario retries.

Where do I get support?

Visit our contact page or email support@media2url.com.

Explore Media2URL Tools

Prepare your media workflows across any file type:

Resources & Reference

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

Published community node

Host images from n8n workflows with Media2URL

An n8n workflow can generate, download, or transform an image, but the next service often needs a URL rather than a binary file. The Media2URL community node takes that image, publishes it through your Media2URL account, and returns a URL your workflow can pass to the next step.

The package is available on npm as n8n-nodes-media2url. Install it on a self-hosted n8n instance where community packages are enabled, then connect your Media2URL account with an API key.

Read the API documentation Ask about the integration

Install the community package

On a self-hosted n8n instance, sign in as an owner or administrator. Open Settings → Community Nodes → Install, enter n8n-nodes-media2url, review the community-package notice, and install it. Follow n8n’s community-node installation guide if your instance needs additional configuration.

Add the Media2URL node to your workflow and create a Media2URL API credential. The package includes account usage, asset upload and URL import, asset lookup and listing, replacement, deletion, and version listing. Account permissions and plan limits still apply to each operation.

No AI model connection is needed

Media2URL is a file-hosting integration, not an AI model. This node does not require an AI model or an OpenAI-compatible provider; it uses a Media2URL API key saved as an n8n credential. The model-provider dialog belongs to n8n’s optional AI Assistant setup and is separate from an image upload workflow.

In the workflow, your image-producing node supplies the file, the Media2URL node uploads it, and n8n makes the returned URL available to later steps. You do not need to select a language model just to host an image.

How to upload an image from n8n

The node follows the usual n8n pattern: one step produces a binary image, Media2URL hosts it, and the next step receives ordinary URL fields. For a basic upload, select the credential and check the incoming binary property.

  1. 01 · Prepare the image

    Use binary output from an earlier step

    A generation, download, or editing node should provide the image as n8n binary data. The default property is binary.data; check the previous node’s output if your workflow stores the image under a different property.

  2. 02 · Connect Media2URL

    Save the API key as a credential

    Add a Media2URL API key through n8n’s credential selector. Keep the key out of ordinary workflow fields, expressions, exported examples, and logs.

  3. 03 · Choose the upload operation

    Select the incoming binary property

    The Asset → Upload Binary File operation uses data by default. If the previous step uses a different property name, set that field to match; the file itself remains in n8n’s binary data rather than being copied into a text field.

  4. 04 · Map the result downstream

    Pass the URL to the next service

    When the asset response includes these links, the node returns directUrl for a service that needs the image file and shareUrl for a person who should open a viewing page. Map the field that matches the receiving node rather than treating the two URLs as interchangeable.

If a source step provides a public URL instead of binary data, the Import From URL operation asks Media2URL to fetch it server-side. That keeps remote fetching and its safety checks on the service side rather than asking the n8n node to download arbitrary addresses itself.

Choose a URL for the next step

Media2URL is designed to return two different link types because a machine and a person do not always need the same destination. The receiving node determines which one belongs in your workflow.

Use directUrl for software

Choose the direct URL when an API, website, or downstream automation needs to request the image itself. It points to the media file, not a page with viewing controls.

Use shareUrl for people

Choose the share page when a teammate, customer, or reviewer should open a browser and view the asset. If the next service expects raw image bytes, use directUrl instead.

Know the upload limits

Eligible Free accounts use one shared account-wide hosted-publication trial across Media2URL integrations. It is intended for short-lived testing rather than permanent production media; check the live product and current plans and pricing before building a workflow that depends on these limits.

UseWhat to expect
Temporary trial3 successful hosted publications in total across eligible Media2URL integrations; PNG, JPG, or JPEG up to 2 MiB each; links expire after 48 hours.
Persistent hostingA paid plan is required for persistent hosting and replacement of an existing asset while keeping its managed URL.

Publications from other Media2URL integrations can reduce what remains for n8n. A temporary link is not suitable for a production workflow that needs an image to remain available beyond its expiry.

Keep credentials and source files under control

A workflow sends the selected image to Media2URL for hosting, so only pass files your account is allowed to publish and that you have permission to use. Store the API key as a credential; do not place it in prompts, normal node fields, public workflow exports, or logs.

For URL imports, treat the source address as untrusted. The import flow uses Media2URL’s server-side fetch and safety checks, including protection against private-network targets and other SSRF paths; it is not intended to make a private or internal address publicly accessible.

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

Questions before you build

Can I install the Media2URL node now?

Yes, on a self-hosted instance that allows community packages. An instance owner or administrator can install n8n-nodes-media2url through Settings → Community Nodes. If installation is unavailable on your instance, use n8n's HTTP Request node with the documented REST API.

Do I need an OpenAI key or model endpoint?

No. Model providers are for n8n’s AI features. The Media2URL node authenticates with a Media2URL API key stored in an n8n credential.

Which URL should I pass to another node?

Use directUrl when the receiving service needs the image file. Use shareUrl when a person should open a browser viewing page. Check the destination node’s input requirements if you are unsure.

Support, copyright, and reporting

For a question about the integration, contact the Media2URL team. To flag suspected misuse, use the abuse-reporting form; copyright holders can review the DMCA and copyright process.

Explore Media2URL