Resources · Make integration

Workstack Make integrationAutomate Workstack with Make.

Can Make keep your Workstack projects, tasks and meetings in sync with the rest of your tools? The Workstack Make integration gives you 7 triggers, 21 actions and 4 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Workstack integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Workstack Make integration do for you?

The Workstack Make integration links your Workstack account to Make, a no-code tool where you chain apps into a scenario, the automation you build step by step. Each step is a module: a trigger that watches Workstack, an action that changes something in it, or a search that pulls a list out of it.

A ready-made checklist on every new project. Watch Created Projects spots the project, then Create a Todo List and Create a Todo lay out the first steps, so nobody starts from a blank page.

A personal task digest. List Tasks for a User returns everything assigned to one person, and the next module can send that list to a chat app or a spreadsheet for a team lead who does not live in Workstack.

Meetings that follow the calendar. When a meeting is booked in another tool, Create a Meeting records it in Workstack, and Update a Meeting keeps it aligned when the source changes.

What the integration does not do: all 7 triggers are scheduled, so Make checks Workstack at intervals instead of hearing about changes instantly. The official documentation also carries a notice saying it was AI-generated from the vendor docs, so test each module with a real record before trusting it. Before you commit, the Make pricing page explains what a plan includes, and n8n vs Make helps if you are still choosing a tool. When something breaks, start with Make troubleshooting.

Connect

How do you connect Workstack to Make?

  1. 01

    Copy your API token from Workstack

    In Workstack, open your Personal Settings page and find the section for API tokens. Click Generate or Reveal if the token is hidden, then copy the value shown on screen. You need an active Workstack account for this.

  2. 02

    Add a Workstack module and open the connection

    In your Make scenario, add any Workstack module and click Create a connection. The connection is your Workstack account linked to Make once; every Workstack module in your scenarios reuses it afterwards.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name like the workspace owner helps when you manage several accounts. Paste the token you copied, confirm, and Make can now read your Workstack data.

First scenario

Your first scenario: a starter task on every new Workstack project

GoalWhen a project is created in Workstack, Make adds a first task to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick the trigger

    Search for Workstack, choose Watch Created Projects and select your connection, or click Create a connection if this is your first Workstack module.

  3. 03

    Add the task

    Click the + on the right of the trigger, pick Create a Task, then map the project coming from the trigger so the task lands in the right place.

  4. 04

    Test with Run once

    Create a test project in Workstack, then click Run once. Open the bubbles above each module to read the bundles, the items each module received and passed on.

  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. Each module run on one bundle counts as one operation on your plan.

Triggers

Workstack triggers: what starts your scenario

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

Workstack1Watch Created Meetings

Watch Created Meetings

triggerIn the docs only

Hands your scenario each meeting that was newly added in Workstack, one bundle per meeting, so you can react to a booking without checking the app yourself.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a meeting shows up at the next check rather than the second it is created.
When to use it
you want a note posted in a team channel or a row added to a sheet whenever someone books a meeting.
Watch out
the name points at creations; if you also care about edits, look at Watch Meetings and test both.
Workstack2Watch Created Projects

Watch Created Projects

triggerIn the docs only

Gives you a fresh bundle for every project that appears in Workstack, which makes it the natural starting point for any setup work a new project needs.

How it fires
scheduled. Make polls Workstack on the scenario's schedule, and on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
a new client project should always get the same starter tasks, a todo list or a line in your reporting tool.
Watch out
projects created before you switch the scenario on are not the point of this module; run a test with a brand new project.
Workstack3Watch Created Tasks

Watch Created Tasks

triggerIn the docs only

Passes each newly created task to the rest of your scenario, so work logged in Workstack can reach people and tools that never open it.

How it fires
scheduled. Make asks Workstack for new tasks at each run of the schedule you set on this first module.
When to use it
a support lead wants every new task copied to a shared tracker, or a message sent to whoever handles intake.
Watch out
a busy team can produce many tasks between two checks; each one is a bundle, and every module after the trigger spends one operation per bundle.
Workstack4Watch Created Todo Lists

Watch Created Todo Lists

triggerIn the docs only

Catches every todo list added in Workstack and sends it on as a bundle, useful when a list marks the start of a phase or a checklist someone must follow.

How it fires
scheduled. Make checks Workstack on the scenario's schedule rather than being alerted by the app.
When to use it
a project manager wants a heads-up in chat each time a new checklist appears, or wants to fill that list automatically with Create a Todo.
Watch out
if the same scenario also creates todo lists, you can end up triggering yourself; keep creation and watching in separate scenarios.
Workstack5Watch Created Todos

Watch Created Todos

triggerIn the docs only

Delivers each new todo, the small checklist item in Workstack, as its own bundle, so even minor action items can travel to another app.

How it fires
scheduled. Make polls the app at the interval of the scenario, 15 minutes unless you change it.
When to use it
an assistant wants personal todos mirrored into a notes app, or an ops lead wants a log of every item added during a launch.
Watch out
todos are often numerous; add a filter after the trigger when only some of them matter, so the following modules do not spend operations on the rest.
Workstack6Watch Meetings

Watch Meetings

triggerIn the docs only

Follows the meetings in your Workstack account and feeds them to the scenario, which is the broader sibling of Watch Created Meetings.

How it fires
scheduled. Make checks Workstack on the scenario's schedule and returns what it finds as bundles.
When to use it
you keep an external calendar or a reporting sheet that should reflect your Workstack meetings.
Watch out
the documentation does not spell out how this module differs from Watch Created Meetings; click Run once after both creating and editing a meeting and read the bundles before you rely on it.
Workstack7Watch Projects

Watch Projects

triggerIn the docs only

Keeps an eye on the projects in Workstack and sends them into your scenario, the wider counterpart of Watch Created Projects.

How it fires
scheduled. Make queries Workstack at every run of the schedule on this module instead of waiting for a signal.
When to use it
a portfolio sheet or a dashboard should stay close to what is happening in your Workstack projects.
Watch out
the doc gives no detail on which project changes this trigger picks up, so test it with a new project and with an edited one before you build on it.
Modules

Workstack modules: actions and searches

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

Workstack1

Create a Meeting

ActionIn the docs only

Adds a meeting to Workstack from data your scenario already has, so a booking made elsewhere shows up where the project team works.

When to use it
a form or a scheduling tool confirms a client call and you want it logged next to the related project.
Watch out
run the scenario once with a test booking, since duplicates appear fast when the source sends the same event twice.
Workstack2

Create a Project

ActionIn the docs only

Opens a new project in Workstack without anyone typing it in, which turns a signed deal or an accepted brief into a workspace right away.

When to use it
a CRM or form marks a client as won and delivery should start in Workstack.
Watch out
map a clear project name from the source app, because every later task and todo will hang off this project.
Workstack3

Create a Task

ActionIn the docs only

Turns an event from another tool into a Workstack task, so a request never stays stuck in an inbox or a form reply.

When to use it
a support ticket, a form entry or a message tagged as work should become something a teammate owns.
Watch out
place it after the module that finds or creates the project, so you can map the right project instead of guessing.
Workstack4

Create a Todo

ActionIn the docs only

Drops a single todo, a small checklist item, into Workstack. It is the lightest way to record a next step coming from another app.

When to use it
a meeting note, an email or a chat message contains one follow-up that someone should tick off.
Watch out
if a search before it returns several bundles, this module runs once per bundle and creates one todo each time.
Workstack5

Create a Todo List

ActionIn the docs only

Creates a todo list in Workstack, ready to receive your steps. Pair it with Create a Todo to build a full checklist in one run.

When to use it
every new project or phase needs the same onboarding checklist, and you are tired of building it by hand.
Watch out
create the list first, then map its output into each Create a Todo module that follows.
Workstack6

Delete a Meeting

ActionIn the docs only

Removes one meeting from Workstack, which keeps the schedule clean when the event is cancelled in the tool where it was first booked.

When to use it
your booking tool reports a cancellation and the Workstack copy should disappear too.
Watch out
a delete cannot be undone from Make; add a filter before it so only the meeting you really mean is sent.
Workstack7

Delete a Project

ActionIn the docs only

Deletes a whole project in Workstack. It is the most drastic module of the set and belongs at the end of a well-filtered cleanup flow.

When to use it
test projects created while you built the scenario need to go, or a deal was cancelled before any work began.
Watch out
nothing brings the project back from Make, and its tasks may go with it; test on a dummy project first.
Workstack8

Delete a Task

ActionIn the docs only

Removes one task from Workstack when the request behind it no longer exists, so your team does not chase work that was withdrawn.

When to use it
a ticket is closed as a duplicate in your help desk and the matching task should go.
Watch out
deletion is final; keep a Get a Task in front of it while testing to check which task you are about to remove.
Workstack9

Delete a Todo

ActionIn the docs only

Takes a single todo out of Workstack. Handy when a checklist item created automatically turns out to be irrelevant for this case.

When to use it
a condition in your scenario shows that a standard step does not apply, for example an internal project with no client review.
Watch out
once gone, the todo cannot be recovered from Make, so filter carefully on the bundle you pass in.
Workstack10

Delete a Todo List

ActionIn the docs only

Deletes a todo list from Workstack, which is how you clear a checklist that an automated setup created by mistake.

When to use it
your onboarding scenario ran twice on the same project and left a duplicate list behind.
Watch out
the todos inside the list are likely affected too, and Make cannot restore them; run it on a test list before going live.
Workstack11

Get a Meeting

ActionIn the docs only

Fetches one meeting from Workstack so later modules can use its details, instead of relying on the partial data a trigger or another app handed over.

When to use it
you know which meeting you need, for example from an earlier bundle, and want its full record before sending a reminder.
Watch out
it reads a single meeting; to go through many, start with List Meetings.
Workstack12

Get a Project

ActionIn the docs only

Reads one project from Workstack and passes its data on, so a message or a report can quote the project instead of a bare reference.

When to use it
a task arrives from a trigger and you want the name of its project in the notification you send.
Watch out
this module needs to know which project to read; map it from a previous bundle rather than typing it by hand.
Workstack13

Get a Task

ActionIn the docs only

Pulls the current state of one task from Workstack, which is useful right before you decide whether to update, notify or delete.

When to use it
a scenario must check a task again after another tool changed something related to it.
Watch out
every Get costs one operation per bundle; only add it when the data you already have is not enough.
Workstack14

Get a Todo

ActionIn the docs only

Retrieves a single todo from Workstack with its details, so the next module works with fresh information instead of a stale copy.

When to use it
you mirror todos into another app and want to confirm one before updating its copy there.
Watch out
it returns one item only; for everything that sits outside a project, List All Todos Without a Project is the better start.
Workstack15

Get a Todo List

ActionIn the docs only

Reads one todo list from Workstack so you can reuse its information further down the scenario, for instance in a summary sent to a client.

When to use it
Watch Created Todos gives you an item and you also want details on the list it belongs to.
Watch out
map the list from a previous bundle; a hand-typed value breaks the day that list is replaced.
Workstack16

List All Todos Without a Project

SearchIn the docs only

Returns the todos that are not attached to any project, the loose items people jot down and forget. It is a search, so it can return zero, one or many bundles.

When to use it
you want a tidy-up scenario that sends these orphan items to their owners or files them into the right project.
Watch out
each returned todo is a bundle, and every following module spends one operation on it.
Workstack17

List Meetings

SearchIn the docs only

Brings back the meetings stored in Workstack as a series of bundles, which you can then filter, count or push to another tool.

When to use it
you build a meeting overview in a spreadsheet or feed a reporting tool with what is booked.
Watch out
an empty result stops the modules after it for that run; test once with at least one meeting in the account.
Workstack18

List Projects

SearchIn the docs only

Collects your Workstack projects and hands them over one bundle at a time, the base for any scenario that works across the whole portfolio.

When to use it
you want a status sheet with every project, or you need to loop over projects to create the same todo in each.
Watch out
the output grows with your account; add a filter early so later modules only handle the projects that matter.
Workstack19

List Tasks for a User

SearchIn the docs only

Gathers the tasks assigned to one person in Workstack, which is exactly what you need to build a personal digest or a workload view.

When to use it
a manager wants each teammate to receive their open tasks in chat or by email.
Watch out
it works for one user per run; to cover a team, feed it one bundle per person from a sheet or another search.
Workstack20

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Workstack API with the connection you already set up, for the jobs none of the listed modules cover.

When to use it
you need something the 32 ready-made modules do not offer and the Workstack API documentation describes it.
Watch out
you write the request yourself, so check the vendor docs first; the Make documentation notes that its own content was AI-generated.
Workstack21

Update a Meeting

ActionIn the docs only

Changes an existing meeting in Workstack, so a moved call or a new agenda reaches your project space without retyping.

When to use it
the booking tool reports a rescheduled meeting and Workstack still shows the old one.
Watch out
map only the values that changed; filling every field from an incomplete source can erase details someone added by hand.
Workstack22

Update a Project

ActionIn the docs only

Edits a Workstack project from another tool, keeping names and details aligned when the source of truth lives elsewhere, such as a CRM.

When to use it
a deal is renamed or its scope changes and the project should follow.
Watch out
if a Watch Projects scenario also listens to the same projects, your update may wake it; keep an eye on loops between the two.
Workstack23

Update a Task

ActionIn the docs only

Modifies a task that already exists in Workstack. It is how a status change in a help desk or a form reply flows back to the person doing the work.

When to use it
a client answers a question and the related task should reflect the new information.
Watch out
find the task first with Get a Task or List Tasks for a User, then map it here.
Workstack24

Update a Todo

ActionIn the docs only

Edits one todo in Workstack, for example to adjust its wording or reflect progress recorded in another app.

When to use it
you keep a todo mirrored elsewhere and a change on that side should come back to Workstack.
Watch out
two scenarios syncing in both directions can bounce the same change back and forth; decide which side wins before you build.
Workstack25

Update a Todo List

ActionIn the docs only

Changes an existing todo list, useful when a checklist created by a template needs a project-specific touch after the fact.

When to use it
the project it belongs to was renamed and the list should carry the new label.
Watch out
this module targets the list. To change one todo, use Update a Todo; click Run once and check the result in Workstack.
Need help

Need help automating Workstack with Make?

A person reads every message.

FAQ

Workstack and Make: common questions

01Is the Workstack Make integration free?
Yes, on the Make side. Workstack is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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 operations, one per module per bundle. You also need your own active Workstack account, which follows Workstack's own pricing.
02What do you need to connect Workstack to Make?
An active Workstack account and its API token. In Workstack, go to Personal Settings, find the API token section, click Generate or Reveal if needed and copy the token. In Make, add a Workstack module, click Create a connection, optionally give it a name, and paste the token. That single connection is then reused by every Workstack module in your scenarios, so you do this once per account rather than once per module.
03Does the Workstack trigger in Make fire in real time?
No. All 7 Workstack triggers are scheduled: Make checks Workstack on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans go down to 1 minute. So a new project or task reaches your scenario at the next check, not the moment it is created. If you need a faster reaction, shorten the schedule on a paid plan.
04What if a Workstack module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Workstack API with the connection you already have, so you can cover what the 21 actions and 4 searches do not. Read the Workstack API documentation before you write the request. Keep in mind that the Make documentation for Workstack carries a notice that it was AI-generated from vendor docs and may contain mistakes, so check anything important with Workstack directly.
05Should you pick Make or n8n for Workstack?
It depends on the tool your team already uses. On Make, Workstack comes with 32 ready-made modules, a visual editor and a connection built once and reused everywhere. Apps like Workstack often have an n8n node too, so check whether one exists before deciding. Base the choice on the modules you actually need, the way each tool counts usage and who will maintain the scenarios. The n8n vs Make comparison on this site walks through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations