How do I use a screenshot from URLpipe in Make?

Read the X-Result-Url response header: a keyless image link valid for 30 days. The body itself is the image in Base64.

How do I get async results into Make?

Use a Custom webhook trigger in a second scenario and pass its address as report_to. URLpipe posts the result there when it is ready.

Why did Make say the JSON is invalid?

A mapped value probably contained a quote or a line break. Build the body with the Data structure input method or the JSON app so values are escaped.

Integrations

URLpipe in Make

Metadata, screenshots and Markdown for every URL a scenario touches — with the HTTP module.

By Roger Campos · Last updated: September 2026

TL;DR

To use URLpipe in Make, add the HTTP app's "Make a request" module: POST to an endpoint such as https://urlpipe.dev/meta, an Authorization: Bearer header, a JSON body with the URL, and Parse response on. For slow work, pass a Custom webhook's address as report_to and let the result trigger a second scenario.

Start free See the API

Free plan, no credit card. 1,000 credits a month.

Setup

The module, field by field

Add HTTP → Make a request after whatever produces your URLs — a Google Sheets row, an RSS item, a form submission.

Field	Value
URL	<code>https://urlpipe.dev/meta</code> (or <code>/markdown</code>, <code>/screenshot</code>, <code>/scrape</code>…)
Method	<code>POST</code>
Headers	<code>Authorization</code>: <code>Bearer YOUR_API_KEY</code>
Body content type	<code>application/json</code>
Body input method	JSON string — or Data structure, if you'd rather map fields than type JSON
Body	<code>{"url": "{{1.url}}", "sync": true}</code>
Parse response	Yes, for the JSON endpoints: /meta, /console, /lighthouse, /scrape
Timeout (advanced)	At least 70 seconds, so a sync call can finish

{{1.url}} is Make's mapping of the first module's url field — pick it from the mapping panel rather than typing it. If the URL could contain a double quote, build the body with Data structure (or the JSON app's Create JSON) instead of a hand-written string, so it is escaped.

Output

Reading the response

With Parse response on, /meta gives you Data: title, description, site_name, image: url, favicon_url, authors, published_at and the rest, ready to map into the next module. /markdown and /screenshot answer with plain text, which arrives as Data — Markdown, or a Base64 image.

For a screenshot you want as a link rather than bytes, read the X-Result-Url response header from the module's Headers output: a link to the image that needs no API key and stays valid for 30 days — ready for an email, a Slack message or an Airtable attachment field.

Body — a link-preview screenshot

{
  "url": "{{1.url}}",
  "sync": true,
  "screenshot_options": {
    "full_page": false,
    "viewport_width": 1200,
    "viewport_height": 630,
    "format": "webp"
  },
  "page_options": { "block_cookie_banners": true }
}

Slow work

Async with a Custom webhook

1
Create a second scenario whose trigger is Webhooks → Custom webhook, and copy its address (https://hook.region.make.com/…).
2
In the first scenario's body, drop sync and add "report_to" with that address, plus "labels": {"row": "{{1.id}}"} so you can match the result to its source.
3
Run the first scenario once so a real delivery reaches the webhook, and let Make determine the data structure from it.
4
Map success, result, labels.row and error into whatever comes next.

Make's hook addresses are public HTTPS URLs on the default port, which is what URLpipe requires of a webhook. The first scenario gets {"token": …, "status": "accepted"} back straight away and finishes.

Limits

What it costs, and what it doesn't do

Every run of the module is one API call: 1 credit for /meta, 1 for a screenshot, 1 for Markdown. Make counts its own operations separately.
Repeats of the same URL inside seven days are free cache hits — handy while you test a scenario.
The API allows 60 requests a minute per project; for long lists, add a Sleep or run the scenario in smaller batches.
There is no URLpipe app in Make yet; this recipe uses the HTTP module, which is all the API needs.

Endpoints

The endpoints on this page

/meta API docs /screenshot API docs

FAQ

Frequently asked questions

HTTP → Make a request, with POST, an Authorization: Bearer header, a JSON body and Parse response on for JSON endpoints.

Keep reading

Screenshots capture the whole page Extracting page metadata Link previews and unfurls og:image Open Graph image sizes Microlink alternatives All of integrations

Connect it in five minutes.

Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.

Start free Email the team