Resources · Make integration

Paymo Make integrationAutomate Paymo with Make.

What if new Paymo clients, tasks and invoices moved on their own? The Paymo Make integration gives you 37 modules, including 6 instant triggers, to link Paymo with the rest of your stack. This page shows you how to connect it and build a first working scenario.

Try the Paymo integration on MakeSee the 37 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Paymo Make integration do for you?

The Paymo Make integration links your Paymo account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Paymo reports new clients, projects, tasks and time entries, and Make carries them into your other apps.

Every new client gets a project from day one. Watch New Clients fires as soon as a client appears in Paymo, and Create a Project opens a matching project, so nobody has to remember that step after a deal closes.

Invoices reach accounting without copy and paste. Watch New Invoices hands each new invoice to Make, where you can send its details to a spreadsheet, a chat channel or your bookkeeping app. Update an Invoice then lets you write changes back into Paymo.

Time logged in one place shows up everywhere. With Watch New Time Entries, a freelancer or a studio can push every new entry into a reporting sheet, while Create a Time Entry does the reverse and logs hours coming from another tool.

Be aware that the Make documentation for Paymo is AI-generated from Paymo's own documentation, so check anything important with Paymo directly. For whatever the listed modules skip, Make an API Call reaches the rest of the Paymo API. Paymo may also have a node in n8n; the n8n vs Make comparison helps you choose, and the Make pricing guide explains what your plan counts.

Connect

How do you connect Paymo to Make?

  1. 01

    Copy your Paymo API key

    In Paymo, click your profile picture in the bottom left corner, open My Settings, then API Keys, and copy the key shown on screen. Make uses it to act on your account, so keep it private.

  2. 02

    Add a Paymo module and create the connection

    In your Make scenario, add any Paymo module and click Create a connection. A connection is your Paymo account linked to Make once, then reused by every Paymo module you add later. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the on-screen instructions, and confirm. You need an active Paymo account with valid credentials for this to work. Once saved, Make can list your Paymo clients, projects and tasks in the module fields.

First scenario

Build your first Paymo scenario in Make

GoalWhen a new client is added in Paymo, Make creates a project for that client in Paymo.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. This first module is the one that starts everything.

  2. 02

    Pick Watch New Clients

    Search for Paymo, choose Watch New Clients, click Create a webhook, then Create a connection and paste your API key. Paymo will now call Make each time a client is created.

  3. 03

    Add Create a Project

    Click the + on the right of the trigger, pick Paymo again and choose Create a Project. Map the client coming from the trigger into the project fields so the new project belongs to the right client.

  4. 04

    Test with Run once

    Click Run once, then add a test client in Paymo. Open the bubbles above each module to read the bundle it received: one bundle is one item, here one client, passed from a module to the next.

  5. 05

    Switch it on

    When the test project looks right, switch the scenario on. Because the trigger is instant, the scenario runs whenever Paymo reports a new client, and each module run counts as one operation on your Make plan.

Triggers

Paymo triggers in Make

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

Paymo1Watch New Clients

Watch New Clients

Instant trigger

In Make“Triggers when a new client has been created.”

This trigger starts your scenario the moment someone adds a client in Paymo, and hands Make that client as a bundle you can reuse in every later module.

How it fires
instant: Paymo calls Make through a webhook as soon as the client is created, so there is no schedule to set.
When to use it
pick it for onboarding flows, such as opening a project, adding the client to your CRM or posting a welcome note in your team chat.
Watch out
it reacts to new clients only, so edits made to an existing client will not start the scenario.
Paymo2Watch New Invoices

Watch New Invoices

Instant trigger

In Make“Triggers when a new invoice has been created.”

Each invoice created in Paymo lands in Make right away, ready to be copied into a spreadsheet, announced to finance or matched against your accounting tool.

How it fires
instant: Paymo notifies Make through a webhook as soon as the invoice exists.
When to use it
choose it when billing needs to leave Paymo, for example to keep a revenue sheet current or to alert whoever chases payments.
Watch out
the trigger sees creation, not later changes; if you need an invoice's latest state, add Get an Invoice after it.
Paymo3Watch New Projects

Watch New Projects

Instant trigger

In Make“Triggers when a new project has been created.”

Watch New Projects gives your scenario a starting signal whenever a project is opened in Paymo, along with the project details as one bundle.

How it fires
instant: a webhook from Paymo reaches Make as soon as the project is created.
When to use it
use it to set up everything a project needs outside Paymo, like a shared folder, a chat channel or a standard task list created with Create a Task List.
Watch out
if another scenario already creates projects from new clients, both flows may chain; check that this is what you want before switching them on.
Paymo4Watch New Task Lists

Watch New Task Lists

Instant trigger

In Make“Triggers when a new task list has been created.”

Here the scenario wakes up each time a task list is added to a Paymo project, which is handy when lists mark phases of your work.

How it fires
instant: Paymo pings Make through a webhook as soon as the list is created.
When to use it
reach for it when a new phase should trigger something elsewhere, such as notifying the people in charge or logging the phase in a tracking sheet.
Watch out
the bundle describes the list itself; to see the tasks inside, follow it with List Tasks.
Paymo5Watch New Tasks

Watch New Tasks

Instant trigger

In Make“Triggers when a new task has been created.”

With this trigger, every task created in Paymo reaches Make as a bundle, so the right person hears about it in the tool they actually read.

How it fires
instant: Paymo sends the task to Make through a webhook as soon as it is created.
When to use it
good for mirroring tasks into a chat message, a calendar or another team's board, without anyone retyping them.
Watch out
a busy workspace creates many tasks, and each run uses operations on your plan; add a filter after the trigger if only some tasks matter.
Paymo6Watch New Time Entries

Watch New Time Entries

Instant trigger

In Make“Triggers when a new time entry has been created.”

Hours logged in Paymo travel straight to Make, one bundle per entry, so your reporting or payroll sheet stays in step with the timer.

How it fires
instant: Paymo calls Make through a webhook as soon as a time entry is created.
When to use it
pick it when time data feeds something outside Paymo, like a client dashboard, a budget tracker or a warning when a project runs long.
Watch out
an entry corrected later does not fire again, so pair it with Get a Time Entry if you need the final figures.
Modules

Paymo modules in Make

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

Paymo1

Create a Client

Action

In Make“Creates a new client.”

Adds a new client to Paymo from data arriving in the scenario, so a signed deal or a form reply becomes a client record without manual entry.

When to use it
place it after your CRM or quote tool marks a deal as won.
Watch out
to avoid a second record for the same company, run List Clients first and only create the client when nothing matches.
Paymo2

Create an Invoice

Action

In Make“Creates a new invoice.”

Drafts an invoice in Paymo from the scenario, which saves you rebuilding the same billing details each time a job is done.

When to use it
use it when a milestone closes in another tool, or when an approved quote should turn straight into an invoice.
Watch out
test it with Run once on a sample client, since a wrong mapping produces a real invoice in your account.
Paymo3

Create a Project

Action

In Make“Creates a new project.”

Opens a fresh project in Paymo, ready for tasks and time tracking, based on what earlier modules passed along.

When to use it
it fits right after Watch New Clients, or after a signed contract in your e-signature app, so work can start the same day.
Watch out
map the client carefully, otherwise the project ends up unattached and harder to bill.
Paymo4

Create a Task

Action

In Make“Creates a new task.”

Turns a request from elsewhere into a Paymo task, so emails, form entries or support tickets end up where your team plans its work.

When to use it
connect it behind a help desk or a form app whenever a new request needs someone to act on it.
Watch out
the task needs a home; pick or map the right project and task list, or it may land in the wrong place.
Paymo5

Create a Task List

Action

In Make“Creates a new task list.”

Sets up a task list inside a Paymo project, which is how you give every new project the same phases without clicking them in by hand.

When to use it
chain it after Create a Project or Watch New Projects to lay down a standard structure such as design, build and review.
Watch out
adding several lists means one module per list, and each one counts as an operation.
Paymo6

Create a Time Entry

Action

In Make“Creates a new time entry.”

Logs hours in Paymo from another source, which keeps your timesheets whole when some of the time is tracked outside Paymo.

When to use it
handy when a calendar event, a call tool or a separate timer holds the real duration and you want it billed in Paymo.
Watch out
the entry must point to the right task; a quick Get a Task beforehand helps you confirm it.
Paymo7

Delete a Client

Action

In Make“Deletes a specified client.”

Removes a client from Paymo when the scenario tells it to, which keeps your client list clean once a record is truly obsolete.

When to use it
only for clear cleanup cases, such as a test client or a duplicate you have already confirmed with List Clients.
Watch out
a deletion cannot be undone from Make, so add a filter that checks exactly which client you are about to remove.
Paymo8

Delete an Invoice

Action

In Make“Deletes a specified invoice.”

Erases a specific invoice in Paymo, useful when a draft was created by mistake or a duplicate slipped through an earlier automation.

When to use it
keep it for correction flows that you trigger on purpose, never as part of routine billing.
Watch out
invoices matter to your accounting, and Make gives you no way to restore one after this module runs.
Paymo9

Delete a Project

Action

In Make“Deletes a specified project.”

Takes a project out of Paymo entirely, which tidies up the workspace when a project was opened by error or never went ahead.

When to use it
fits cancellation flows, for instance when a deal is marked lost in your CRM after the project was already set up.
Watch out
think about the tasks and time attached to that project before deleting it, because there is no undo from the scenario.
Paymo10

Delete a Task

