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.
Community node in development
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 planned Media2URL community node is designed to take that image, publish it through your Media2URL account, and return a URL your workflow can pass to the next step.
The node is not ready to install yet. This guide explains the intended workflow and planned account limits; it does not mean a package is available in n8n today.
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; when available, it will use 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 planned 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 the planned workflow will work
The node is being designed for the usual n8n pattern: one step produces a binary image, Media2URL hosts it, and the next step receives ordinary URL fields. The default is intended to stay simple, with only the credential and incoming binary property to check for a basic upload.
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.
02 · Connect Media2URL
Save the API key as a credential
When the node is released, you will add a Media2URL API key through n8n’s credential selector. Keep the key out of ordinary workflow fields, expressions, exported examples, and logs.
03 · Choose the upload operation
Select the incoming binary property
The planned `Asset → Upload Binary File` operation will use `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.
04 · Map the result downstream
Pass the URL to the next service
The result is designed to include `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 planned `Import From URL` operation will ask 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 `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 planned upload limits
The n8n free trial is planned around short-lived testing rather than permanent production media. The limits below describe the proposed integration behavior; check the live product and current plans and pricing before building a workflow that depends on them.
| Planned use | What to expect |
|---|---|
| Temporary trial | 3 successful hosted uploads in total through n8n; PNG, JPG, or JPEG up to 2 MiB each; links expire after 48 hours. |
| Persistent hosting | A paid plan is required for persistent hosting and replacement of an existing asset while keeping its managed URL. |
The n8n trial is separate from other Media2URL integrations. 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 planned 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?
Not yet. The community node is still in development and is not available through n8n’s installer. Until the package is released and the page is updated, use the documented REST API if you need to connect a workflow today.
Do I need an OpenAI key or model endpoint?
No. Model providers are for n8n’s AI features. The Media2URL node is designed to authenticate 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.
Where can I check the current product rules?
See pricing for current plan limits and the Acceptable Use Policy for publishing rules. For a product question, contact the Media2URL team.
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
- Media2URL homepageGet an overview of hosted media links and the service.
- Media2URL toolsExplore image, file, and media workflows available today.
- REST API v1 documentationUse the documented API for automation while the node is in development.
- plans and pricingCheck current plan features and limits before choosing a workflow.
- Privacy PolicyUnderstand how account information and uploaded files are handled.
- Security CenterReview security controls and guidance for connected workflows.
- Terms of ServiceRead the terms that apply when using Media2URL.
- Acceptable Use PolicyCheck which files and hosting behavior are permitted.
- contact the Media2URL teamAsk a product or integration question.
- report suspected abuseReport content or activity that may violate policy.
- DMCA and copyright processFind the process for copyright-related reports.
- SubprocessorsReview service providers involved in processing data.