Resources · Make integration

Olostep Make integrationAutomate Olostep with Make.

Need the content of a web page inside an automation, without writing a scraper? The Olostep Make integration gives you 2 action modules, Scrape a URL and Make an API Call. This guide shows how to link your API key and build a first scenario around them.

Try the Olostep integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Olostep Make integration do for you?

The Olostep Make integration lets a Make scenario (the automation you build in Make, a chain of modules) ask Olostep to scrape a web page and pass the result to the next step. A module is one brick of that chain. Olostep brings two of them, both actions, so something else has to start the scenario.

Enrich a lead list with page content. A new company appears in your CRM or your spreadsheet with its website. Make hands that address to Scrape a URL, and whatever Olostep returns can be mapped into the next module, for a summary, a note, or a row update.

Watch pages your team cares about. Keep a list of pages in a sheet, let a scheduled scenario read it, and send each address to Olostep. Every page travels as one bundle, meaning one item that flows from a module to the next.

Reach the rest of the Olostep API. When the scraping module is not enough, Make an API Call calls any endpoint of the Olostep API with the same connection.

What Make will not do here: start a scenario from Olostep itself, since the app has no trigger. The Make documentation for Olostep is also flagged as AI-generated from vendor material, so check any detail that matters with Olostep. To see how Make compares with its closest rival, read n8n vs Make, and before you pick a plan, look at Make pricing. If you would rather have the scenario built for you, the Make agency page explains how the team works.

Connect

How do you connect Olostep to Make?

  1. 01

    Copy your Olostep API key

    You need an active Olostep account first. Open your account settings, go to the Authentication section, and copy the API key shown on that page. Keep it at hand, Make will ask for it in a moment.

  2. 02

    Open a connection from the module

    In your scenario, add an Olostep module and click Create a connection. A connection is your Olostep account linked to Make once, then reused by both modules. You can type a label in Connection name, which helps if several accounts coexist.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make displays on screen, then confirm. The connection now appears in the module's dropdown, and any other Olostep module you add later can pick it directly.

First scenario

Your first scenario with Olostep and Make

GoalWhen a new URL shows up in another app, Make sends it to Olostep and passes the scraped page to the next module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Olostep has no trigger, so pick the app where your URLs live, such as a sheet or a form.

  2. 02

    Add Scrape a URL

    Click the + to the right of that first module, search for Olostep, and choose Scrape a URL. Select the connection you created, or click Create a connection if this is your first time.

  3. 03

    Map the address

    In the module fields, map the URL coming from the first module instead of typing a fixed one. That way each new bundle, one address each time, gets its own scrape.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received and check what Olostep sent back before going further.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan) and switch the scenario on. Add a module after Olostep whenever you know where the content should go.

Modules

What the Olostep modules do

Olostep gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Olostep1

Make an API Call

ActionIn the docs only

This module opens the whole Olostep API to your scenario: you call any endpoint yourself, and Make reuses the connection you already set up, so no second key to manage.

When to use it
the page you need is handled by an Olostep feature that Scrape a URL does not cover and you have found the endpoint in its API reference.
Watch out
you write the request by hand, so read the vendor reference first. Each call still counts as one operation, a single execution Make counts on your plan.
Olostep2

Scrape a URL

ActionIn the docs only

Give it a web address and it asks Olostep to scrape that page, then hands the result to the modules that follow. A link sitting in another tool becomes content you can reuse.

When to use it
a new link appears in a sheet, a form or a CRM record, and the next step needs what is on the page.
Watch out
map the URL from the previous module rather than typing it, otherwise every run scrapes the same page and burns operations for nothing.
Need help

Need help automating Olostep with Make?

A person reads every message.

FAQ

Olostep and Make: frequent questions

01Is the Olostep Make integration free?
Yes on the Make side: Olostep is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum 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, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Olostep itself needs an active account with an API key, and its subscription is described on the Olostep pricing page.
02What do you need to connect Olostep to Make?
An active Olostep account and its API key. The key sits in the Authentication section of your Olostep account settings: copy it, add any Olostep module to a scenario, click Create a connection, optionally name it, and paste the key. That single connection then serves both modules, Scrape a URL and Make an API Call. If the screens differ from what the Make documentation describes, remember that this documentation is flagged as AI-generated, so check with Olostep.
03Can the Olostep Make integration react in real time?
No, not by itself, because Olostep has no trigger module in Make, neither scheduled nor instant. A scenario that uses Olostep has to start somewhere else. The usual choice is a trigger from the app holding your URLs, a new row or a new form answer for example. You can also start the scenario on a schedule, every 15 minutes by default, or with a webhook from another tool when you need Make to react as soon as an event happens.
04What if the Olostep module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Olostep API with the connection you already have, so a feature without its own module stays within reach. The trade off is that you write the request yourself from the Olostep API reference. Also keep the Make plan limits in mind, since a long scrape runs inside the execution time your plan allows, 5 minutes on Free and 40 minutes on paid plans.
05Should you use Make or n8n with Olostep?
It depends on how you like to work, and the tools are best compared on their own terms. In Make, Olostep offers 2 modules, Scrape a URL and Make an API Call, which together reach the full Olostep API through one connection, with a visual editor and a Free plan to test on. Whether an n8n node exists for Olostep is worth checking on the n8n side. The n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations