Resources · Make integration

vPlan Make integrationAutomate vPlan with Make.

Can Make keep your vPlan boards and cards in step with the rest of your tools? The vPlan Make integration offers 57 modules, including 5 triggers. This guide is for planners and ops leads: connect the account, build a first scenario, then pick the right module.

Try the vPlan integration on MakeSee the 57 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the vPlan Make integration let you automate?

The vPlan Make integration links your vPlan account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule. Each module is one brick of that chain, and vPlan brings 57 of them, from watching events to creating cards and orders.

Work requests that land as cards. A request typed into a form or another app becomes a vPlan card through Create a card, and Create a comment adds the context the requester gave. Nobody retypes anything.

Orders that carry their own lines. Create an order followed by Create an order row builds the order and its details in one run, from data that already exists elsewhere, such as a quote accepted in your sales tool.

A log of what moves in vPlan. Watch updated events or Watch deleted events feeds each change to the next module, so a shared sheet or a team channel keeps a trace of every edit.

What Make will not do here: every vPlan trigger is scheduled, so nothing reacts the second a change happens, and Make's vPlan documentation is flagged as AI-generated from vPlan's own docs, so check important details against vPlan itself. The same app may also exist as an n8n node; the n8n vs Make page lays out how the two tools differ. Before you commit, the Make review and the Make pricing page help you size the plan.

Connect

How do you connect vPlan to Make?

  1. 01

    Create the key in vPlan

    In vPlan, open Settings in the side menu, then API Keys, and click ADD KEY. Copy the API key and the API env shown on screen: Make asks for both. An OAuth 2 app registration also works if your team prefers it.

  2. 02

    Add a vPlan module in Make

    In your scenario, click the +, search for vPlan, pick any module and click Create a connection. A connection is your vPlan account linked to Make once, then reused by every vPlan module you add later.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when several people share the Make team. Paste the key and the env you copied, or follow the instructions on screen, then save.

First scenario

Your first scenario: turn a request into a vPlan card

GoalWhen a request arrives in another app, Make creates a vPlan card and adds a comment with the details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app where requests arrive, such as your form tool.

  2. 02

    Add Create a card

    Click the + on the right of that first module, search for vPlan and choose Create a card. Click Create a connection if you have not linked vPlan yet.

  3. 03

    Map the request into the card

    Fill the fields of Create a card with data from the first module. Once connected, Make lists the vPlan items it can read, so you pick them instead of typing them.

  4. 04

    Add Create a comment

    Add a third module, Create a comment, and map the card that Create a card just returned, plus the details from the request, so the context sits on the card.

  5. 05

    Test with Run once

    Click Run once and send one test request. Each module shows the bundles it received, one bundle per item, so you can confirm the card and comment look right.

  6. 06

    Schedule and switch on

    Open Scheduling on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan) and switch the scenario on.

Triggers

What can start a vPlan scenario?

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

vPlan1Watch all events

Watch all events

triggerIn the docs only

Watch all events gives you one trigger that starts the scenario for any kind of event vPlan reports, whether something was created, updated, attached or deleted.

How it fires
scheduled. Make checks vPlan on the scenario's schedule and passes each new event to the next module as a bundle.
When to use it
an audit trail where every movement in vPlan should land in one shared sheet or channel.
Watch out
every event costs an operation (one run of one module on one bundle) in each following module; if only one kind of event matters, a narrower Watch module keeps the count down.
vPlan2Watch attached events

Watch attached events

triggerIn the docs only

Watch attached events picks up the events of the "attached" kind. Make gives no description, so this is a reading of the name: most likely something attached in vPlan, such as a file, that can travel on to your other tools.

How it fires
scheduled. Make checks vPlan on the scenario's schedule, not the moment the attachment appears.
When to use it
when a document added to vPlan should also be announced to the team or copied to a shared storage app.
Watch out
the module name is the only description Make gives, so run it once on a real attachment and read the bundle before you build on it.
vPlan3Watch created events

