Resources · Make integration

ParseHub Make integrationAutomate ParseHub with Make.

Your scrapes can start, stop and hand over their data without you opening ParseHub. The ParseHub Make integration gives you 10 modules: 1 instant trigger, 8 actions and 1 search. This page shows you how to link your account, build a first scenario and pick the right module.

Try the ParseHub integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ParseHub Make integration do for you?

The ParseHub Make integration links your ParseHub account to Make, a no-code tool where you build scenarios (an automation made of a chain of modules). Once connected, Make can start a scraping project, react when a run begins, and fetch the data a run extracted, then pass it to your other apps.

Scrapes that launch themselves. Put Run a Project after any event from another app, and ParseHub starts collecting on its cloud without a click from you. Pair it with Cancel a Run when a condition says the job is no longer needed.

Fresh data where your team works. Get Last Ready Data and Get Data For a Run hand the extracted results to the next module, so a sheet, a database or an Airtable Make integration can receive them.

A clear view of every run. Watch Runs wakes your scenario the moment a run starts in a project, and Get a Project adds its details, which is enough to keep a tidy log of what ran and when.

Know the limits before you build. The trigger only reacts when a run starts, not when it finishes. Make's own page for ParseHub states it was written with AI help and asks you to check important details with ParseHub. For anything the 10 modules skip, Make an API Call reaches the rest of the API with the same connection.

The same app often has an n8n node too. If you are weighing both tools, read n8n vs Make, and check Make pricing before you scale up.

Connect

How do you connect ParseHub to Make?

  1. 01

    Copy your ParseHub API key

    Make needs an active ParseHub account and its API key. In the ParseHub dashboard, click the profile icon labeled My Account in the left sidebar, then copy the key shown in the Account Settings panel.

  2. 02

    Add a ParseHub module in Make

    Open your scenario, add any ParseHub module and click Create a connection. The connection is your ParseHub account linked to Make once, then reused by every ParseHub module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read your projects.

First scenario

Your first scenario: log every ParseHub run

GoalWhen a run starts in a ParseHub project, Make fetches that project's details so you can record them anywhere.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. That first module is the one that decides when everything starts.

  2. 02

    Pick Watch Runs

    Search for ParseHub, choose Watch Runs, click Create a webhook and link your account through Create a connection. The lightning badge tells you ParseHub will call Make itself.

  3. 03

    Add Get a Project

    Click the + on the right of the trigger and add Get a Project. Choose the project, or map it from what Watch Runs passes along, so each bundle (one run flowing through) brings back its project.

  4. 04

    Test with Run once

    Click Run once, then start a run in ParseHub. Open the bubble above each module to read the bundles it received and confirm the project details look right.

  5. 05

    Switch it on

    Once the test is clean, add the module of the app that keeps your log after Get a Project, then switch the scenario on. Every new run now leaves a trace without you watching.

Triggers

What starts a ParseHub scenario

1 module starts a scenario when something happens in ParseHub. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ParseHub as soon as it happens.

ParseHub1Watch Runs

Watch Runs

Instant trigger

In Make“Triggers when a new run is started in a project.”

Watch Runs starts your scenario each time a new run begins in one of your ParseHub projects, so you know a scrape is underway without refreshing the dashboard.

How it fires
it is instant: ParseHub calls Make through a webhook as soon as the run starts, with no polling interval to wait for.
When to use it
to log each run, alert a colleague that fresh collection is in progress, or chain a check with Get a Run.
Watch out
it fires at the start of a run, not at the end, so the extracted data is not ready at that moment.
Modules

Every ParseHub module, explained simply

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

ParseHub1

Cancel a Run

Action

In Make“Cancels a run and changes its status to cancelled.”

Cancel a Run stops a run that is in progress and switches its status to cancelled, so ParseHub stops working on a job you no longer need.

When to use it
a condition in another app says the scrape is no longer useful, for example the page it targets was already processed.
Watch out
it only changes the status; to remove the run and its data too, Delete a Run is the module you want.
ParseHub2

Delete a Run

Action

In Make“Cancels and deletes a run and its data.”

Delete a Run goes further than cancelling: it stops the run and wipes it together with everything it extracted, which keeps your project history lean.

When to use it
after you have copied the results elsewhere and no longer want the run in ParseHub.
Watch out
there is no undo, so fetch the data with Get Data For a Run before this step.
ParseHub3

Get a Project

Action

In Make“Gets a detail of a project in an account.”

Get a Project returns the details of one project in your account, handy when the next module needs more than a bare identifier to make sense of a run.

When to use it
right after Watch Runs, to attach the project's information to each run you record or announce.
Watch out
it reads one project; to go through all of them, start with List Projects.
ParseHub4

Get a Run

Action

In Make“Returns the run object for a given run token.”

Get a Run looks up one run from its token (the identifier of that run) and returns the record ParseHub keeps for it, so your scenario can decide what comes next.

When to use it
after Run a Project, to see where the run you launched stands before pulling anything from it.
Watch out
it describes the run, not its results; for the scraped content, use Get Data For a Run.
ParseHub5

Get Data For a Run

Action

In Make“Returns the data that was extracted by a run.”

Get Data For a Run brings back what a specific run actually extracted, the scraped content itself, ready to be mapped into a sheet, a CRM or a message.

When to use it
you know exactly which run you want, for instance the one your scenario started a few modules earlier.
Watch out
a run that is still going has nothing complete to return, so look it up with Get a Run first.
ParseHub6

Get Last Ready Data

Action

In Make“Returns the date for the most recent ready run for a project.”

Get Last Ready Data points at a project rather than a run and goes to its most recent ready run, which saves you from tracking run tokens at all.

When to use it
another app asks for the latest results of a project and does not care which run produced them.
Watch out
if a newer run is still in progress, you get the previous ready one, not the one underway.
ParseHub7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you call any endpoint of the ParseHub API that the other nine modules do not cover, using the connection you already set up.

When to use it
you found an operation in the ParseHub API documentation that has no dedicated module in Make.
Watch out
you write the request yourself, so read the vendor documentation before mapping anything into it.
ParseHub8

Run a Project

Action

In Make“Starts running an instance of a project on the ParseHub cloud.”

Run a Project starts a new instance of one of your projects on the ParseHub cloud, so a scrape can kick off from any event in another app.

When to use it
a new row, a form reply or a message in another tool means fresh data is needed now.
Watch out
the run begins right away but takes its own time to finish; collect results later with Get Data For a Run or Get Last Ready Data.
ParseHub9

List Projects

Search

In Make“Retrieves a list of all projects in an account.”

List Projects retrieves every project in your ParseHub account and sends each one as its own bundle to the modules that follow.

When to use it
to build an inventory of your projects, or to loop an action such as Get Last Ready Data over each of them.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per project, which adds operations.
Need help

Need help automating ParseHub with Make?

A person reads every message.

FAQ

ParseHub and Make: common questions

01Is the ParseHub Make integration free?
Yes, on the Make side. ParseHub is a standard app, available from the Free plan like the other 3,000+ standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled executions, 5 minutes of execution at most and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, where each operation is one module running on one bundle. ParseHub itself needs an active account; its own pricing page covers the subscription.
02What do you need to connect ParseHub to Make?
An active ParseHub account and its API key. In ParseHub, click the profile icon in the left sidebar of the dashboard and copy the key from the Account Settings panel. In Make, add a ParseHub module, click Create a connection, give it a name if you like, and paste the key. If your first module is Watch Runs, Make asks you to click Create a webhook before the connection. After that, the same connection serves all 10 ParseHub modules in every scenario you build.
03Does the ParseHub trigger in Make react instantly?
Yes. Watch Runs is an instant trigger: ParseHub calls Make through a webhook as soon as a new run starts in a project, so your scenario does not wait for a schedule. Keep in mind what it watches, though. It reports the start of a run, not its end, so the scraped data is not available yet at that moment. To act on finished results, add Get a Run to look up the run, or use Get Last Ready Data in a scenario that starts from another event.
04What if a ParseHub module is missing in Make?
Use Make an API Call. It reaches any endpoint of the ParseHub API from your scenario with the connection you already have, so an operation without its own module is still within reach. You write the request yourself, which means reading the ParseHub API documentation first. Also note that Make's page for this app says it was produced with AI help from the official ParseHub documentation and may contain mistakes, so double check anything critical with ParseHub before relying on it.
05Should you use Make or n8n for ParseHub?
It depends on which tool your team already works in. On Make, ParseHub comes with 10 ready modules, an instant trigger for new runs and Make an API Call for the rest, all available from the Free plan. The same app often has an n8n node as well, so check the node list there before deciding. Compare what each side offers for your exact steps, such as starting a project or pulling run data, and choose the one where those steps exist without extra work.
Same platform

Other docs you might need on this stack.

Browse all integrations