Resources · Make integration

Checkvist Make integrationAutomate Checkvist with Make.

What if your Checkvist lists filled themselves? The Checkvist Make integration gives you 13 modules: 2 triggers, 9 actions and 2 searches. This guide shows you how to connect your account and build a first working scenario, step by step.

Try the Checkvist integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Checkvist Make integration do for you?

The Checkvist Make integration links your outliner to Make, a no code tool where you build scenarios: automations made of modules, each module being one brick such as a trigger, an action or a search. Make can spot new lists and items in Checkvist, then create, read, update, find or delete them for you.

Tasks that arrive on their own. A support request, a form answer or an order in another app becomes a line in a shared checklist with Create a List Item. Nobody retypes anything, and the list stays the single place where the team looks.

Projects that start with their checklist. When a deal closes in your CRM, Search Checklists checks whether a list already exists for that client, and Create a Checklist opens one if it does not. Update a Checklist then keeps it aligned when the project changes.

Checkvist that talks to the rest of your stack. Watch List Items sends each new item of a chosen list to another tool, so a message, a ticket or a spreadsheet row appears without a copy and paste.

Know the limits before you start. Both triggers are scheduled, so Make checks Checkvist on the scenario's schedule rather than instantly. The Make documentation for this app is also marked as limited, because little public information about Checkvist exists; expect to test each module with Run once. If a step breaks, the Make troubleshooting guide helps, and Make pricing explains how operations are counted. Still weighing tools? Read n8n vs Make.

Connect

How do you connect Checkvist to Make?

  1. 01

    Add a Checkvist module

    In your scenario, click the + and search for Checkvist, then pick any module. Make asks for a connection, meaning your Checkvist account linked to Make once and reused by every Checkvist module. Click Create a connection.

  2. 02

    Name it and give access

    Give the connection a name if you like, for example the account it belongs to. Then follow what Make shows: either approve access on the Checkvist page that opens, or paste the key Checkvist gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, the fields can now read your account, so Make can offer your checklists instead of making you type references by hand. If nothing appears, the connection did not go through.

First scenario

Your first scenario with Checkvist

GoalWhen a new checklist appears in Checkvist, Make adds a starter item to it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Add Watch Checklists

    Search for Checkvist, pick Watch Checklists and create or select your connection. This scheduled trigger will pick up each checklist created in your account.

  3. 03

    Add Create a List Item

    Click the + on the right of the trigger and pick Create a List Item. For the target list, map the checklist delivered by Watch Checklists, then write the text of your starter item.

  4. 04

    Test with Run once

    Create a test checklist in Checkvist, then click Run once. Open the bubbles above each module to read the bundles, the items each module received, and check the new line in Checkvist.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on each new checklist gets its starter item.

Triggers

Which Checkvist triggers start a scenario?

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

Checkvist1Watch Checklists

Watch Checklists

Scheduled trigger

In Make“Triggers when a new list is created.”

Watch Checklists starts your scenario whenever someone creates a new checklist in Checkvist, so a fresh list can kick off the rest of your process without anyone copying it by hand.

How it fires
it is a scheduled trigger: Make checks Checkvist on the scenario's schedule, every 15 minutes by default, and picks up the lists created since the previous check.
When to use it
a new checklist marks the start of a project, and a matching record, message or first set of items should follow.
Watch out
nothing happens between two checks, so a list created just after a run waits for the next one.
Checkvist2Watch List Items

Watch List Items

Scheduled trigger

In Make“Triggers when a new list item is created in a chosen list.”

Watch List Items keeps an eye on one checklist you pick and sends each new item into your scenario as a bundle, the single piece of data Make passes from one module to the next.

How it fires
scheduled: Make checks Checkvist on the scenario's schedule, never the moment an item is typed, and collects what was added since its last visit.
When to use it
your team captures requests or bugs in a shared list, and each new line should reach another tool without a copy and paste.
Watch out
the trigger follows only the list chosen in its settings; items added to other checklists stay invisible to it.
Modules

What can the Checkvist modules do?

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

Checkvist1

Create a Checklist

Action

In Make“Creates a new checklist.”

Create a Checklist gives you a brand new list in Checkvist, ready to be filled by the modules that follow it in the same scenario.

When to use it
a deal is signed or a form is submitted in another app, and the project deserves its own checklist.
Watch out
if the scenario runs twice on the same event, you get two lists; put Search Checklists in front to check that the list does not exist yet.
Checkvist2

Create a List Item

Action

In Make“Creates a new list item.”

Create a List Item adds one line to a checklist you choose, so tasks coming from emails, forms or tickets land where your team already works.

When to use it
each new support request or order should become a to-do in a shared Checkvist list.
Watch out
the module writes one item per bundle; if an earlier module returns ten rows, Make creates ten items and counts ten operations, an operation being one run of one module.
Checkvist3

Delete a Checklist

Action

In Make“Deletes a checklist.”

Delete a Checklist removes an entire list from your Checkvist account, which keeps closed or duplicated projects from piling up.

When to use it
a project is cancelled in your CRM and its checklist has no reason to stay around.
Watch out
the whole list goes at once, so try it with Run once on a throwaway list before you switch the scenario on.
Checkvist4

Delete a List Item

Action

In Make“Deletes a list item.”

Delete a List Item takes a single line out of a checklist and leaves the rest of the list untouched.

When to use it
a task is cancelled at its source, for example an order refunded in your shop, and its line in Checkvist should go too.
Watch out
the module needs to know exactly which item to remove; find it first with Search List Items and look at the result, because a wrong match deletes the wrong task.
Checkvist5

Get a Checklist

Action

In Make“Gets checklist information.”

Get a Checklist reads the information of one list you can already point to, so later modules can reuse it without anyone opening Checkvist.

When to use it
your scenario starts from another app that stores a checklist reference, and you need the list information before writing a report or a message.
Watch out
it returns a single list; when you cannot identify the list yet, Search Checklists is the better pick.
Checkvist6

Get a List Item

Action

In Make“Gets list item information.”

Get a List Item fetches the current state of one specific item, which helps when the data you received earlier is incomplete or may have changed since.

When to use it
just before an update, to read the item exactly as it stands in Checkvist at that moment.
Watch out
it only works on an item you can already identify; with nothing more than a keyword, go through Search List Items instead.
Checkvist7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Checkvist API from your scenario, reusing the same connection as the other Checkvist modules.

When to use it
you need something that none of the other twelve modules covers.
Watch out
you build the request yourself, and the Make page for Checkvist is marked as limited documentation, so test every call with Run once and read the response before going further.
Checkvist8

Update a Checklist

Action

In Make“Updates a checklist.”

Update a Checklist changes an existing list in place, so it stays in step with what happens elsewhere without a second copy appearing.

When to use it
a project changes in your CRM and the matching checklist in Checkvist should follow the same change.
Watch out
you must point to the right list; pair it with Search Checklists when your scenario only knows the project, not the list itself.
Checkvist9

Update a List Item

Action

In Make“Updates a list item.”

Update a List Item edits a line that already exists in a checklist, which saves you from deleting and recreating tasks every time something moves.

When to use it
a ticket evolves in your helpdesk and its twin item in Checkvist has to reflect the new situation.
Watch out
the item has to be identified first, which is why Get a List Item or Search List Items usually sits right before this module.
Checkvist10

Search Checklists

Search

In Make“Searches lists by given criteria.”

Search Checklists looks through your Checkvist lists using the criteria you set and returns every match, one bundle per list.

When to use it
before creating a checklist, to see whether one already exists for this client, or to find the list an update should target.
Watch out
a search can return zero, one or several lists; decide what the next modules do when nothing comes back and when several do.
Checkvist11

Search List Items

Search

In Make“Search list items by given criteria.”

Search List Items finds the items matching your criteria, the simplest way to locate a task when you only know part of it.

When to use it
an email mentions a task and your scenario must find the matching line in Checkvist before updating it.
Watch out
every item found becomes its own bundle, so the modules after it run once per result and each run costs one operation.
Need help

Need help automating Checkvist with Make?

A person reads every message.

FAQ

Checkvist Make integration: common questions

01Is the Checkvist Make integration free?
Yes. Checkvist is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute and allow unlimited active scenarios. Usage is counted in operations, one execution of one module on one bundle.
02What do you need to connect Checkvist to Make?
A Checkvist account and a Make account. The Make documentation lists no special prerequisite for Checkvist and gives no dedicated connection steps, so the usual path applies: add a Checkvist module, click Create a connection, optionally name it, then either approve access on the Checkvist page or paste the key Checkvist provides, and click Save. The connection is then shared by every Checkvist module in your scenarios, so you only set it up once.
03Do the Checkvist triggers in Make react in real time?
No. Both Checkvist triggers, Watch Checklists and Watch List Items, are scheduled. Make checks Checkvist on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the shortest interval is 15 minutes; paid plans go down to one minute. Checkvist has no instant trigger in Make, so a new list or item is picked up at the next check, not the second it is created.
04What if a Checkvist module is missing in Make?
Use Make an API Call. It calls any endpoint of the Checkvist API with the same connection as the other modules, so you are not limited to the 13 listed modules. Keep in mind that the Make documentation for Checkvist is marked as limited, since little public information about the app exists. Build the request carefully and test it with Run once, reading the response bundle before connecting the next modules.
05Should you use Make or n8n for Checkvist?
It depends on the tool your team already runs. On the Make side, Checkvist offers 13 ready modules, 2 scheduled triggers and Make an API Call for the rest, so a first scenario comes together from the visual editor without code. If your automations already live in n8n, check whether a Checkvist node exists there before moving anything. Neither choice is better by default; compare the modules you need and the way each tool counts usage.
Same platform

Other docs you might need on this stack.

Browse all integrations