Watch created events

triggerIn the docs only

Watch created events hands you each new item as soon as Make notices it, which makes it the natural start for anything that begins with "something new appeared in vPlan".

How it fires
scheduled. Make checks vPlan on the scenario's schedule, every 15 minutes by default.
When to use it
a new card or order in vPlan should open a task, send a message or add a row somewhere else.
Watch out
if the same scenario also creates items in vPlan, it can pick up its own work on the next check; send new items to another app instead.
vPlan4Watch deleted events

Watch deleted events

triggerIn the docs only

Watch deleted events tells you what disappeared from vPlan, so a removal leaves a trace in another tool instead of vanishing silently.

How it fires
scheduled. Make checks vPlan on the scenario's schedule and returns the deletions it finds since the last check.
When to use it
a manager wants to know when planned work is removed, or a mirror sheet should drop the same line.
Watch out
the item is already gone in vPlan, so a Get module placed after this trigger has nothing left to fetch; use what the bundle itself carries.
vPlan5Watch updated events

Watch updated events

triggerIn the docs only

Watch updated events catches the changes made to existing vPlan items, which is what you need to keep another tool in step with the planning.

How it fires
scheduled. Make checks vPlan on the scenario's schedule and returns each update as a separate bundle.
When to use it
a customer or a colleague needs to hear about a change without opening vPlan.
Watch out
an Update module later in the same scenario changes vPlan again, and the next check sees that change too; keep the scenario's output outside vPlan to avoid a loop.
Modules

What can vPlan do inside a scenario?

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

vPlan1

Create a board

ActionIn the docs only

Create a board sets up a new board in vPlan from your scenario, so a new project or team gets its planning space without anyone clicking through the setup.

When to use it
a signed deal or a new project record in another tool should come with its own board in vPlan.
vPlan2

Create a card

ActionIn the docs only

This is the module that turns outside data into planned work: Create a card adds a card in vPlan, filled with what earlier modules passed along.

When to use it
a form entry, a support ticket or an email should become a card instead of a note someone copies by hand.
Watch out
run once with one test item before switching on, or every bundle creates its own card.
vPlan3

Create a collection

ActionIn the docs only

You get a new collection in vPlan the moment the scenario reaches this module, filled from the data mapped into its fields.

When to use it
a batch of work arrives from another system and deserves its own collection, which you can later place on a board with Plan a collection on a board.
vPlan4

Create a comment

ActionIn the docs only

Create a comment writes a comment into vPlan, which keeps the conversation about the work next to the work itself.

When to use it
just after Create a card, to paste the original request, or when a reply in another tool should be visible to planners.
Watch out
the module needs to know which item it comments on, so map it from an earlier module.
vPlan5

Create a resource

ActionIn the docs only

A new resource appears in vPlan without manual entry: Create a resource adds it from the data your scenario already holds.

When to use it
someone joins the team in your HR tool, or a machine is added to an inventory sheet, and planners need to see it in vPlan too.
vPlan6

Create an activity

ActionIn the docs only

Create an activity records a new activity in vPlan, so the planning reflects what has to happen next without a second round of typing.

When to use it
a step in another tool, a booking or an approval for instance, should show up as an activity for the people who plan the week.
vPlan7

Create an attachment

ActionIn the docs only

With Create an attachment, a file that already travels through your scenario ends up attached in vPlan, where the team will look for it.

When to use it
a drawing, a quote or a photo arrives by email or in cloud storage and belongs with the related planning item.
Watch out
on the Free plan Make handles files up to 5 MB.
vPlan9

Create an order

ActionIn the docs only

Create an order opens a new order in vPlan straight from your scenario, which saves rekeying data that already exists in your sales or ERP tool.

When to use it
a quote is accepted elsewhere and production or delivery planning should start from it.
Watch out
the order lines come separately, through Create an order row placed right after.
vPlan10

Create an order row

ActionIn the docs only

Each run of Create an order row adds one line to an existing vPlan order, which is how an order gets its detail.

When to use it
right after Create an order, once for each product or task the source document lists.
Watch out
map the order returned by the previous module, otherwise the row has nowhere to go.
vPlan11

Delete a board

ActionIn the docs only

Delete a board removes a whole board from vPlan, which keeps the workspace tidy when a project is really over.

When to use it
a project is archived or cancelled in your main tool and its board should not linger.
Watch out
treat the deletion as final and test on a throwaway board before pointing the module at real planning.
vPlan12

Delete a card

ActionIn the docs only

When work is cancelled at the source, Delete a card takes the matching card out of vPlan so the planning does not show ghosts.

When to use it
a ticket is closed as a duplicate or an order is withdrawn in another tool.
Watch out
make sure an earlier module points at the right card; one wrong mapping removes the wrong work.
vPlan13

Delete a collection

ActionIn the docs only

Delete a collection clears a collection out of vPlan once it no longer serves any purpose, without anyone hunting for it in the interface.

When to use it
the batch of work behind it was cancelled upstream.
Watch out
if you only want it off the board, Move a collection to the backlog is the gentler choice.
vPlan14

Delete a comment

ActionIn the docs only

Delete a comment removes one comment from vPlan, handy when a comment your scenario posted turns out to be wrong or outdated.

When to use it
a message was retracted in the source tool and its copy in vPlan should go too.
Watch out
Update a comment keeps the history cleaner when only the text changed.
vPlan15

Delete a resource

ActionIn the docs only

Delete a resource takes a resource out of vPlan so nobody plans work on someone who has left or on equipment that is gone.

When to use it
an offboarding in your HR tool or a retired machine in your inventory.
Watch out
check first with List resources that the scenario targets the right one.
vPlan16

Delete an activity

ActionIn the docs only

Delete an activity drops an activity from the vPlan planning, which frees the slot when the underlying event no longer happens.

When to use it
a booking is cancelled in another app and its activity should disappear with it.
Watch out
if the activity only moved, Update an activity keeps it and its links intact.
vPlan17

Delete an attachment

ActionIn the docs only

Delete an attachment removes a file or link attached in vPlan, so an outdated document stops circulating among planners.

When to use it
a new version of a quote or drawing replaces the old one, right after Create an attachment adds the new file.
Watch out
run once and read the bundle to confirm which attachment the scenario targets.
vPlan18

Delete an order

ActionIn the docs only

Delete an order takes an order out of vPlan when it was cancelled at the source, so production does not plan work that nobody will pay for.

When to use it
a customer withdraws a purchase in your sales tool.
Watch out
treat it as final; a status change through Update an order is safer when the order may come back.
vPlan19

Delete an order row

ActionIn the docs only

Delete an order row trims one line from a vPlan order while the rest of the order stays in place.

When to use it
the customer drops one item from a quote, and the same change should reach the planning.
Watch out
List order rows first if you need to find which row matches the dropped item.
vPlan20

Get a board

ActionIn the docs only

Get a board fetches one board from vPlan and hands its details to the next modules, so they can reuse what vPlan already knows.

When to use it
you already know which board you need, for example from a trigger, and want its full data before writing elsewhere.
Watch out
to browse several boards, List boards is the module to use.
vPlan21

Get a card

ActionIn the docs only

You receive the full record of one vPlan card, ready to map into a message, a sheet or another module further down.

When to use it
a trigger such as Watch updated events tells you something changed, and you need the card's current content before acting.
Watch out
Get a card reads one known card; List cards is for finding them.
vPlan22

Get a collection

ActionIn the docs only

Get a collection brings one collection's details from vPlan into the scenario, so later modules work from fresh data instead of guesses.

When to use it
before Plan a collection on a board or Update a collection, to check what the collection currently holds.
Watch out
it reads the collection itself; List collection cards returns the cards inside it.
vPlan23

Get a comment

ActionIn the docs only

Get a comment reads one comment from vPlan so its text can be forwarded, quoted or stored somewhere else.

When to use it
a trigger reports new activity and you want to pass the exact wording of a comment to a colleague who does not use vPlan.
Watch out
to read every comment, use List comments.
vPlan24

Get a resource

ActionIn the docs only

Get a resource pulls one resource's details out of vPlan, useful when a message or a report needs to name the person or the equipment involved.

When to use it
after a trigger or a list, when you have one resource in hand and need its full record.
Watch out
List resources is the better start when you do not know which one yet.
vPlan25

Get an activity

ActionIn the docs only

Get an activity returns the current state of one vPlan activity, so a reminder or a customer update carries the right information.

When to use it
a trigger signals a change and you want the activity's latest version before notifying anyone.
Watch out
the module reads one activity at a time; List activities returns several.
vPlan26

Get an attachment

ActionIn the docs only

Get an attachment fetches one attachment from vPlan so the scenario can pass it on to a mailbox, a drive or a client portal.

When to use it
Watch attached events fires and you want the attachment itself, not only the event about it.
Watch out
on the Free plan Make handles files up to 5 MB.
vPlan27

Get an order

ActionIn the docs only

Get an order brings one vPlan order into the scenario with its details, ready to feed an invoice, a delivery note or a status message.

When to use it
a trigger reports a change on an order and your finance or logistics tool needs the current version.
Watch out
the lines are separate; add List order rows to read them.
vPlan28

Get an order row

ActionIn the docs only

Get an order row reads a single line of a vPlan order, which is enough when only one item matters to the next step.

When to use it
you have one row in hand from a trigger or a list and need its full details before updating stock or sending a notice.
Watch out
for all lines of an order, List order rows is quicker.
vPlan29

Get info about connection

ActionIn the docs only

Get info about connection tells you what Make knows about the vPlan connection in use, which answers the question "which account is this scenario talking to?"

When to use it
while testing with Run once, or when several colleagues share connections and you want to check the right one is selected.
vPlan30

List activities

SearchIn the docs only

List activities gathers the vPlan activities in one pass, so the scenario can report on them or act on each one.

When to use it
building a digest of upcoming activities for a team channel, or checking activities before creating a new one.
Watch out
a search returns zero, one or many bundles, and each following module runs once per bundle.
vPlan31

List attachments

SearchIn the docs only

List attachments returns the attachments vPlan holds, so you can copy, check or clean them in bulk rather than one by one.

When to use it
backing files up to a shared drive, or finding the outdated attachment to remove with Delete an attachment.
Watch out
every file found becomes a bundle, which adds operations downstream.
vPlan32

List boards

SearchIn the docs only

List boards shows every board your vPlan connection can see, a quick way to find the one a scenario should work on.

When to use it
matching a project from another tool with its board, or feeding a report of all current boards.
Watch out
when it returns nothing, the following modules do not run at all.
vPlan33

List cards

SearchIn the docs only

List cards collects the cards from vPlan so a single scenario can review, export or update many of them.

When to use it
looking for the card that matches a ticket before creating a duplicate, or exporting cards to a spreadsheet.
Watch out
a large result multiplies operations, so connect only the modules you really need after it.
vPlan34

List collection cards

SearchIn the docs only

List collection cards returns the cards that belong to one collection, so you work on that batch without touching the rest of vPlan.

When to use it
a collection moves on a board and every card inside it needs the same update or the same message.
Watch out
map the collection from an earlier module first.
vPlan35

List collections

SearchIn the docs only

List collections lays out the vPlan collections, a starting point when the scenario must decide which batch to plan, move or report on.

When to use it
before Plan a collection on a board or Move a collection to the backlog, to find the right collection.
Watch out
each collection found is a separate bundle.
vPlan36

List comments

SearchIn the docs only

List comments brings back the comments stored in vPlan, so a whole discussion can be archived or passed to someone outside the tool.

When to use it
a project closes and its comments should be saved in a document or a shared drive.
Watch out
expect one bundle per comment, and plan your operations accordingly.
vPlan37

List order rows

SearchIn the docs only

List order rows reads the lines of vPlan orders, which is how an invoice or a picking list gets its full detail.

When to use it
right after Get an order, when finance or the warehouse needs every line.
Watch out
the rows arrive as separate bundles; to merge them into one document you need a Make tool that groups bundles, not a vPlan module.
vPlan38

List orders

SearchIn the docs only

List orders pulls the orders from vPlan into your scenario, a base for reports, reconciliations or bulk updates.

When to use it
checking vPlan orders against your ERP, or finding the order linked to a customer before creating a new one.
Watch out
no result means the rest of the scenario stops for that run, which is often what you want.
vPlan39

List resources

SearchIn the docs only

List resources returns every resource set up in vPlan, so your scenario can match them with records in other tools.

When to use it
syncing staff between vPlan and an HR tool, or finding the resource to update before Update a resource runs.
Watch out
each resource is its own bundle.
vPlan40

Make an API call

ActionIn the docs only

Make an API call lets you reach any endpoint of the vPlan API from the scenario, with the same connection as the other vPlan modules.

When to use it
the other vPlan modules do not cover what you need, and the vPlan API documentation describes the call that does.
Watch out
you build the request yourself, so read the vPlan API docs before sending anything that writes data.
vPlan41

Move a collection to the backlog

ActionIn the docs only

Move a collection to the backlog pulls a collection off its board and sends it back to the vPlan backlog, so the work stays on file but no longer holds a slot in the schedule.

When to use it
a customer postpones a job, and the planner needs that space freed as soon as the change is recorded elsewhere.
Watch out
the module handles one collection per run, so map its ID from a Watch or List module placed before it.
vPlan42

Plan a collection on a board

ActionIn the docs only

Plan a collection on a board places a collection from your backlog onto a board, which turns a waiting piece of work into something scheduled that the team can see.

When to use it
an order is confirmed in another tool and the job should land on the right board without anyone dragging it there by hand.
Watch out
this changes the live planning, so press Run once on a test board before switching the scenario on.
vPlan43

Update a board

ActionIn the docs only

Update a board edits an existing board in vPlan, keeping everything already planned on it while its details are brought up to date from your scenario.

When to use it
a team or a site is renamed in your HR or project tool and the matching board should follow.
Watch out
Make needs to know which board to change; List boards or Get a board earlier in the flow gives you its ID to map.
vPlan44

Update a card

ActionIn the docs only

Update a card changes a card that already exists, so the task a person sees in vPlan matches what just happened in the tool where the work is actually tracked.

When to use it
a ticket changes status in your support desk and the card linked to it should reflect that, rather than creating a duplicate.
Watch out
after List cards, every card returned is a separate bundle, and each update counts as one operation on your Make plan.
vPlan45

Update a card custom field

ActionIn the docs only

Update a card custom field writes a value into one of the custom fields you added to cards in vPlan, the extra information your team relies on that the standard card does not carry.

When to use it
a reference number or a customer tier lives in your CRM and should appear on the card without anyone retyping it.
Watch out
Make's vPlan documentation is flagged as AI-generated, so check the card in vPlan after your first Run once.
vPlan46

Update a collection

ActionIn the docs only

Update a collection brings an existing collection in line with the latest information, so the grouped work on your planning reflects the current state of the project behind it.

When to use it
a project is renamed or rescheduled in your project tool and the matching collection in vPlan should carry the change.
Watch out
do not start this scenario with Watch updated events on the same collection, or it will react to its own edit.
vPlan47

Update a collection custom field

ActionIn the docs only

Update a collection custom field sets the value of a custom field on a collection, the place where teams keep the project data vPlan does not track by default.

When to use it
a budget code or a contract reference is approved in your finance tool and should be stamped on the matching collection.
Watch out
if a field you need is not reachable here, Make an API call reaches the vPlan API with the same connection.
vPlan48

Update a comment

ActionIn the docs only

Update a comment rewrites a comment already posted in vPlan, handy when an automated note needs correcting instead of piling a second one underneath.

When to use it
a scenario posts a status note on a card and later has fresher news to put in that same note.
Watch out
keep the comment ID from Create a comment or List comments, because without it Make cannot tell which comment to edit.
vPlan49

Update a resource

ActionIn the docs only

Update a resource refreshes a resource in vPlan so the planning keeps working with its current details instead of whatever was entered when it was first set up.

When to use it
an employee record changes in your HR software and the matching resource in vPlan should carry the same information.
Watch out
Get info about connection confirms which vPlan account the scenario writes to before you touch real resources.
vPlan50

Update an activity

ActionIn the docs only

Update an activity adjusts an activity that already exists in vPlan so the step it describes stays accurate as the job moves forward in another tool.

When to use it
a field technician closes a task in a mobile app and the corresponding activity should show that progress.
Watch out
test with Run once and read the bundle each module received, which shows whether the right activity was targeted.
vPlan51

Update an order

ActionIn the docs only

Update an order keeps an order in vPlan aligned with its source, so production or service planning reads the same terms your sales side agreed on.

When to use it
a deal is amended in your CRM or ERP and the order already created in vPlan must follow, not be recreated.
Watch out
Make finds the order by its ID, which Get an order, List orders or Create an order earlier in the scenario can supply.
vPlan52

Update an order row

ActionIn the docs only

Update an order row edits a single line of an order, so one product or task changes while the rest of the order stays untouched.

When to use it
a quantity or a line description is corrected in the source system and only that row needs fixing in vPlan.
Watch out
List order rows returns every row as its own bundle, and each one you update uses an operation, so narrow the list first.
Need help

Need help automating vPlan with Make?

A person reads every message.

FAQ

Common questions about the vPlan Make integration

01Is the vPlan Make integration free?
Yes, on Make's side. vPlan is a standard app, available on every Make plan including Free. The Free plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes 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 count usage in credits each month. You still need an active vPlan subscription; its price is set by vPlan, not by Make.
02What do you need to connect vPlan to Make?
An active vPlan account and either an API key or an OAuth 2 app registration. For the key route, open Settings in vPlan, go to API Keys, click ADD KEY and copy both the API key and the API env shown on screen. Then, in Make, add any vPlan module, click Create a connection, give it a name if you like and paste the two values. The connection is reused by every vPlan module afterwards.
03Do the vPlan triggers in Make react in real time?
No. All 5 vPlan triggers are scheduled: Make checks vPlan on the scenario's schedule, shown by the clock badge on the first module, and picks up what happened since the last check. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the minimum, while paid plans go down to 1 minute. None of the vPlan triggers is instant, so there is no webhook to set up for them.
04What if a vPlan module is missing in Make?
Use the Make an API call module. It calls any endpoint of the vPlan API with the connection you already set up, so anything the API offers can be reached even when none of the listed modules covers it. Read the vPlan API documentation first to know which call to send, and test it with Run once before you switch the scenario on. Keep in mind that Make's vPlan documentation is flagged as AI-generated, so check important details with vPlan directly.
05Should vPlan be automated with Make or n8n?
It depends on what your team already uses. Make gives vPlan 57 ready modules, including 5 scheduled triggers and a generic API call, inside a visual editor. Many apps also have an n8n node; check whether one exists for vPlan and whether it covers the same operations before choosing. Compare the modules you actually need rather than the tool's reputation. The n8n vs Make comparison on this site sets out the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations