Paymo

Paymo is project management, time tracking, resource scheduling and invoicing for small teams. Agents create projects and tasks, log time, schedule bookings, issue invoices and estimates, and start flows when Paymo records change.

1 trigger 167 actions Basic auth available

Paymo website Platform Documentation Capability data verified 2026-08-18

The billing period closes, or On Paymo Event reports a milestone reaching completion

List Time Entries pulls the period's logged hours, filtered by client and project

List Expenses narrowed to uninvoiced finds the costs that still need billing

Get Project confirms the work is billable and reads the rate the client agreed to

Create Invoice assembles the lines, naming the time entry and expense identifiers so Paymo marks them billed

Download Invoice renders the PDF and posts it to the account lead with the underlying breakdown

The account lead approves the invoice before it is sent, because Paymo will not un-bill the hours on its own

What This Integration Enables

Paymo's argument is that a small services team should not run a project tool, a timesheet, a resource planner and an invoicing system as four separate purchases. Time is logged against a task, the task belongs to a project, the project belongs to a client, and an invoice line can name the exact time entries it bills. That last link is the one that matters, because it is what makes the path from work to money a single traceable chain rather than a monthly reconstruction. FlowRunner agents work along that chain end to end: creating projects from templates, assigning people, starting and stopping timers, reserving capacity with resource bookings, and turning unbilled time and expenses into invoices and estimates with the PDFs rendered and ready.

Two properties of this API change how a flow should be written. Paymo publishes no paging on any route, so every list returns the whole collection and the answer is to filter rather than to paginate; each list operation here takes typed filter fields plus a free-form expression for anything the typed fields miss. And billing is one-directional by design: naming a time entry on an invoice line marks that time as billed, and getting it back means deleting the invoice. That asymmetry is exactly why the human-in-the-loop step on this connector sits at the money boundary rather than anywhere upstream of it.

Without FlowRunner

Billing assembled by hand each month Somebody exports the timesheet, cross-checks the expenses, and rebuilds the invoice from a spreadsheet

Uninvoiced work goes quiet Expenses logged mid-project are found at year end, long after the client would have accepted them

Recurring invoices are all or nothing Either a person raises every repeat invoice by hand, or the schedule sends them with nobody looking

With FlowRunner

Billing assembled from the source Time entries and expenses are read where they were logged and become invoice lines directly

Uninvoiced work surfaces on a schedule The uninvoiced filter runs every period, so nothing sits unbilled because nobody thought to look

Recurring invoices keep a reviewer The schedule drafts, the agent assembles, and a person approves before the client sees anything

Use Case Scenarios

A kickoff that provisions itself from the template

A deal closes in HubSpot. The agent calls Create Client with the fiscal information the invoice header will later need, adds the client contacts, and calls Create Project naming the client deliberately rather than letting Paymo file the work under an invented sample client. Apply Project Template copies the standard delivery structure in, adding to the project rather than replacing anything already there, and adding any assignees the template names who are not yet on the project. Create Task Assignment then returns the assignment identifiers that Create Booking needs to reserve each person's hours across the delivery window. The kickoff channel in Slack gets the project link and the booked capacity in one message.
Utilization the delivery lead can act on

Every Monday the agent calls Create Report as a temporary report, which returns the numbers without storing anything or cluttering the Paymo application. It reads billable against non-billable hours per person for the previous week, cross-references List Bookings to see what had been reserved, and flags the gaps in both directions: people booked past their capacity and people with capacity nobody reserved. The digest posts to the delivery lead, and Download Report attaches the workbook for anyone who wants the detail. Resourcing conversations start from the same numbers every week instead of from whoever spoke first.
Deadlines that raise their hand before they slip

The agent runs List Milestones filtered by due date with the completion flag off, which is Paymo's own way of asking for deadlines still at risk. For each one it reads the linked task lists and their tasks, checks how much of the budgeted time has been logged with Get Task Spent Time equivalents from List Time Entries, and posts a per-milestone summary naming the responsible user. Where a milestone is short on time and long on remaining tasks, the flow escalates to the project manager rather than quietly moving the date. Paymo's own reminder mechanism sends nothing when the reminder window is set to zero, so a flow that assumes a reminder went out is assuming too much.

