Resources · Make integration

OpenGraph.io Make integrationAutomate OpenGraph.io with Make.

Need the preview data behind a link without opening the page yourself? The OpenGraph.io Make integration gives you 1 action, Site Lookup, and no trigger. This page is for marketers and ops people who collect links, and it walks you from the connection to a scenario that runs on its own.

Try the OpenGraph.io integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OpenGraph.io Make integration do for you?

With the OpenGraph.io Make integration, a Make scenario (the automation you build, a chain of bricks called modules) can ask OpenGraph.io for the Open Graph information of a website. That is the data a site publishes to describe itself when someone shares its link. You get it back inside Make, ready to send to the next app.

A cleaner link library. When a teammate drops a URL into a sheet or a form, Site Lookup fetches the page's Open Graph information so the row stops being a bare address and starts looking like something a person can scan.

Richer content curation. A newsletter editor who saves articles from many sources can run each saved link through Site Lookup, then pass what comes back to a writing tool or a CMS in the next module.

Better lead research. A sales team logging a prospect's company site in a CRM can let Make look that site up and store the description next to the contact, before anyone opens a browser tab.

Know the limits up front. OpenGraph.io has no trigger in Make, so something else has to start the scenario: another app's module or Make's own schedule. There is also no Make an API Call module for this app, and the documentation gives no numeric limit. If Make is new to you, the Make review explains how the editor works, and the Make pricing page shows how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect OpenGraph.io to Make?

  1. 01

    Create an API key in OpenGraph.io

    Sign in to your OpenGraph.io account, open the API Keys section and click Create API Key. Copy the value it shows and keep it somewhere safe, because Make will ask for it in a moment.

  2. 02

    Add the module and open the connection

    In your Make scenario, add the OpenGraph.io module and click Create a connection. A connection is your OpenGraph.io account linked to Make once, then reused by every module of the app. Naming it in Connection name is optional.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Make asks you to authenticate or confirm access, accept it. The connection then shows up in the module, ready to use.

First scenario

Build your first scenario with OpenGraph.io

GoalWhen a new link lands in another app, Make looks it up with OpenGraph.io and passes the preview data along.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since OpenGraph.io has no trigger, this first module comes from the app where your links live.

  2. 02

    Pick the starting module

    Search that other app by name, choose the module that gives you new items, and connect its account. Each item it returns is a bundle: one row, one record, one message carrying a link.

  3. 03

    Add Site Lookup

    Click the + on the right of the first module, search OpenGraph.io and pick Site Lookup. Choose your connection, then map the website address from the previous module into it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Check that Site Lookup returned the data you expected for your test link.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default on a new scenario. Then switch the scenario on so it keeps working without you.

Modules

What the OpenGraph.io module does in Make

OpenGraph.io gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

OpenGraph.io1

Site Lookup

Action

In Make“Gets Open Graph information from websites.”

Site Lookup takes a website and hands back its Open Graph information, so a bare link becomes data the next module can store or reuse. It is the only OpenGraph.io module, and as an action it works on one item per run.

When to use it
right after a module that brings in a fresh link, such as a new row in a sheet or a new CRM entry.
Watch out
each lookup is one operation, the unit Make counts on your plan, so many links cost one operation each.
Need help

Need help automating OpenGraph.io with Make?

A person reads every message.

FAQ

OpenGraph.io and Make: common questions

01Is the OpenGraph.io Make integration free?
Yes, on the Make side. OpenGraph.io is a standard app, so it works from the Free plan onward. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need your own OpenGraph.io account, whose terms are set by OpenGraph.io.
02What do you need to connect OpenGraph.io to Make?
An OpenGraph.io account and an API key. Inside OpenGraph.io, go to the API Keys section, click Create API Key and copy the value. In Make, add an OpenGraph.io module, click Create a connection, give it a name if you like, paste the key into the API Key field and click Save. If Make prompts you to authenticate or confirm access, do it. That single connection then serves every OpenGraph.io module in your scenarios.
03Does the OpenGraph.io module run in real time?
It depends on what starts your scenario, because OpenGraph.io has no trigger of its own in Make. You have two options. Put another app's trigger first: an instant trigger fires as soon as that app calls Make through a webhook, while a scheduled trigger is checked on the scenario's schedule. Or use Make's scheduling alone, which runs every 15 minutes by default on a new scenario, and 1 minute at the shortest on paid plans. Site Lookup then runs each time the scenario does.
04What if an OpenGraph.io module is missing in Make?
OpenGraph.io offers a single module in Make, Site Lookup, and no Make an API Call module, so you cannot reach other parts of its API from this app. The documentation lists no numeric limit for the module either. If you need something Site Lookup does not cover, look for another app in Make that provides it, or ask the team at Hack'celeration to study your case and suggest a workable setup.
05Should you use Make or n8n for OpenGraph.io?
It depends on your criteria, not on a winner. Many apps available in Make also have an n8n node, so check whether OpenGraph.io does before you choose. In Make, you get one action, Site Lookup, a visual editor and a Free plan with 2 active scenarios. Compare how each tool handles the rest of your workflow, the apps you already use and the way you prefer to build. The n8n vs Make comparison linked on this page lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations