Resources · Make integration

ProofHub Make integrationAutomate ProofHub with Make.

What if new requests turned into ProofHub tasks without anyone retyping them? The ProofHub Make integration gives you 18 modules for tasks, subtasks and comments. This guide walks project leads through the connection, a first scenario and every module.

Try the ProofHub integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ProofHub Make integration do for your projects?

The ProofHub Make integration links your ProofHub account to Make so a scenario, the automation you build as a chain of bricks called modules, can create, read, change, move, copy and delete tasks, subtasks and comments for you. You set it up once with an API key, and no code is involved.

Requests become tasks on their own. A form entry or an email in another app starts the scenario, Create a Task files the work in ProofHub, and Create a Subtask breaks it into steps so nobody rebuilds the same checklist by hand.

Statuses stay in sync. When a deal closes or a ticket is resolved elsewhere, Search Tasks finds the matching task and Update a Task or Move a Task puts it where it belongs. Pair this with Create a Comment to leave a trace your team will read.

Kickoffs start from a model. Keep one well-written task as a template and let Copy a Task duplicate it each time a new client signs.

One thing Make does not offer here: ProofHub has no trigger module, so ProofHub itself cannot start a scenario. You launch it from another app or on a schedule. Make also flags its ProofHub documentation as AI-generated, so check anything critical with ProofHub. New to the editor? The Make training covers the basics, Make troubleshooting helps when a run fails, and n8n vs Make compares the two tools if you are still choosing.

Connect

How do you connect your ProofHub account to Make?

  1. 01

    Copy your ProofHub API key

    In ProofHub, click the profile icon in the bottom left corner, choose API access in the menu, then copy the key shown in the window that opens. Keep it at hand for the next step.

  2. 02

    Add a ProofHub module

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, paste the API key you copied, and confirm. Make can now read and write in your ProofHub account.

First scenario

Your first scenario with ProofHub and Make

GoalWhen a new request lands in another app, Make creates a ProofHub task and adds a first comment to it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your requests arrive, since ProofHub has no trigger of its own.

  2. 02

    Add Create a Task

    Click the + on the right of that first module, search for ProofHub and choose Create a Task. Click Create a connection and paste your API key if you have not linked ProofHub yet.

  3. 03

    Map the request into the task

    Fill the module fields. Make lists what it can read in ProofHub once the connection exists, and you drag values from the first module, such as the request title, into the task.

  4. 04

    Add Create a Comment

    Click the next + and add Create a Comment. Map the task the previous module just created, then write the comment, for example the full request text or who sent it.

  5. 05

    Test with Run once

    Click Run once and send a test request. Each module shows the bundles it received, a bundle being one item passed along, so you can check the task and its comment in ProofHub.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From then on, each request becomes a commented task without anyone copying it over.

Modules

Every ProofHub module in Make, explained

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

ProofHub1

Copy a Task

Action

In Make“Copies an existing task.”

Duplicates a task that already exists, so a carefully written model becomes a fresh task in one step instead of being rewritten.

When to use it
a new client signs and the onboarding task you polished should appear again for this account.
Watch out
keep the source task clean, since every copy inherits what it contains.
ProofHub2

Create a Comment

Action

In Make“Creates a new comment.”

Posts a comment on ProofHub content, which leaves a readable trace for the team right where they already work, without an extra message elsewhere.

When to use it
an invoice gets paid or a customer replies in another tool, and the people on the task should see it.
Watch out
map the right task from an earlier module, otherwise the note lands in the wrong place.
ProofHub3

Create a Subtask

Action

In Make“Creates a new subtask.”

Adds a subtask under an existing task, turning one broad job into smaller steps people can tick off one by one.

When to use it
right after Create a Task, to split a website request into copy, design and review.
Watch out
the parent task has to exist first, so place this module after the one that creates or finds it.
ProofHub4

Create a Task

Action

In Make“Creates a new task.”

Creates a new task in ProofHub, which is how outside events become work your team can see, assign and track.

When to use it
a form submission, a support email or a signed quote in another app should land as a task without retyping.
Watch out
if the source can send the same item twice, check with Search Tasks first to avoid duplicates.
ProofHub5

Delete a Comment

Action

In Make“Deletes an existing comment.”

Removes an existing comment, handy for clearing automatic notes that no longer make sense once a situation has changed.

When to use it
a scenario posted a status comment that turned out to be wrong and the correction should replace it.
Watch out
a deletion cannot be undone from Make, so test with Run once on a dummy comment before switching the scenario on.
ProofHub6

Delete a Subtask

Action

In Make“Deletes an existing subtask.”

Erases a subtask from its task, which keeps checklists short when a step stops applying to the job.

When to use it
a client drops an option from the order, and the matching subtask should disappear from the plan.
Watch out
treat the deletion as final and pick the subtask with care, ideally through Search Subtasks.
ProofHub7

Delete a Task

Action

In Make“Deletes an existing task.”

Deletes a whole task, the heaviest cleanup move in this app, and the one to reserve for work that truly vanished.

When to use it
a deal is cancelled in your CRM and the task created for it has no reason to stay.
Watch out
nothing brings it back from Make; if you might need it later, Move a Task takes it out of the way while keeping it in ProofHub.
ProofHub8

Get a Comment

Action

In Make“Retrieves an existing comment.”

Fetches one precise comment and passes its content to the next modules, so its text can travel to another tool.

When to use it
you already know which comment matters, for example one stored earlier in the scenario, and need its latest wording.
Watch out
it reads a single comment you point it to; to browse several, Search Comments is the right module.
ProofHub9

Get a Subtask

Action

In Make“Retrieves an existing subtask.”

Reads one subtask in full, giving later modules its current details to decide what happens next.

When to use it
before changing a step, you want to check its present state so the scenario only acts when it should.
Watch out
this module needs to know exactly which subtask to open, so map it from an earlier module rather than guessing.
ProofHub10

Get a Task

Action

In Make“Retrieves an existing task.”

Brings back the details of a single task, which is useful when another tool needs to show or reuse what ProofHub holds.

When to use it
a client portal or a report should display the live state of one known task.
Watch out
if you only have a name and not the task itself, start with Search Tasks and feed its result here.
ProofHub11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the ProofHub API with the connection you already set up, the way to reach features the listed modules skip.

When to use it
you need something in ProofHub that none of the other ProofHub modules handles.
Watch out
you write the request yourself, so read the ProofHub API reference first and test with Run once.
ProofHub12

Move a Task

Action

In Make“Moves an existing task.”

Relocates an existing task so it shows up where your team expects it, without recreating it.

When to use it
work passes from sales to delivery and the task should follow into the right place.
Watch out
moving keeps the task in ProofHub, a softer choice than Delete a Task when you just want it out of the way.
ProofHub13

Update a Comment

Action

In Make“Updates an existing comment.”

Edits the text of a comment already posted, so a status note can stay current instead of piling up new versions.

When to use it
a scenario keeps one progress comment per task and rewrites it whenever the figure it reports changes.
Watch out
readers see the new wording only, so avoid this when the team needs a record of each change.
ProofHub14

Update a Subtask

Action

In Make“Updates an existing subtask.”

Changes a subtask in place, which lets a step reflect what happened elsewhere without anyone opening ProofHub.

When to use it
a file is approved in your review tool and the related subtask should show it.
Watch out
point it to the right subtask from an earlier module, then check the result with Run once before going live.
ProofHub15

Update a Task

Action

In Make“Updates an existing task.”

Modifies an existing task, the everyday module for keeping ProofHub in step with the rest of your tools.

When to use it
a deadline shifts in the client thread and the task should carry that change without manual edits.
Watch out
each run costs an operation, one execution of one module, so filter upstream to update only tasks that really changed.
ProofHub16

Search Comments

Search

In Make“Searches for comments or lists them all.”

Looks for comments, or lists them all, and sends each match on as its own bundle to the following modules.

When to use it
you want to copy every comment of a task into a document or a report.
Watch out
a search can return zero, one or many results, and each result triggers the next modules once, which counts operations.
ProofHub17

Search Subtasks

Search

In Make“Searches for subtasks or lists them all.”

Finds subtasks, or lists every one of them, which gives you the steps to review, update or clean up afterwards.

When to use it
before closing a task, you want to see which of its steps remain open.
Watch out
it can return nothing at all, so test with Run once the case where no subtask matches.
ProofHub18

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Searches tasks, or lists all of them, and is usually the first ProofHub module in scenarios that change existing work.

When to use it
another app gives you a client name and you need the matching task before updating or moving it.
Watch out
several tasks may match, and the modules after it will run for each one, so narrow the search well.
Need help

Need help automating ProofHub with Make?

A person reads every message.

FAQ

ProofHub and Make: frequent questions

01Is the ProofHub Make integration free?
Yes, on the Make side. ProofHub is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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) lower the interval to 1 minute and remove the cap on active scenarios. You still need an active ProofHub account with its own subscription, which ProofHub handles on its pricing page.
02What is needed to connect ProofHub to Make?
Two things: an active ProofHub account and its API key. To find the key, click the profile icon in the bottom left corner of ProofHub, choose API access, and copy the key shown in the window. Then add any ProofHub module in Make, click Create a connection, optionally name it, and paste the key. That connection is reused by all 18 ProofHub modules, so you only do this once per account.
03Does the ProofHub Make integration react in real time?
No. ProofHub has no trigger module in Make, so nothing in ProofHub can start a scenario by itself. You have two ways around it. Start the scenario with a trigger from another app, such as a form or a CRM, and then act in ProofHub. Or let the scenario run on its schedule, every 15 minutes by default, with Search Tasks as the first step to go through your tasks and act on the ones you need. On paid plans the interval can go down to 1 minute.
04What if a ProofHub module is missing in Make?
Use Make an API Call. It reaches any endpoint of the ProofHub API with the same connection as the other modules, so you can cover features the listed actions and searches do not. You will need to read the ProofHub API reference to build the request. Also keep in mind that Make labels its ProofHub documentation as AI-generated and possibly inaccurate, so confirm with ProofHub any behavior your scenario depends on.
05Should you pick Make or n8n for ProofHub?
It depends on what you need to automate. Make offers 18 ProofHub modules covering tasks, subtasks and comments, plus the API call module, and no ProofHub trigger. If those modules match your case, Make lets you build it visually from the editor. Before deciding, check whether n8n offers a ProofHub node and what it covers, then compare both on your own scenario rather than on general claims. The n8n vs Make comparison linked above lists the criteria to weigh.
Same platform

Other docs you might need on this stack.

Browse all integrations