WaymarqIntegrations
Waymarq fits around the tools you already use
Push what happens in Waymarq out to your own systems, or drive Waymarq programmatically from somewhere else. More integrations are on the way — and everything here is documented, not just advertised.
Available now
Webhooks
Send events anywhere that accepts a URL.
When something happens — a quote is accepted, a client reports a problem, a task is finished — we send it to your own systems, or to Zapier, Make and n8n. Signed, retried, and logged so you can see exactly what was sent and what came back.
MCP server
Connect the AI assistant you already use.
Claude, Cursor and ChatGPT can read your plan and keep it up to date while you work — ask what to pick up next, mark something done, log the time, without leaving the conversation. Nine tools shaped around what people ask for, a URL and a token, nothing to install.
Command-line client
Anywhere there is a shell.
npx @waymarq/cli — no dependencies, --json on every command. For CI steps, git hooks, coding agents that can only run commands, and anyone who would rather type than click. Commit a .waymarq.json and the repository knows which project it belongs to.
REST API
Read and write everything, programmatically.
A full API over projects, phases, tasks, clients, opportunities and quotes — the same services the app itself uses, with the same permissions. Point a coding assistant at it and let it set a project up for you.
Calendar feed
Your deadlines in the calendar you already use.
Subscribe to project and task dates from Google Calendar, Outlook or Apple Calendar and they sit alongside everything else in your week. Read-only by design rather than a two-way sync — nothing to reconcile, and nothing your calendar app can push back and break. The feed shows only what you can already see in Waymarq.
Slack
Post what happens into a channel.
Events arrive as readable messages in a channel you choose — your own, or one shared with a client so they can see progress without logging in.
GitHub & Bitbucket
See the work behind a task.
Commits, branches and pull requests appear on the tasks they mention, so a task shows whether anyone has actually touched the code. Switch it on per repository and it will move tasks along too — but only on what you write, never on a guess: "fixes WR-11" or a merged pull request marks it done, a plain mention moves it to in progress, and nothing ever moves backwards.
Zapier, Make & n8n
Wire Waymarq to anything, without writing code.
Both directions work today. Catch a Waymarq event in a scenario and act on it — an accepted quote into a spreadsheet, a support request into whatever your team watches — or go the other way and have an automation create work here from a form, an inbox, or a tracker you have not finished moving off yet. There is no listed app in their directories, so you paste a URL rather than picking Waymarq from a menu.
Where we’re heading
The direction we want to take Waymarq. Some of these are already scoped, others are here because people keep asking — none of them have a date, and we would rather say so than invent one. Tell us which matters most and it moves up.
Xero
Invoicing, without doing it twice.
Raise invoices in Xero from your project payment schedule and logged billable time, and see what has actually been paid. We stop at "here is what should be invoiced" — Xero owns the invoice itself.
QuickBooks
The same, for the other half of the world.
Everything the Xero integration does, for people whose accountant asked for QuickBooks instead. Same principle: we say what should be billed and what is still outstanding, your accounting package owns the document.
Stripe
Let a client pay the moment they accept.
Put a payment link on an accepted quote or a statement, and mark the work paid automatically when the money lands — instead of chasing a bank transfer and reconciling it by hand a fortnight later.
Microsoft Teams
Slack, for the organisations that use Teams.
The same event messages that already go to Slack, posted into a Teams channel instead. Mostly a matter of speaking the other message format — the events and the delivery machinery already exist.
Google Drive & Dropbox
Attach files that already live somewhere else.
Link a brief, a drawing or a design straight from the drive it already sits in, rather than uploading a second copy that starts drifting out of date the moment someone edits the original.
HubSpot & Pipedrive
Bring an existing pipeline with you.
Import clients and open deals rather than retyping them, and keep a deal in step if you are not ready to move your whole sales process over at once.
Gmail & Outlook
Keep the client thread with the client.
Log the emails that actually decided something against the client record, so the history of a project is not split between here and an inbox only one person can search.
Something not listed?
Webhooks and the REST API between them cover most things without waiting for us. Webhooks push events out as they happen; the API reads and writes everything the app itself can. If you use Zapier, Make or n8n, that’s usually all you need to connect Waymarq to a few hundred other tools.