Resources · Make integration

Vestberry Make integrationAutomate Vestberry with Make.

Can Make keep your Vestberry portfolio data moving without copy and paste? The Vestberry Make integration gives you 18 modules: 5 triggers, 8 actions and 5 searches. This page explains each one in plain words, then walks you through a first scenario you can test right away.

Try the Vestberry integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Vestberry Make integration let you automate?

The Vestberry Make integration links your Vestberry account to Make, a no-code tool where you build a scenario (the automation itself) out of modules, one brick per step. Vestberry can start a scenario when notes, companies, reports, KPIs or files show up, and it can add companies, notes and files or read funds and metrics.

Reports that tell the team they exist. Watch New Portfolio Company Report spots a fresh report, and Add a Note to a Portofolio leaves a note on the portfolio so nobody has to announce it by hand.

A deal flow that feeds itself. When a deal closes in your CRM or a form comes in, Add a Portfolio Company creates the company in Vestberry, and Upload File attaches the documents that came with it.

Numbers where people read them. Watch Portfolio Company KPIs, Get a Metric For a Fund and Get a Metric For a Portfolio Company pull figures out of Vestberry so another app, such as a spreadsheet or a chat tool, can show them.

Be aware of one gap: Make's own documentation for Vestberry is limited, because little public information exists about the app. The module names are known, but their fields are not described. Expect to discover them in the editor once your connection is in place, and use Make an API Call for anything the listed modules leave out. If you are weighing tools, the n8n vs Make comparison sets them side by side, the Make training covers the editor from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Vestberry account to Make?

  1. 01

    Add a Vestberry module

    In a new scenario, click the big +, type Vestberry and pick any of its modules. Make then asks for a connection, which is your Vestberry account linked to Make once and reused by every Vestberry module after that.

  2. 02

    Create and name the connection

    Click Create a connection. Giving it a name is optional, but a clear one such as "Vestberry main fund" helps when several people or accounts share the same Make organization.

  3. 03

    Authorize and save

    Follow what Make shows next: either approve access on the Vestberry page that opens, or paste the key Vestberry gives you. Then click Save, and the module can start listing your Vestberry data.

First scenario

Your first scenario with Vestberry

GoalWhen a new portfolio company report appears in Vestberry, Make adds a note to the portfolio so the team sees it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes the first module, the one that starts everything.

  2. 02

    Add the report trigger

    Search for Vestberry, choose Watch New Portfolio Company Report and select your connection. Fill in what the module asks for; Make lists the objects it can read once the connection works.

  3. 03

    Add the note action

    Click the + on the right of the trigger and pick Add a Note to a Portofolio. Map data from the report into the note, so each note says which report just arrived.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one report. Check that the note reads well.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Triggers

Which Vestberry triggers can start a scenario?

5 modules start a scenario when something happens in Vestberry. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Vestberry as soon as it happens.

Vestberry1Watch New Notes

Watch New Notes

triggerIn the docs only

Watch New Notes starts your scenario whenever a new note is written in Vestberry, so the comment a partner leaves on a company can travel to the people who need it.

How it fires
scheduled: Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
your investment team writes meeting notes in Vestberry and the rest of the firm lives in a chat tool or a shared doc.
Watch out
do not pair it with Add a Note to a Portofolio in the same scenario, or every note you add will be picked up again as a new note.
Vestberry2Watch New Portfolio Companies

Watch New Portfolio Companies

triggerIn the docs only

With Watch New Portfolio Companies, each company added to Vestberry becomes the starting point of a scenario, which is handy for onboarding tasks you would otherwise remember by hand.

How it fires
scheduled: Make checks the app on the scenario's schedule, so a company appears at the next check rather than instantly.
When to use it
a fresh investment should open a folder, a task list or a record in your CRM without anyone asking.
Watch out
Make's documentation for this app is limited, so run it once and read the bundle to see which company details actually come through.
Vestberry3Watch New Portfolio Company Report