Human-in-Loop Highlight

Create Invoice Recurring Profile carries a setting called Auto Send, and turning it on emails each new invoice to the client without anyone reviewing it first. That is the operation this page's gate is built around, because it is Paymo offering to remove the last person from the loop on a repeating money-moving action. FlowRunner's answer is to leave Auto Send off and put the agent in the space it vacated. The profile raises the draft on schedule. The agent then reads the invoice with its line detail included, pulls the underlying time entries and uninvoiced expenses that period actually produced, and compares the draft against them. If the numbers agree, it still stops: "Recurring invoice 2041 for Marchant Group, 14,200 GBP, raised from the monthly retainer profile. The period logged 96 billable hours against a 90 hour retainer, and two uninvoiced expenses totaling 340 GBP are not on it. Send as raised, add the expenses, or hold?" The account lead answers, and only then does the invoice go out. Naming a time entry on an invoice line marks that time billed, and Paymo un-bills it only by deleting the invoice, so this is the point in the chain where being right matters more than being quick.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

167 actions

Company

Get Company Reads the company profile with every account wide setting: default currency, invoice and estimate numbering, workday hours and the subscription limits. Check this first when writes start failing, because the current and maximum counts explain most refusals.
Update Company Updates the company profile and its settings. Only the fields supplied are changed, and read only counters such as the subscription limits are ignored if sent.

Users

Get Current User Reads the Paymo user the API key belongs to. Paymo scopes what a key can see to that person's own access rights, so this is how a flow discovers what it is actually able to reach.
List Users Lists the users in the company, optionally narrowed to active or retired accounts or to one account type.
Get User Reads one user together with the projects they are assigned to and the projects they manage.
Create User Invites a new user into the company. Only the email address is required, and leaving the password out creates the account for the person to complete themselves.
Update User Updates a user. Only what is supplied changes, except the assigned and managed project lists, which replace rather than add to what was there.
Set User Active Retires or reactivates a user. A retired user cannot sign in and stops counting toward the subscription limit, but their logged time is kept. The reversible alternative to Delete User.
Delete User Permanently deletes a user. Every time entry that person logged is deleted with them, which changes project totals and any report built from that time.

Clients and Contacts

List Clients Lists the clients in the account, optionally narrowed to active or archived ones.
Get Client Reads one client, including the fiscal information used in invoice headers and the logo image URLs.
Create Client Creates a client. The fiscal information field is what Paymo prints in the invoice header, so fill it in when this client will be invoiced.
Update Client Updates a client. Only the fields supplied are changed.
Set Client Active Archives or reactivates a client. Archiving hides the client without touching their projects, and is the reversible alternative to Delete Client.
Delete Client Permanently deletes a client along with their projects, task lists, tasks and all the time logged against them. Archive instead unless the whole history is genuinely meant to go.
List Client Contacts Lists the people recorded against clients, optionally narrowed to a single client.
Get Client Contact Reads one client contact, including whether they can sign in to the client portal.
Create Client Contact Adds a person to a client. Marking the contact as the main one makes them the default recipient for that client's correspondence.
Update Client Contact Updates a client contact. Only the fields supplied are changed.
Set Client Contact Portal Access Grants or withdraws a client contact's access to the Paymo client portal. Granting requires a password the person then uses to sign in; withdrawing needs none.
Delete Client Contact Deletes a client contact. The client itself and its projects are untouched.

Projects

List Projects Lists projects, optionally narrowed by client, status, active state, billability or the users assigned to or managing them.
Get Project Reads one project. The include parameter pulls the whole structure back in a single call, task lists with their tasks or tasks with their time entries.
Create Project Creates a project. Leaving the client out makes Paymo invent a sample client and file the project under it, so set one deliberately. Supplying a template copies its task lists and tasks in.
Update Project Updates a project. Only what is supplied changes, except the users and managers lists, which replace rather than add. Changing the workflow resets every task status in the project.
Set Project Active Archives or reactivates a project. Time cannot be logged against an archived project's tasks, which is what makes archiving the safe way to close work down.
Reorder Project Task Lists Sets the display order of a project's task lists.
Apply Project Template Copies the task lists and tasks from a template into an existing project. Nothing already there is replaced, the template's content is added alongside it, and assignees the template names are added to the project if missing.
Delete Project Permanently deletes a project along with its task lists, tasks, discussions, files and every time entry logged against it. Set Project Active is the alternative that keeps all of it.

Project Statuses

List Project Statuses Lists the project statuses defined for the company. A status carries an active flag that decides whether time can still be logged against the projects in it.
Get Project Status Reads one project status, optionally with every project currently in it.
Create Project Status Adds a project status. The active flag is what distinguishes work in progress from work that is closed to further time.
Update Project Status Updates a project status. The statuses Paymo ships with are read only and cannot be edited.
Delete Project Status Deletes a project status. The read only statuses Paymo ships with cannot be deleted.

Project Templates

List Project Templates Lists the project templates in the account, with the identifiers Create Project needs to copy one.
Get Project Template Reads one project template, and with its task lists and tasks included, its whole structure in a single call.
Create Project Template Creates a project template, either empty or as a copy of an existing project's structure. Files, discussions and comments are never part of a template.
Update Project Template Renames a project template. Projects already created from it are unaffected.
Delete Project Template Deletes a project template together with its task lists and tasks. Projects already created from it keep everything they were given.
Create Project Template Task List Adds a task list to a project template. Template tasks are added through this task list rather than to the template directly.
Update Project Template Task List Renames or repositions a task list inside a project template.
Delete Project Template Task List Deletes a task list from a project template together with every task in it.
Create Project Template Task Adds a task to a project template task list, optionally with its billing settings, budget hours and assigned users. Those settings copy into every project made from the template.
Update Project Template Task Updates a task inside a project template. Only what is supplied changes, except the users list, which replaces the previous assignment.
Delete Project Template Task Deletes a task from a project template.

Task Lists

List Task Lists Lists task lists, optionally narrowed to one project or to the ones linked with a milestone.
Get Task List Reads one task list, optionally with every task in it.
Create Task List Creates a task list in a project. Linking it to a milestone means every task in the list is expected to finish by that milestone's due date.
Update Task List Updates a task list. A task list cannot be moved between projects.
Reorder Tasks Sets the order of the tasks inside a task list. Order is a property of the list rather than of the project, and only the identifiers that moved need sending.
Delete Task List Permanently deletes a task list along with every task in it and every time entry logged against those tasks.

Tasks

List Tasks Lists tasks, optionally narrowed by project, task list, completion, assignee or workflow status. Unassigned Only finds the work nobody owns, which is the first thing a triage flow asks for.
Get Task Reads one task, optionally with its discussion, attachments, subtasks or logged time in the same call.
Create Task Creates a task in a task list or a project. Given a project with no task list, Paymo files it in a default list and creates that list if needed, so pass a task list when the destination matters.
Update Task Updates a task. Only what is supplied changes, except the users list, which replaces the previous assignment. Moving a task between lists in the same project is done here.
Set Task Complete Marks a task finished or reopens it. Paymo moves the workflow status too, so completing sets the status to complete and reopening discards whichever column the task was in.
Set Task Status Moves a task to a workflow status, which is what a board column represents. Use this rather than Set Task Complete when the task should move without being finished.
Set Task Priority Sets a task's priority. Paymo stores priority as one of four fixed values and refuses anything else rather than accepting it silently.
Delete Task Permanently deletes a task along with every time entry logged against it, which changes project totals and any report built from that time.

Subtasks

List Subtasks Lists subtasks, optionally narrowed to one task or project and to open or finished ones. Subtasks are Paymo's checklist and carry no time of their own.
Get Subtask Reads one subtask, including who finished it and when.
Create Subtask Adds a subtask to a task. A subtask carries a name and a finished flag, and no time can be logged against it.
Update Subtask Updates a subtask. Only the fields supplied are changed.
Set Subtask Complete Ticks a subtask off or reopens it. Paymo records who did it and when on the subtask itself.
Reorder Subtasks Sets the order of the subtasks inside a task. Only the identifiers that moved need sending.
Delete Subtask Deletes a subtask. The task it belonged to is untouched.

Task Assignments

