Make logoMake
Automation

Add a Vindaris module to a scenario, and your other apps create goals and update KPIs.

Make connects apps into visual scenarios. Add a Vindaris module to a scenario and those apps can create and update goals, projects, KPIs and tasks in your workspace, and post comments, so a signed contract or a filled form lands on the plan without anyone retyping it.

Automate Vindaris with Make
Writes
Create and update goals, projects, KPIs and tasks, and post comments.
Build
Add a Vindaris module to any Make scenario.
Scope
Updates only ever touch the objects that connection created.
Auth
Authorize with your Vindaris login when the scenario first runs.
What the Vindaris module does

The module creates work in Vindaris, then keeps what it made current.

Drop the Vindaris module into your scenario and choose what it should do. It can open a new goal, project, KPI or task, update one it created on an earlier run, or post a comment, all driven by the data the scenario already carries.

Create goals, projects, KPIs and tasks

A Vindaris module can open any of these in your workspace from the data a scenario carries, so a new deal or a new project kicks off the matching work in Vindaris.

Update what the connection created

The same module can update an object it made on an earlier run, moving a KPI value or a task status as the source app changes.

Updates stay inside the connection

An update only ever changes an object this Make connection created. Work your team created by hand in Vindaris is never edited by a scenario.

Post comments onto the right item

A scenario can post a comment onto a goal, project, KPI or task, so a note from the source app shows up in the discussion on the item it belongs to.

Driven by the apps you already run

Make reaches a wide catalog of apps. Any of them can start the scenario, so the data that creates and updates Vindaris work begins where your team already works.

Authorized with your Vindaris account

The first run opens the Vindaris login so you authorize the connection. The scenario then acts within the access your account already has.

How the connection works

Build the scenario, then drop in the Vindaris module.

You set this up in Make, not in Vindaris. The Vindaris module is one of the steps you add to a scenario, and it authorizes itself against your workspace the first time it runs.

01
Build a scenario in Make

Start from any trigger Make supports, such as a new CRM deal or a submitted form your team already uses.

02
Add the Vindaris module

In the module step, choose the Vindaris app and pick what it should do: create or update a goal, project, KPI or task, or post a comment.

03
Sign in to authorize

The first time the step runs, Make opens the Vindaris login. Authorize it once and the connection is reused on every later run.

04
Map the fields and turn it on

Point the scenario's data at the Vindaris fields, then switch the scenario on. From then on the module runs on its own.

Alignment Canvas

The goals a scenario opens land on the canvas.

A goal or KPI created through Make appears on the alignment canvas with everything else, so work that started in another app is mapped into the strategy from the moment it arrives.

A goal created through Make shown on the Vindaris alignment canvas
Task board

A task from a scenario is tracked like any other.

Once the module creates a task, Vindaris tracks it the same way it tracks work created by hand, so a task opened by a scenario counts toward the goal above it.

A task created by a Make scenario on the Vindaris task board
Why it matters

The deal closes in the CRM, and the plan never hears about it.

A contract gets signed in the CRM. A project gets greenlit in a form. The event that should start work in Vindaris happens somewhere else, and someone has to remember to open the goal or the task by hand, which is exactly the step that gets skipped when a quarter is busy.

A scenario removes that step. The source app that already knows a deal closed can create the goal or open the task in Vindaris the moment it happens, and because an update only touches what the connection created, the automation keeps its own work current without ever disturbing what your team set up.

Related

Where to go next

Developers
Automation API reference
The endpoints, fields, and errors behind the Zapier and Make apps.
Solution
Goal tracking software
Progress derived from work activity instead of a status field.
Use case
Automated status reporting
Build the weekly review from work data, not from chasing owners.
Frequently asked questions

Make and Vindaris, answered

How do I connect Make to Vindaris?

You connect it from Make, not from inside Vindaris. Build a scenario, add a Vindaris module, and Make opens the Vindaris login so you can authorize the connection. From then on that scenario can write to your workspace.

What can the Vindaris module do?

It can create and update goals, projects, KPIs and tasks, and post comments. An update only ever changes an object that the same connection created earlier, so a scenario never edits work it did not make.

Can a scenario read data out of Vindaris?

Not yet. The integration writes into Vindaris today, so there are no triggers that start a scenario from a Vindaris change. Creating and updating goals, projects, KPIs and tasks, and posting comments, is what the module supports.

Will a scenario change a goal my team created by hand?

No. A Vindaris module updates only the objects that same connection created through Make. Goals, KPIs and tasks you create in Vindaris stay untouched by the scenario.

Let the apps that start the work open it in Vindaris.

Add a Vindaris module to your first scenario in a couple of minutes. Free forever for goal management, two integrations included.

Automate Vindaris with Make

No credit card | No migration | Nobody leaves Make