Integration
Connect Paymo and wethod
When New Client fires in Paymo, your agent runs Create a client in wethod, or New Client in wethod to Create Client in Paymo. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Paymo and wethod to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Paymo and wethod can do together
From Paymo to wethod
When New Client in Paymo
then Create a client in wethod
When New Client Contact in Paymo
then Create a contact in wethod
From wethod to Paymo
When New Client in wethod
then Create Client in Paymo
When New Contact in wethod
then Add client contact in Paymo
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Paymo and wethod
Triggers and actions 23 triggers · 90 actions
Trigger
New ClientTriggers when a new client is created in Paymo.
Trigger
New Client ContactTriggers when a new client contact is created in Paymo.
Trigger
New EstimateTriggers when a new estimate is created in Paymo.
Trigger
New ExpenseTriggers when a new expense is created in Paymo.
Trigger
New InvoiceTriggers when a new invoice is created in Paymo.
Trigger
New ProjectTriggers when a new project is created in Paymo.
Trigger
New ReportTriggers when a new report is created in Paymo.
Trigger
New TaskTriggers when a new task is created in Paymo.
Trigger
New Task ListTriggers when a new task list is created in Paymo.
Trigger
New Time EntryTriggers when a new time entry is logged in Paymo (entries from the last 30 days are checked).
Trigger
Timer StartedTriggers when someone starts a timer in Paymo.
Trigger
Timer StoppedTriggers when a timer is stopped in Paymo, delivering the finished time entry (timers from the last 7 days are checked).
Trigger
Updated ClientTriggers when a client is updated in Paymo.
Trigger
Updated ProjectTriggers when a project is updated in Paymo.
Trigger
Updated TaskTriggers when a task is updated in Paymo.
Trigger
Updated Time EntryTriggers when a time entry is updated in Paymo.
Action
Add client contactCreates a contact person under an existing Paymo client.
Action
Add estimateCreates an estimate for a client in Paymo, including its line items.
Action
Create ClientCreates a new client in Paymo.
Action
Create ExpenseCreates a new expense for a client in Paymo.
Action
Create InvoiceCreates a new invoice for a client in Paymo.
Action
Create ProjectCreates a new project in Paymo.
Action
Create TaskCreates a new task in a Paymo project or task list.
Action
Create Task ListCreates a new task list in a Paymo project.
Action
Create Time EntryLogs a new time entry against a Paymo task.
Action
Delete clientDeletes a client in Paymo, along with all of its projects, tasks, task lists and time entries.
Action
Delete expensePermanently deletes an expense in Paymo.
Action
Delete invoicePermanently deletes an invoice in Paymo.
Action
Delete projectDeletes a Paymo project, along with all its task lists, tasks, discussions, files and time entries.
Action
Delete taskDeletes a task, along with all time entries logged for it.
Action
Delete time entryDeletes a time entry (or a running timer) from Paymo.
Action
Find Client by EmailFinds a Paymo client by email address.
Action
Find TaskFinds a Paymo task by name, optionally within one project.
Action
Get clientReturns one Paymo client by its ID, including address, contact details and status.
Action
Get estimateReturns a Paymo estimate by ID, optionally with its line items and related client, invoice or template.
Action
Get expenseReturns a single Paymo expense by its ID, including amount, currency, date, notes, tags and receipt.
Action
Get invoiceReturns a single Paymo invoice by its ID, including totals, status, dates and links; optionally includes its line items, payments, client or template.
Action
Get projectReturns a single Paymo project by its ID, including its client, billing settings and assigned users.
Action
Get time entryReturns a single Paymo time entry by its ID, optionally with its task, user or invoice item.
Action
List client contactsReturns the client contacts in your Paymo account, optionally only those of one client.
Action
List clientsReturns the clients in your Paymo account, optionally filtered to active or archived clients.
Action
List estimatesReturns the estimates in your Paymo account, optionally filtered by client, status or total.
Action
List expensesReturns the expenses in your Paymo account, optionally filtered by client, project, date or invoiced status.
Action
List invoicesReturns the invoices in your Paymo account, optionally filtered by client, status, total or other invoice attributes.
Action
List projectsReturns the projects in your Paymo company, optionally filtered (for example by client, active status or assigned user).
Action
List tasksReturns the tasks in your Paymo account, optionally filtered by project, task list, completion or assignee.
Action
List time entriesReturns time entries from Paymo, optionally filtered by project, task, user, client or a time interval.
Action
Restart timerStarts a running timer again on a task by creating a new time entry with a start time and no end time. Fails if the user already has a timer running.
Action
Stop timerStops a running Paymo timer by setting its end time, turning it into a completed time entry.
Action
Update clientUpdates an existing Paymo client's details, such as name, contact info and address, or archives/reactivates it. Only the fields you fill in are changed.
Action
Update client contactUpdates an existing contact of a Paymo client. Only the fields you fill in are changed.
Action
Update expenseUpdates an existing expense in Paymo. Only the fields you fill in are changed.
Action
Update invoiceUpdates an existing Paymo invoice — its dates, client, taxes, text blocks, status or line items. Only the fields you fill in are changed.
Action
Update projectUpdates an existing Paymo project's details, billing settings, assigned users or status. Only the fields you fill in are changed.
Action
Update taskUpdates an existing Paymo task; only the fields you fill in are changed.
Action
Update time entryUpdates an existing Paymo time entry, changing only the fields you fill in (task, user, times, date, duration, description or billed status).
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Paymo
Paymo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Paymo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Paymo to StripeStripe is a payment processing platform for online businesses.
Paymo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Paymo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Paymo to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into wethod
HubSpot to wethodHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to wethodSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to wethodSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to wethodGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to wethodGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to wethodGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Paymo and wethod, answered
What can start an automation from Paymo?
Any of Paymo's 16 triggers in the catalog, including New Client, New Client Contact, New Estimate and New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in wethod when something happens in Paymo?
Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from wethod to Paymo?
Yes. When something happens in wethod, your agent can act in Paymo too. This page covers both directions: wethod's triggers and Paymo's actions are listed here as well.
Do I have to build a connector for Paymo or wethod?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Paymo and wethod without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.