List Task Assignments Lists the links between users and tasks. Paymo refuses this call without at least a user or a task, and assignments matter because a resource booking is made against one.
Get Task Assignment Reads one user to task assignment. Its identifier is what a resource booking is made against.
Create Task Assignment Assigns a user to a task and returns the assignment identifier that Create Booking needs. Setting the task's users list achieves the same assignment but does not hand back this identifier.
Update Task Assignment Repoints an existing assignment at a different user or task, keeping the bookings attached to it.
Delete Task Assignment Unassigns a user from a task by deleting the assignment.

Recurring Tasks

List Task Recurring Profiles Lists the rules that generate tasks on a schedule. Each records when it last ran and when it will next run, which is the quickest way to see whether a recurrence is still alive.
Get Task Recurring Profile Reads one task recurring profile, including how many tasks it has generated and when the next one is due.
Create Task Recurring Profile Creates a rule that generates a task on a schedule. Given an existing task to copy, Paymo takes every task field from that task and ignores the ones sent alongside it.
Update Task Recurring Profile Updates a task recurring profile. Turning it inactive pauses generation without losing the schedule or the count of tasks already generated.
Delete Task Recurring Profile Deletes a task recurring profile. Tasks it already generated stay where they are.

Milestones

List Milestones Lists milestones, optionally narrowed by project, responsible user, completion or due date. Due before with completion off is how a flow finds deadlines at risk.
Get Milestone Reads one milestone, including the task lists linked to it.
Create Milestone Creates a milestone in a project. The responsible user receives the late reminders, and a reminder window of zero means no reminder at all rather than one at the due moment.
Update Milestone Updates a milestone. Only what is supplied changes, except the linked task lists, which replace the previous set.
Set Milestone Complete Marks a milestone as reached, or reopens it. The tasks in its linked task lists are not changed.
Delete Milestone Deletes a milestone. The task lists that were linked to it stay, they simply lose the link.

Time Entries and Timers

List Time Entries Lists timesheet entries, optionally narrowed by project, task, user or client and by a date and time window. The read that every billing and utilization flow starts from.
Get Time Entry Reads one time entry. An entry with a start time and no end time is a running timer rather than a finished entry.
Create Time Entry Logs time against a task, either as a start and end time or as a date with a duration in seconds. A start with no end starts a running timer instead, which is what Start Timer is for.
Update Time Entry Updates a time entry. Duration can only be changed on an entry created with a date and a duration; on a start and end entry the length is changed by moving the end time.
Start Timer Starts a running timer on a task. A user can have only one timer running, so this is refused if one is already going.
Stop Timer Stops a running timer by giving its entry an end time. Paymo refuses to stop a timer whose total would be under a minute.
Get Running Timer Finds the timer a user currently has running. Returns nothing when none is, so a flow can branch on it cleanly.
Delete Time Entry Deletes a time entry. Also the only way to discard a running timer that is too short to stop.

Resource Bookings

List Bookings Lists resource scheduling bookings. Paymo requires at least one of assignment, task, project, user or a date window, so a flow always says what it is asking about.
Get Booking Reads one resource scheduling booking.
Create Booking Reserves a person's time on a task between two dates. A booking is made against a task assignment identifier rather than a task, so create or find the assignment first.
Update Booking Updates a resource scheduling booking. Only the fields supplied are changed.
Delete Booking Deletes a resource scheduling booking. The task assignment it was made against is untouched.

Discussions and Comments

List Discussions Lists project discussions, optionally narrowed to one project or to the ones a given user started.
Get Discussion Reads one discussion, optionally with the conversation itself or its attachments.
Create Discussion Starts a discussion in a project. The description accepts HTML, and replies are added afterwards as comments.
Update Discussion Updates a discussion's title or opening message. Replies are edited separately.
Delete Discussion Deletes a discussion along with every comment posted in it.
List Comment Threads Lists comment threads. In Paymo a comment hangs off a thread rather than off a task, discussion or file directly, so this is how the thread is found.
Get Comment Thread Reads one comment thread, and with comments included, the whole conversation attached to a task, discussion or file.
List Comments Lists comments in a thread. Given a task or discussion rather than a thread, List Comment Threads with comments included does it in one call instead.
Get Comment Reads one comment, optionally with anything attached to it.
Create Comment Posts a comment, saying what it is about with exactly one of task, discussion, file or thread. Paymo finds or creates the thread from whichever is given.
Update Comment Rewrites a comment's content. A comment cannot be moved to another thread.
Delete Comment Deletes a comment. Files attached to it are removed with it.