Action

In Make“Deletes a specified task.”

Removes one task from Paymo, so a request withdrawn elsewhere stops cluttering your team's plan.

When to use it
connect it to a cancellation signal, like a ticket closed as invalid in your help desk, to keep both tools aligned.
Watch out
make sure the scenario targets the right task, ideally by mapping it from an earlier module, since the deletion is final.
Paymo11

Delete a Task List

Action

In Make“Deletes a specified task list.”

Drops a whole task list from a Paymo project, which is how you undo a template phase that does not apply to a given job.

When to use it
after Create a Task List has laid out a standard structure, remove the phases a smaller project does not need.
Watch out
a list can hold tasks, so check its content with List Tasks before letting the scenario delete it.
Paymo12

Delete a Time Entry

Action

In Make“Deletes a specified time entry.”

Removes a time entry from Paymo, handy when hours were logged twice or synced from the wrong source.

When to use it
use it inside a correction flow, for example when a duplicate entry is spotted after comparing List Time Entries with another timer.
Watch out
once deleted, those hours are gone from billing and reports, so filter tightly before this step.
Paymo13

Get a Client

Action

In Make“Returns information about a specified client.”

Fetches the full details of one Paymo client, which lets later modules use information the trigger did not carry.

When to use it
place it after a task, project or invoice event when you need the client's details to write an email or fill a document.
Watch out
it returns a single client you point to; to look through many, use List Clients instead.
Paymo14

Get an Invoice

Action

In Make“Returns information about a specified invoice.”

Reads one invoice from Paymo as it stands now, so your scenario works with current figures rather than the snapshot taken at creation.

When to use it
add it before sending invoice data to accounting, or before a reminder, to be sure you share the latest version.
Watch out
you need to know which invoice to read, usually mapped from a trigger or from List Invoices.
Paymo15

Get a Project

Action

In Make“Returns information about a specified project.”

Pulls the details of a single Paymo project into the scenario, giving you its name and settings to reuse in the next modules.

When to use it
useful when a time entry or task arrives and you want to show which project it belongs to in a report or a message.
Watch out
it reads one project only; for a set of projects, List Projects is the right module.
Paymo16

Get a Task

Action

In Make“Returns information about a specified task.”

Retrieves one task from Paymo with its current details, a quick way to check a task before acting on it elsewhere.

When to use it
run it before Update a Task or before posting a status message, so you work from what the task says today.
Watch out
map the task from an earlier module; guessing which task to read leads to wrong data further down.
Paymo17

Get a Task List

Action

In Make“Returns information about a specified task list.”

Loads the details of one task list, so the scenario knows which phase of a project it is dealing with.

When to use it
handy after Watch New Tasks when your message or report should name the list, and so the phase, the task sits in.
Watch out
the module describes the list, not its tasks; List Tasks is what brings those in.
Paymo18

Get a Time Entry

Action

In Make“Returns information about a specified time entry.”

Reads a single time entry from Paymo, including any correction made since it was logged, which keeps your reports honest.

When to use it
place it before exporting hours to payroll or a client report, when the figure must be the final one.
Watch out
it works on one entry; to gather hours for a period or a project, use List Time Entries.
Paymo19

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Calls any endpoint of the Paymo API from your scenario with the same connection, which covers everything the ready-made modules leave out.

When to use it
reach for it when you need a Paymo object or action that has no module in this list.
Watch out
you write the request yourself, so keep Paymo's API documentation open and test with Run once before switching the scenario on.
Paymo20

Update a Client

Action

In Make“Updates the information of a specified client.”

Changes the information of an existing Paymo client, so a new address or contact entered in your CRM is reflected where you bill.

When to use it
connect it to a contact update in your CRM to keep both tools telling the same story.
Watch out
fill only the fields you want to change and check the result with Run once, so no correct value gets overwritten.
Paymo21

Update an Invoice

Action

In Make“Updates the information of a specified invoice.”

Edits an invoice already in Paymo, which lets the scenario reflect a payment, a new reference or a correction coming from another tool.

When to use it
place it after your payment or accounting app reports a change that Paymo should know about.
Watch out
target the invoice precisely, typically mapped from Get an Invoice or List Invoices, so you edit the right one.
Paymo22

Update a Project

Action

In Make“Updates the information of a specified project.”

Modifies a Paymo project from the scenario, keeping its details in line with decisions taken in other tools.

When to use it
good when a deal changes in your CRM, or when a status in another board should be mirrored in Paymo.
Watch out
fill only the details you mean to change, and test on a sample project with Run once before going live.
Paymo23

Update a Task

Action

In Make“Updates the information of a specified task.”

Changes an existing Paymo task, so progress recorded elsewhere, like a closed ticket, shows up on the task your team follows.

When to use it
use it when a help desk, a code tool or a form reports that something moved forward.
Watch out
map the task from Get a Task or List Tasks; a hard-coded task will be the only one ever updated.
Paymo24

Update a Task List

Action

In Make“Updates the information of a specified task list.”

Edits a task list in Paymo, for instance to rename a phase once the project scope changes.

When to use it
chain it after an event in another tool that redefines the phases of a project, so Paymo keeps the same wording.
Watch out
the module changes the list only; the tasks inside stay as they are unless you update them separately.
Paymo25

Update a Time Entry

Action

In Make“Updates the information of a specified time entry.”

Corrects a time entry already logged in Paymo, so hours adjusted in another tool are not billed twice or left wrong.

When to use it
reach for it when a timer or calendar fixes a duration after the fact and Paymo must follow.
Watch out
map the entry from Get a Time Entry or List Time Entries, so the scenario corrects the right hours and not the latest ones.
Paymo26

List Clients

Search

In Make“Returns a list of clients.”

Returns your Paymo clients as separate bundles, zero, one or many, so the next modules can handle each client in turn.

When to use it
use it for a full export to a sheet, or to check whether a client already exists before Create a Client.
Watch out
every returned client passes through the following modules and uses operations, so filter early.
Paymo27

List Invoices

Search

In Make“Returns a list of invoices.”

Brings back the invoices stored in Paymo, each as its own bundle, which is the starting point for any billing overview built outside Paymo.

When to use it
pick it for an export to your finance sheet or to hand a reminder flow the invoices it should look at.
Watch out
a long invoice history means many bundles; keep only the ones you need with a filter.
Paymo28

List Projects

Search

In Make“Returns a list of projects.”

Gathers the projects in your Paymo account and passes them on one by one, ready to be copied, compared or reported on.

When to use it
good for building a portfolio view in a spreadsheet, or for finding a project by name before updating it.
Watch out
the result can be empty; add a filter so the next modules only run on the projects you actually want.
Paymo29

List Task Lists

Search

In Make“Returns a list of task lists.”

Returns the task lists found in Paymo, which tells the scenario which phases already exist before it adds or changes anything.

When to use it
run it before Create a Task List to avoid creating a phase twice in the same project.
Watch out
each list becomes a bundle and every following module runs once per list, which adds operations.
Paymo30

List Tasks

Search

In Make“Returns a list of tasks.”

Fetches Paymo tasks as separate bundles, so you can report on open work or act on a whole batch of tasks at once.

When to use it
use it to send a digest of open tasks to a chat channel or to spot the tasks that still need an owner.
Watch out
without a filter, a big workspace can return many tasks, each costing operations in later modules.
Paymo31

List Time Entries

Search

In Make“Returns a list of time entries.”

Collects the time entries logged in Paymo, one bundle per entry, which is the raw material for timesheets and profitability reports.

When to use it
pick it when you want to total hours per project in a sheet, or compare Paymo with another timer.
Watch out
to add the entries up, place an aggregator after this module, since each entry arrives on its own.
Need help

Need help automating Paymo with Make?

A person reads every message.

FAQ

Paymo and Make: frequent questions

01Is the Paymo Make integration free?
Yes, Paymo is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario limit, bring the interval down to 1 minute and allow 40 minutes per execution. Usage is counted in operations, one per module run on one bundle. You still need your own Paymo subscription.
02What do you need to connect Paymo to Make?
You need an active Paymo account with valid credentials and a Paymo API key. To find the key, click your profile picture in the bottom left corner of Paymo, open your account settings, then API Keys, and copy it. In Make, add a Paymo module, click Create a connection, give it a name if you like, and paste the key. For the instant triggers, click Create a webhook first, then Create a connection.
03Do Paymo triggers in Make react in real time?
Yes. All 6 Paymo triggers in Make are instant: Paymo calls Make through a webhook as soon as a client, invoice, project, task list, task or time entry is created. There is no polling schedule to set on these triggers. They only react to new items, though, so changes to existing records do not start a scenario. To pick those up, run a scenario with a List or Get module on a schedule, every 15 minutes by default.
04What if the Paymo module you need is missing in Make?
Use Make an API Call. It sends any request to the Paymo API with the connection you already set up, so objects or actions without a dedicated module stay within reach. Keep Paymo's API documentation at hand to write the request. Also note that the Make documentation for Paymo is AI-generated from Paymo's own documentation, so confirm anything critical with Paymo before relying on it in production. If you are unsure how to phrase a request, test it once with Run once and read the response bundle.
05Should you use Make or n8n for Paymo?
It depends on the tool you already use and on what you need to cover. Make offers 37 Paymo modules, including 6 instant triggers, plus Make an API Call for the rest of the API. Paymo may also be available as an n8n node; compare the modules each tool offers for your actual flows, such as client onboarding or time reporting, and pick the one your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations