Resources · Make integration

Projectworks Make integrationAutomate Projectworks with Make.

Tired of typing the same client and leave data into Projectworks by hand? The Projectworks Make integration gives you 21 modules: 16 actions and 5 searches. This guide is for ops leads who know Projectworks and are new to Make, and it walks you from connection to a live scenario.

Try the Projectworks integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Projectworks Make integration do for you?

The Projectworks Make integration links your Projectworks account to Make, a visual tool where you chain modules into a scenario (an automation that runs on its own). Each module is one brick: it creates, reads, updates or deletes a client, a user, a leave, a forecast or a timesheet, without a line of code.

Leave requests that record themselves. A request comes in from a form or a chat tool. Search Users finds the employee, then Create a Leave books the absence in Projectworks, so nobody retypes dates.

A client list that stays in sync. When a deal is won in your CRM, Create a Client opens the record in Projectworks. When the company details change on the CRM side, Update a Client carries the change over.

Timesheet data where your reports live. List Timesheets pulls entries out as bundles (one item per timesheet) that you can send to a spreadsheet or a dashboard app.

One limit to know up front: Projectworks has no trigger module in Make. Make cannot notice on its own that something changed inside Projectworks, so every scenario starts from another app or from a schedule. If you also look at n8n, the n8n vs Make comparison sets the two tools side by side, and the Make pricing page explains how operations are counted.

Connect

How do you connect Projectworks to Make?

  1. 01

    Add a Projectworks module

    Log in to Make, open your scenario and add any Projectworks module. In the module panel, click Create a connection. A connection is your Projectworks account linked to Make once, then reused by every Projectworks module.

  2. 02

    Name the connection

    The Connection name field is optional. Filling it still helps: a label such as the name of your workspace tells you which account a module uses when you open the scenario later.

  3. 03

    Paste your Projectworks credentials

    Enter the credentials you copied from Projectworks, or follow the instructions on screen. According to the Make doc, you find a Username and a Password in the settings or account section of Projectworks.

First scenario

Your first scenario: turn a leave request into a Projectworks leave

GoalWhen a leave request arrives from another app, Make finds the employee in Projectworks and creates the leave.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where leave requests land first, such as your form tool, since Projectworks has no trigger.

  2. 02

    Find the employee

    Click the + on the right of the first module, search for Projectworks and pick Search Users. Click Create a connection, then map what the request says about the person.

  3. 03

    Record the leave

    Add Create a Leave after the search. Map the user found in the previous step and the dates from the request. Make lists the Projectworks data it can read once the connection exists.

  4. 04

    Test with Run once

    Send one test request, then click Run once. Open each module and read the bundles it received: the search should return the right person, and the leave should appear in Projectworks.

  5. 05

    Schedule and switch on

    Set the clock on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Modules

What the 21 Projectworks modules do

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

Projectworks1

Create a Client

ActionIn the docs only

Opens a new client record in Projectworks from data that already exists elsewhere, so the account manager never types the company twice.

When to use it
right after a deal is marked as won in your CRM, to have the client ready before the first project starts.
Watch out
run List Clients first if the same company can come in twice, or you may end up with duplicates.
Projectworks2

Create a Forecast

ActionIn the docs only

Adds a forecast in Projectworks from another tool, which gives your planning view data without a manual entry for each new piece of work.

When to use it
when a signed quote or a planning sheet already holds what you expect to deliver and you want Projectworks to reflect it.
Watch out
the Make doc does not describe the forecast fields, so open the module and check what it asks for before mapping.
Projectworks3

Create a Leave

ActionIn the docs only

Books an absence in Projectworks for a given user, so holidays and time off show up where managers plan capacity.

When to use it
once a request has been approved in your HR tool, a form or a chat channel.
Watch out
the module needs to know which user takes the leave, so place Search Users or Get a User before it in most scenarios.
Projectworks4

Create a User

ActionIn the docs only

Adds a new person to Projectworks, which spares the office manager a manual account setup on every hire.

When to use it
when a new employee record appears in your HR system or onboarding sheet and that person will log time.
Watch out
search first with Search Users if the same hire can be sent twice, since a second run creates a second user.
Projectworks5

Delete a Client

ActionIn the docs only

Removes a client from Projectworks for good, which keeps the list short when an account closes on the CRM side.

When to use it
after a client record is flagged as closed or created by mistake in the source tool.
Watch out
a deletion done by a scenario cannot be undone from Make, so test with Run once on a dummy client before switching it on.
Projectworks6

Delete a Leave

ActionIn the docs only

Cancels an absence that no longer applies, so the capacity view in Projectworks stops showing someone as away.

When to use it
when an employee withdraws a request or a manager rejects it after it was already recorded.
Watch out
you need the exact leave to remove, so fetch it with List Leaves or Get a Leave first, and remember a deletion is final.
Projectworks7

Delete a Timesheet

ActionIn the docs only

Erases a timesheet from Projectworks, which helps clean up entries logged against the wrong work before invoicing.

When to use it
when an approval step elsewhere marks an entry as invalid and it should disappear from the numbers.
Watch out
hours deleted here are gone from reporting, so consider Update a Timesheet when the entry only needs a correction.
Projectworks8

Get a Client

ActionIn the docs only

Reads one client you already know, so the rest of the scenario can reuse its details without asking anyone.

When to use it
when an earlier module hands you the client's identifier and you need the full record, for example to fill an invoice draft in another app.
Watch out
it returns one client only; to browse several, choose List Clients instead.
Projectworks9

Get a Leave

ActionIn the docs only

Fetches a single leave with its details, so you can check it before acting on it or pass it on to a calendar or a message.

When to use it
when you hold the reference of one absence and want to confirm what Projectworks recorded.
Watch out
without that reference you will not get far, and List Leaves is the module that finds leaves you cannot yet identify.
Projectworks10

Get a Timesheet

ActionIn the docs only

Retrieves one timesheet entry, giving the scenario the hours and context it needs for a check or a notification.

When to use it
when another step already points to a specific entry, say a line a manager flagged in a review sheet.
Watch out
it reads a single entry; for a batch of entries to export or total, List Timesheets is the right module.
Projectworks11

Get a User

ActionIn the docs only

Loads the profile of one Projectworks user, which is handy when a later module needs more than a name.

When to use it
after a leave or a timesheet gives you a user reference and you want that person's details in a message or a report.
Watch out
without the user's Projectworks reference, Search Users is the module that finds the person first.
Projectworks12

List Clients

SearchIn the docs only

Returns your Projectworks clients as separate bundles, so each one can flow into the next module on its own.

When to use it
to copy the client list into a spreadsheet, or to check whether a company exists before Create a Client.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations on your plan.
Projectworks13

List Forecasts

SearchIn the docs only

Brings your Projectworks forecasts into the scenario, which lets you share the planned workload outside the tool.

When to use it
when a staffing meeting relies on a sheet or a dashboard and you want the forecast numbers there instead of copied by hand.
Watch out
each forecast becomes one bundle, so add an aggregator from Make if the next app expects a single table.
Projectworks14

List Leaves

SearchIn the docs only

Collects recorded absences from Projectworks, the starting point for any team calendar or availability summary built elsewhere.

When to use it
when a shared calendar or a chat channel should show who is away, fed from Projectworks rather than a separate list.
Watch out
the scenario reads leaves when it runs; since Projectworks has no trigger, a new absence appears only at the next scheduled run.
Projectworks15

List Timesheets

SearchIn the docs only

Pulls timesheet entries out of Projectworks as bundles, ready to land in a spreadsheet, a BI tool or an invoicing app.

When to use it
when finance closes a period and wants logged hours outside Projectworks without an export by hand.
Watch out
many entries mean many bundles and as many operations downstream, so filter what you keep before the next module.
Projectworks16

Make an API Call

ActionIn the docs only

Calls any endpoint of the Projectworks API with the connection you already set up, covering whatever the dedicated modules leave out.

When to use it
when you need a Projectworks object or action that none of the listed modules offers, such as data outside clients, users, leaves, forecasts and timesheets.
Watch out
you write the request yourself, so keep the Projectworks API documentation open while you set it up.
Projectworks17

Replace a Leave

ActionIn the docs only

Swaps an existing leave for a new version in Projectworks, which fits when an absence changes rather than disappears.

When to use it
an employee moves an approved holiday, and the source tool sends the corrected request.
Watch out
the Make doc does not say so, but the name suggests the whole leave gets overwritten. Map every value you want to keep, not only the one that changed.
Projectworks18

Search Users

SearchIn the docs only

Finds Projectworks users from what you know about them, turning what another app knows about someone into a real Projectworks person.

When to use it
ahead of Create a Leave or Update a User, when the incoming data does not carry a Projectworks identifier.
Watch out
a search may match nobody or several people, so add a filter after it before any action runs.
Projectworks19

Update a Client

ActionIn the docs only

Changes an existing client in Projectworks, so company details corrected in your CRM reach the project side too.

When to use it
when the sales team edits company details and delivery should not work from stale data.
Watch out
the module needs the right client, so pair it with List Clients or Get a Client when the source only holds a company name.
Projectworks20

Update a Timesheet

ActionIn the docs only

Corrects a timesheet entry already in Projectworks, which saves a round of emails when hours were logged slightly wrong.

When to use it
when a review in another tool approves a change to logged time and the entry should match.
Watch out
test the mapping with Run once on one entry first, since an update overwrites what the person typed.
Projectworks21

Update a User

ActionIn the docs only

Edits a Projectworks user profile, keeping it aligned with the system where HR maintains people data.

When to use it
after a role change or a team move is recorded in your HR tool, so Projectworks shows the same information.
Watch out
run Search Users or Get a User before it, because updating the wrong person is easy when two colleagues share a name.
Need help

Need help automating Projectworks with Make?

A person reads every message.

FAQ

Projectworks and Make: common questions

01Is the Projectworks Make integration free?
Yes, Projectworks is a standard app in Make, so its modules are available on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Every module that runs uses operations, which Make counts on your plan. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and allow a shorter interval. You still need your own Projectworks subscription.
02What do you need to connect Projectworks to Make?
You need an active Projectworks account and its API credentials. The Make doc lists an API key as a prerequisite and describes finding a username and a password in the settings or account section of Projectworks. In Make, add any Projectworks module, click Create a connection, give it a name if you like, then paste the credentials. The connection is created once and reused by all 21 Projectworks modules in your scenarios.
03Can the Projectworks Make integration react to changes in real time?
No, not from inside Projectworks. The app has no trigger module in Make, scheduled or instant, so Make is never told when something changes in Projectworks. You still have two ways to start a scenario. Put a trigger from another app first, such as a form or a CRM, and let the Projectworks modules act on what it sends. Or start with a list module like List Timesheets and let Make run the scenario on its schedule, every 15 minutes by default.
04What if a Projectworks module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Projectworks API with the connection you already created, so you can reach data the 21 listed modules do not cover. You write the request yourself, which means keeping the Projectworks API documentation at hand. Also note that the Make doc for Projectworks is marked as AI-generated from the vendor documentation and may contain mistakes, so check anything important directly with Projectworks.
05Should you use Make or n8n for Projectworks?
It depends on your criteria rather than on a winner. On Make, Projectworks comes with 21 modules, a visual editor and a Free plan to test a first scenario. Many apps also have an n8n node, so check whether one exists for Projectworks and what it covers before choosing. Compare the modules each tool offers for your use case, how each counts usage, and which editor your team is comfortable in. The comparison page on this site goes through those points.
Same platform

Other docs you might need on this stack.

Browse all integrations