Files

List Files Lists files, optionally narrowed to a project, discussion, task or comment. Paymo documents this only with one of those, so a call giving none may return nothing useful.
Get File Reads one file record, including its download link, size and thumbnails. This returns metadata rather than bytes.
Upload File Uploads a file from a URL into Paymo, attaching it to a project, discussion, task or comment. Without a target the file waits in a temporary area with a token.
Attach File Attaches a file uploaded without a target, using the token Paymo returned together with exactly one destination.
Update File Renames a file or changes its description. Those are the only two fields Paymo accepts here.
Delete File Deletes a file from Paymo.

Expenses

List Expenses Lists expenses, optionally narrowed by client, project, date range or whether they have been invoiced. Filtering on uninvoiced is the usual way to find what still needs billing.
Get Expense Reads one expense, including its receipt link and whether it has been invoiced.
Create Expense Records an expense against a client and optionally a project. The currency is required, because an expense with none cannot be billed.
Update Expense Updates an expense. Only what is supplied changes, except the tags, which replace the previous set.
Set Expense Invoiced Marks an expense as billed, or unmarks it, without creating an invoice. Use it for expenses billed outside Paymo; billing one properly is done by naming it on an invoice line.
Download Expense Receipt Fetches the PDF rendering of an expense into FlowRunner file storage and returns a URL a later step can use.
Delete Expense Deletes an expense together with its receipt.

Invoices

List Invoices Lists invoices, optionally narrowed by client, status or date. Paymo has no paging, so a long history comes back in full unless it is filtered.
Get Invoice Reads one invoice. Without its items included you get only the totals and no line detail, and payments have to be asked for separately.
Create Invoice Creates an invoice with its lines. Leaving the number empty lets Paymo assign the next one and keep the sequence unbroken. A line can bill time by naming entry identifiers or bill an expense by naming its identifier, and doing either marks that time or expense as billed.
Update Invoice Updates an invoice. Sending items replaces the whole set of lines, so a line you keep has to be sent again with its own identifier and a line left out is deleted.
Set Invoice Status Sets an invoice's status by hand. Paymo moves it on its own when the invoice is sent, viewed or paid, so this is for the cases it cannot see, such as voiding one.
Download Invoice Fetches the PDF rendering of an invoice into FlowRunner file storage and returns a URL a later step can attach to an email or archive.
Delete Invoice Deletes an invoice together with its lines and payments. Time and expenses billed on it go back to being unbilled, which is the only route back from a wrong invoice.

Invoice Payments

List Invoice Payments Lists payments recorded against invoices, optionally narrowed to a single invoice.
Get Invoice Payment Reads one invoice payment. A payment has no currency of its own and uses the invoice's.
Create Invoice Payment Records a payment against an invoice. Paymo refuses a payment larger than what is outstanding, and moves the invoice to paid once the payments cover the total.
Update Invoice Payment Updates a payment. Changing the amount can move the invoice's status in either direction, up to paid or back down from it.
Delete Invoice Payment Deletes a payment. If the remaining payments no longer cover the total, Paymo moves the invoice back out of paid.

Recurring Invoices

List Invoice Recurring Profiles Lists the rules that raise invoices on a schedule, optionally narrowed to one client.
Get Invoice Recurring Profile Reads one invoice recurring profile, optionally with its lines, which are otherwise left out just as they are on an invoice.
Create Invoice Recurring Profile Creates a rule that raises an invoice on a schedule. Paymo runs these daily and raises an invoice once the start date has passed. Turning Auto Send on emails each new invoice to the client with nobody reviewing it first, which is the setting this page's human gate exists to replace.
Update Invoice Recurring Profile Updates an invoice recurring profile. Sending items replaces the whole set of lines, exactly as it does on an invoice.
Delete Invoice Recurring Profile Deletes a recurring profile so no further invoices are raised from it. Invoices it already raised are untouched.

Estimates

List Estimates Lists estimates, optionally narrowed by client, status or date. An estimate moves to invoiced once an invoice has been created from it.
Get Estimate Reads one estimate. Without its items included you get only the totals and no line detail.
Create Estimate Creates an estimate with its lines. Leaving the number empty lets Paymo assign the next one, and an accepted estimate becomes an invoice through Create Invoice.
Update Estimate Updates an estimate. Sending items replaces the whole set of lines, so include the identifier of every line to keep.
Set Estimate Status Sets an estimate's status by hand. Paymo moves it on its own when the estimate is sent, opened, accepted or invoiced, so this is for the cases it cannot see.
Download Estimate Fetches the PDF rendering of an estimate into FlowRunner file storage and returns a URL a later step can attach to an email.
Delete Estimate Deletes an estimate together with its lines. An invoice already created from it is untouched.

Templates

List Invoice Templates Lists the invoice templates set up for the company, with the identifier Create Invoice needs and a flag showing which is the default.
List Estimate Templates Lists the estimate templates set up for the company, with the identifier Create Estimate needs and a flag showing which is the default.

Workflows

List Workflows Lists the task workflows in the company. A workflow is the set of statuses a project's tasks can be in, which is what a board's columns show.
Get Workflow Reads one workflow, optionally with its statuses.
Create Workflow Creates a task workflow. Paymo gives every new one a starting and a finishing status, and further columns are added separately.
Update Workflow Renames a workflow or makes it the default for new projects.
Delete Workflow Deletes a workflow. Paymo refuses to delete one any project is still using, so move those projects first.
List Workflow Statuses Lists workflow statuses, optionally narrowed to one workflow. These are the board columns, and their identifiers are what Set Task Status needs.
Get Workflow Status Reads one workflow status.
Create Workflow Status Adds a status, in effect a board column, to a workflow. Paymo requires a color as well as a name.
Update Workflow Status Renames or recolors a workflow status. Its position is set by Paymo and cannot be changed here.
Delete Workflow Status Deletes a workflow status. Paymo refuses to delete one any task is still in, so move those tasks first.

Reports

List Reports Lists saved time reports. The content is left out of a listing, so read one to see its numbers.
Get Report Reads one report with its content, a flat list of items each carrying a type, a level and a number of seconds. A live report regenerates as it is read; a static one shows the figures as they stood when it was made.
Create Report Builds a time report and returns its content. Choose temporary when a flow only needs the numbers, because a temporary report is not stored and never appears in the Paymo application.
Update Report Rebuilds a saved report with new parameters. Paymo treats this as a full replacement, so send the whole definition again.
Download Report Fetches a report as a PDF or a workbook into FlowRunner file storage and returns a URL a later step can attach to an email.
Delete Report Deletes a saved report. The time entries it was built from are untouched.

Webhooks

List Webhooks Lists the webhooks the API key's own user created, each with the status code of its last delivery, which is the quickest way to spot one whose endpoint has stopped answering.
Get Webhook Reads one webhook including its last delivery status. The secret is never returned.
Create Webhook Subscribes an address to a Paymo event, choosing an object type and an action. For a flow the trigger is the better route, because it manages the subscription itself.
Update Webhook Updates a webhook. Paymo clears the recorded last delivery status as part of the update, so a failing webhook gets a clean slate.
Delete Webhook Deletes a webhook so Paymo stops posting to it. Paymo also removes one on its own once its address reports itself gone.

Triggers

1 triggers

Event Triggers

On Paymo Event Fires when a record changes in Paymo. Pick an object type and an action, or leave either as its any option to cover a whole family with a single subscription. A delete delivers only the identifier of what was removed rather than the record itself, so a flow needing the details has to read them before the deletion happens. Set a webhook secret on the connection and Paymo signs each delivery, which is what lets a flow gate on the verified field rather than trusting whatever arrives.

Frequently Asked Questions

What can FlowRunner do with Paymo?

FlowRunner agents can run Get Company, Update Company, and Get Current User in Paymo, plus 164 more actions.

Does connecting Paymo to FlowRunner require OAuth?

No. Paymo connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Paymo trigger a FlowRunner workflow automatically?

Yes. Paymo supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Paymo

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us