Resources · Make integration

Vitally Make integrationAutomate Vitally with Make.

Could your customer success tool fill itself while you talk to clients? The Vitally Make integration gives you 13 modules: 12 actions and 1 search. This guide is for CS and ops teams who want notes, tasks and user records written for them, from the first connection to a scenario that runs.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vitally Make integration do for your team?

The Vitally Make integration lets Make write into Vitally and read from it for you. In Make you build a scenario, the automation itself, out of modules: each module is one brick, such as creating a note or looking up a user. Vitally has no trigger in Make, so something else starts the scenario and Vitally receives the work.

A follow-up that never gets forgotten. When a deal closes in your CRM or a form comes in, Get a User by ID or Email finds the matching person in Vitally and Create a Task puts the next step on the account owner's list. Onboarding can go further with Create a Project from Template, which starts the same project plan for every new customer.

Feedback that lands where CSMs look. Survey answers collected elsewhere can become records through Create an NPS Response, and a comment from a support ticket can be saved with Create a Note, so the whole story sits on the customer's page.

Profiles that stay current. Update a Customer and Update a User push changes from your billing or product tools, while List Users pulls several users at once for a sync.

Know the limits before you start. There is no trigger, so Make cannot notice on its own that something changed in Vitally. The Make documentation for this app is short and flagged by Make as AI-generated, so test each module on real data with the button Make calls Run once. For anything the 13 modules skip, Make an API Call reaches the rest of the Vitally API. Pricing questions are covered in Make pricing, and if you are also looking at n8n, n8n vs Make lays out the criteria. To learn the editor step by step, see Make training.

Connect

How do you connect Vitally to Make?

  1. 01

    Copy your Vitally API key

    In Vitally, open the Settings section, then the API Access tab. The key is shown on screen: copy it and keep it at hand. Make needs it once, and every Vitally module in your scenarios will reuse it.

  2. 02

    Add a Vitally module in Make

    Log in to Make, open your scenario and add any Vitally module, for example Create a Note. In the module window, click Create a connection. A connection is your Vitally account linked to Make, saved for later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name such as the workspace you use helps when there are several. Paste the key you copied from Vitally, or follow the instructions Make displays to create the connection.

First scenario

Your first scenario: a Vitally task for each new signup

GoalWhen a new signup reaches another of your tools, Make finds that person in Vitally and creates a task for the account owner.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where signups arrive, such as your form tool or CRM. This first module starts everything, since Vitally has no trigger.

  2. 02

    Find the user in Vitally

    Click the + on the right, search for Vitally and choose Get a User by ID or Email. Select your connection, then map the email from the first module into the lookup.

  3. 03

    Add the task

    Add Create a Task after the lookup. Make lists what it can read once the connection exists; fill in the task and reuse the user's details received from the previous module.

  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. Open the new task in Vitally to check the result.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set the schedule: a new scenario runs every 15 minutes by default. Then switch the scenario on, and new signups will turn into tasks without you.

Modules

What each Vitally module does

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

Vitally1

Create a Message

Action

In MakeCreates a new message.

This module posts a new message in Vitally, so a conversation that happened in another tool also shows up next to the account. Your CSMs read one timeline instead of hopping between apps.

When to use it
a client emails the shared inbox and you want that exchange visible in Vitally too.
Watch out
the Make docs list no fields for it, so run it once and inspect what lands in Vitally before switching the scenario on.
Vitally2

Create an NPS Response

Action

In MakeCreates a new NPS response.

Survey scores gathered outside Vitally become proper NPS records with this action, which keeps your health view complete even when the survey tool is another product.

When to use it
your survey form collects answers, and each new answer should appear on the right customer in Vitally.
Watch out
every answer creates a record, so filter test submissions out upstream or your scores will be skewed.
Vitally3

Create a Note

Action

In MakeCreates a new note.

Need context saved on an account without typing it twice? Create a Note writes a new note in Vitally from whatever the earlier modules carried, such as a call summary or a ticket comment.

When to use it
a support ticket closes and the resolution should be readable by the CSM on the customer page.
Watch out
each operation, meaning one run of this module on one item, adds a note; group items first if you want one note, not ten.
Vitally4

Create a Project from Template

Action

In MakeCreates a new project from an existing template.

Onboarding starts the same way every time when this module opens a project in Vitally based on a template you already built there. Nobody has to copy the plan by hand.

When to use it
a contract is signed in your CRM and the new customer needs its onboarding plan straight away.
Watch out
the template must exist in Vitally first; Make only starts a copy of it and does not design the steps.
Vitally5

Create a Task

Action

In MakeCreates a new task.

With Create a Task, a to-do lands in Vitally for your team, built from data received from another app. It is the simplest way to turn a signal into an action someone owns.

When to use it
a usage drop is spotted in your product analytics and the account owner should call the client.
Watch out
without a filter before it, the scenario creates a task on every run, including repeats of the same event.
Vitally6

Get a Customer

Action

In MakeRetrieves a single customer.

Get a Customer brings back one customer account from Vitally so that later modules can use its details. Think of it as opening the account page, but inside the scenario.

When to use it
before sending a renewal reminder from another tool, you want the account data Vitally holds.
Watch out
it returns a single customer; when you need several people at once, List Users is the module that returns many.
Vitally7

Get an Admin

Action

In MakeRetrieves a single admin.

Admins in Vitally are the people on your side, such as the CSM who owns an account. This module fetches one of them, so the scenario knows who to notify or assign.

When to use it
a task or message must reach the right CSM, and you want their details from Vitally rather than a list kept elsewhere.
Watch out
do not confuse it with Get a User, which reads your customers' users, not your own team.
Vitally8

Get a User

Action

In MakeRetrieves a single user.

Here you retrieve one user record from Vitally, one person using your product at a client account. The details then flow to the next module in the scenario.

When to use it
you already have the Vitally reference of the person and just want their current record before updating it.
Watch out
if all you hold is an email or an ID from another system, Get a User by ID or Email is the better fit.
Vitally9

Get a User by ID or Email

Action

In MakeRetrieves a single user by external ID or email.

Other tools rarely know Vitally's own references, and this lookup solves that: it finds a single user from an external ID or an email address you already have.

When to use it
a form or CRM sends you an email, and you need the matching Vitally user before creating a task or updating the profile.
Watch out
test with an address that does not exist in Vitally too, and decide in the scenario what should happen when nothing is found.
Vitally10

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

When none of the 13 modules does what you need, Make an API Call reaches any endpoint of the Vitally API through the same connection. You get full coverage without new credentials.

When to use it
an object or action you rely on in Vitally has no ready-made module in Make.
Watch out
you write the request yourself, so keep the Vitally API reference open and test with Run once first.
Vitally11

Update a Customer

Action

In MakeUpdates existing customer's details.

Account data changes in billing or in your CRM, and this module carries that change onto the existing customer in Vitally. The team then reads the same facts in both tools.

When to use it
a client upgrades their plan in your billing tool and Vitally should reflect it.
Watch out
it edits a customer that already exists; put Get a Customer before it when you are not sure which account to target.
Vitally12

Update a User

Action

In MakeUpdates existing user's details.

Update a User rewrites the details of a person already in Vitally, for instance after they change role or email in your product. Profiles stay accurate without manual edits.

When to use it
your app records a change on a person and you want the Vitally user to match.
Watch out
map only the values you mean to change, and look the user up first with Get a User by ID or Email if you hold just an email.
Vitally13

List Users

Search

In MakeRetrieves a list of users.

Unlike the Get modules, List Users is a search: it returns several users, each as its own bundle, so every following module runs once per user.

When to use it
you want to push every Vitally user of an account to a sheet or to your email tool.
Watch out
each user returned costs operations in the modules after it; add a filter early when the list is long.
Need help

Need help automating Vitally with Make?

A person reads every message.

FAQ

Vitally and Make: common questions

01Is the Vitally Make integration free?
Yes, on the Make side. Vitally is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, and up to 5 minutes per execution, with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in credits, that is operations, per month. You still need your own Vitally subscription, which this page does not price.
02What does it take to connect Vitally to Make?
An active Vitally account and its API key. In Vitally, go to Settings, open the API Access tab and copy the key displayed there. In Make, add any Vitally module, click Create a connection, give it a name if you like and paste the key. That single connection is then reused by all 13 Vitally modules, so you do this step once per Vitally account. If Make rejects the key, go back to the API Access tab and copy it again in full.
03Can a Vitally scenario start by itself when something changes?
Not from Vitally. The app has no trigger module in Make, so it cannot tell Make that a record changed. The scenario has to start elsewhere: on a trigger from another app, like a form, a CRM or a billing tool, or on the schedule you set on the first module, every 15 minutes by default. Vitally then sits after that first module and receives the notes, tasks and updates. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute.
04What if a Vitally module is missing in Make?
Use Make an API Call. It is included for Vitally and can call any endpoint of the Vitally API with the connection you already set up, so you are not limited to the 12 actions and 1 search listed. Keep in mind that the Make documentation for this app is marked as AI-generated and may contain mistakes; when a detail matters, check it in Vitally's own documentation or ask Vitally directly.
05Make or n8n for Vitally: which one fits?
It depends on the tool your team already runs. Make offers 13 Vitally modules plus the API call module, with a visual editor and a Free plan to test. n8n is another automation tool, and many apps have a node there too; whether Vitally does is worth checking before you choose. Compare what each covers for your exact use case, since no ranking between the two applies to every team. The n8n vs Make comparison linked earlier on this page lists the criteria.