Watch New Portfolio Company Report

triggerIn the docs only

This trigger reacts to newly available portfolio company reports, which lets the numbers a founder sends reach your team without a manual heads up.

How it fires
scheduled: Make checks the app on the scenario's schedule; on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
reporting season, when you want each incoming report to trigger a note, a message or a review task.
Watch out
if you only need the list of recent reports at a given moment, List New Portfolio Company Report inside another scenario may fit better than a trigger.
Vestberry4Watch Portfolio Company KPIs

Watch Portfolio Company KPIs

triggerIn the docs only

Watch Portfolio Company KPIs hands your scenario the key figures tracked for your companies, so dashboards and alerts outside Vestberry stay in line with what the platform holds.

How it fires
scheduled: Make checks the app on the scenario's schedule and passes along what it finds as bundles.
When to use it
KPI values should land in a spreadsheet or a reporting tool that people outside Vestberry open.
Watch out
each KPI bundle that flows into later modules costs operations, so filter early if you only care about a few figures.
Vestberry5Watch for Files

Watch for Files

triggerIn the docs only

Watch for Files lets a document stored in Vestberry kick off the rest of your process, such as copying it to a drive or telling the deal team it is there.

How it fires
scheduled: Make checks the app on the scenario's schedule, not the moment the file is saved.
When to use it
legal papers or board decks are uploaded to Vestberry and another team needs a copy in the tool it already uses.
Watch out
the Free plan caps files at 5 MB per file, so large decks may need a paid plan.
Modules

What can Make do in Vestberry?

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

Vestberry1

Add a Note to a Portofolio

ActionIn the docs only

Your scenario can write a note straight onto a portfolio, so updates from email, forms or reports sit where investors look for context. The typo in the module name is Make's own.

When to use it
a report or a message elsewhere deserves a written trace next to the portfolio.
Watch out
keep it out of scenarios that start with Watch New Notes to avoid a loop.
Vestberry2

Add a Portfolio Company

ActionIn the docs only

Creating a company in Vestberry becomes one step of a scenario instead of a form you retype, which keeps the platform in sync with the tool where deals are closed.

When to use it
a deal marked as won in your CRM should appear as a portfolio company.
Watch out
search first with Search Portfolio Company if the same deal could reach the scenario twice.
Vestberry3

Get Notes

ActionIn the docs only

Get Notes brings the notes stored in Vestberry into your scenario, which is useful when a summary or an export has to include what the team already wrote.

When to use it
you build a digest for a partner meeting and want the notes on a given company in it.
Watch out
unlike Watch New Notes, it only reads when the scenario reaches it; it never starts anything.
Vestberry4

Get a Fund by ID

ActionIn the docs only

When you already hold a fund's identifier, this module returns that fund's record so later modules can use its details without a search.

When to use it
the ID came from an earlier module, a spreadsheet row or a webhook, and you need the matching fund.
Watch out
without the ID, start with Search Funds instead, since this module expects one precise identifier.
Vestberry5

Get a Metric For a Fund

ActionIn the docs only

This module reads one metric at fund level from Vestberry, the figure you would otherwise open the platform to copy into a slide or an update.

When to use it
an investor update or an internal dashboard needs a fund figure pulled at the moment the scenario runs.
Watch out
it targets a fund; for a single company's numbers, pick Get a Metric For a Portfolio Company.
Vestberry6

Get a Metric For a Portfolio Company

ActionIn the docs only

Here the metric belongs to one portfolio company, so you can drop a value for that company into a message, a sheet or a note without logging in.

When to use it
right after a report trigger, to fetch the figure the team discusses first.
Watch out
you need to point it at the right company, usually mapped from a trigger or from Search Portfolio Company.
Vestberry7

List New Portfolio Company Report

SearchIn the docs only

This search returns the recent portfolio company reports as a list, each report arriving as its own bundle, so you decide in the flow what to do with every one.

When to use it
a scenario started by something else, a form or a webhook, needs the latest reports at that moment.
Watch out
a list can hold zero, one or many reports, and every module after it runs once per report.
Vestberry8

List Portfolio Companies

SearchIn the docs only

List Portfolio Companies hands you the companies of your portfolio one bundle at a time, the base for any export or bulk update that touches all of them.

When to use it
you rebuild a company register in a spreadsheet or check each company against another system.
Watch out
a large portfolio multiplies operations in the modules that follow, so add a filter when you can.
Vestberry9

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Vestberry API with the connection you already set up, which covers what the other modules do not.

When to use it
the action or data you need has no dedicated module in this list.
Watch out
Make's documentation on Vestberry is limited, so you will need Vestberry's own API reference to know which endpoint and fields to send.
Vestberry10

Search Files

SearchIn the docs only

Search Files looks through the documents held in Vestberry and returns the matches, ready to be copied, shared or linked elsewhere.

When to use it
someone asks for a company's latest board pack and the scenario should find it rather than a person.
Watch out
like every search, it may return nothing or several files, so plan what happens in both cases.
Vestberry11

Search Funds

SearchIn the docs only

Search Funds finds funds in Vestberry when you do not know their ID yet, and passes each result on so later modules can read its metrics.

When to use it
ahead of Get a Metric For a Fund, when only the fund's name travels with your data.
Watch out
more than one fund can match, so check the bundles after Run once before mapping.
Vestberry12

Search Portfolio Company

SearchIn the docs only

This module finds an existing company in your portfolio, which lets the scenario reuse the right record instead of creating a twin.

When to use it
before Add a Portfolio Company, to test whether the company is already there.
Watch out
with zero results, later modules have nothing to work on, so plan what happens when the company is missing.
Vestberry13

Upload File

ActionIn the docs only

Upload File places a document from another app into Vestberry, so term sheets and reports arriving by email or cloud storage end up next to the right company.

When to use it
an attachment arrives in your inbox and belongs in Vestberry.
Watch out
on the Free plan, Make handles files up to 5 MB and 512 MB of data transfer in total.
Need help

Need help automating Vestberry with Make?

A person reads every message.

FAQ

Vestberry and Make: common questions

01Is the Vestberry Make integration free?
Yes, Vestberry is a standard app in Make, so its modules are available from the Free plan. That plan has limits: 2 active scenarios, at least 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 and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, per month. Your Vestberry subscription is a separate matter.
02What do you need to connect Vestberry to Make?
A Vestberry account and a Make account. Make's documentation lists no specific prerequisite and no official steps for Vestberry, so the generic flow applies: add a Vestberry module, click Create a connection, optionally name it, then either authorize Make on the Vestberry page or paste the key Vestberry provides, and click Save. The connection is then shared by every Vestberry module in your scenarios. If the authorization step asks for access you lack, the admin of your Vestberry account is the person to ask.
03Do Vestberry triggers in Make work in real time?
No. The 5 Vestberry triggers are listed as scheduled, which means Make checks Vestberry on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default, and that is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Note that this type comes from the module list, since Make's documentation for Vestberry is limited, so look for the clock badge on the module in the editor to confirm it.
04What if a Vestberry module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Vestberry API with the same connection as the other modules, so you are not limited to the 18 listed ones. The catch is documentation: Make explains that it cannot fully document Vestberry because little public information exists about the app, so the fields of each module are not described. Test each module with Run once to see what it returns, and rely on Vestberry's own API reference when you build a custom call.
05Should you use Make or n8n for Vestberry?
It depends on what you already run. On Make, Vestberry comes with 18 modules plus Make an API Call, a visual editor and plans that start free. Many apps also have an n8n node, but this page does not confirm one for Vestberry, so check the n8n side before deciding. Neither tool is ranked here. Compare the modules each offers for your exact use case, the way each counts usage, and which editor your team finds easier to maintain. The comparison page linked above lays the two out side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations