Clientary

Clientary, formerly Ronin, is the invoicing, time tracking, and project management platform. Agents manage clients and contacts, log time against projects, issue invoices and estimates, and record payments as work gets billed.

Verified 60 actions API key available

Clientary website Platform Documentation Capability data verified 2026-08-24

The monthly billing run opens for a client's active projects

List Hours returns the unbilled time on each project, grouped by the task it was booked against

Get Project reads the budget and rate settings the hours are supposed to be billed at

List Expenses finds the rebillable costs sitting against the same projects

Create Invoice builds the draft document from the unbilled hours and the recoverable expenses

The agent posts the draft, the budget position, and anything it would be writing off

An account lead confirms the write-offs and the overrun before Send Invoice goes to the client

What This Integration Enables

Clientary, the platform formerly called Ronin, is the system a services business runs between winning work and getting paid for it. Leads become clients, clients hold projects, projects hold tasks, tasks hold tracked hours, and hours become invoices. That chain is the product. It is not a ledger, and treating it like one is the usual mistake: the general ledger, the VAT return, and the bank reconciliation belong somewhere else, and what belongs here is the question of what was worked on and what it should be billed at.

FlowRunner agents work that chain end to end. They create clients and their contacts, open projects with their budget and rate settings, record tracked hours against tasks, capture rebillable expenses, assemble invoices and estimates from what is actually unbilled, send them, and record the payments that come back. One connection detail shapes all of it. Clientary issues a separate API token to every user and says why: so that platform activity can be attributed to a person. Time tracked through the API shows against the staff member whose token the connection holds. A shared integration user keeps automated activity out of individual timesheets, and a personal token puts it in. That is a decision to make on purpose before the first flow runs, not a credential detail to discover afterwards.

Without FlowRunner

Billing rebuilt every month Someone reassembles hours, expenses, and rates from three places before an invoice exists

Overruns found on the invoice The budget is exceeded quietly and the conversation happens after the client sees the number

Cleanup avoided Dormant records pile up because nobody is sure what removing one would take with it

With FlowRunner

The draft assembles itself Unbilled hours, rebillable expenses, and the project's own rate settings arrive as one proposed invoice

Overruns surfaced before sending The budget position is stated alongside the draft, while the number can still be discussed

Cleanup with its consequences shown Any removal is proposed with a full count of what sits underneath the record

Use Case Scenarios

Won deals become projects with a budget already on them

A deal closes in HubSpot or Pipedrive. The agent resolves the account with List Clients, calls Create Client when it is genuinely new, and adds the billing contact with Create Contact so the invoice has somewhere to go. Create Project opens the engagement with the budget and rate settings taken from the signed scope rather than from a default, and Create Task lays out the work items that hours will be booked against. If the account started life as a prospect, Create Lead and Update Lead have already been carrying it, and the lead record is closed out in the same run.
Estimates that turn into recurring revenue

Create Estimate builds the proposal with its line items, tax, and currency, and Send Estimate delivers it with the PDF attached. When the client accepts, Update Estimate moves it through its status and the agent decides which shape the work takes. One-off engagements become a project and an invoice. Retainers become a recurring schedule instead, through Create Recurring Schedule with its interval and payment terms, and Create Payment Profile stores the payment route that schedule will charge. Payments arriving through Stripe are matched back with Create Payment so the invoice closes without anyone opening it.
A dormant client sweep that shows its work

Once a quarter the agent looks for clients with no hours, no invoices, and no estimates inside a defined window. For each one it reads List Projects, List Invoices, List Estimates, and List Contacts and builds a plain count of what sits underneath the record, along with anything List Payments shows as still outstanding. That summary goes to the account lead in Slack alongside a copy written into Google Sheets for the record. The agent proposes. It does not remove anything, for the reason below.

Human-in-Loop Highlight

Delete Client is the most destructive operation in this connector, and the vendor states its behavior plainly: removing a client also removes every project, invoice, estimate, and contact under it, and the deletion is permanent. Delete Invoice behaves the same way one level down, taking the invoice's items and its payments with it. What makes this a gate rather than a warning is what the API does not offer. There is no archive action for a client anywhere in this connector, and no soft delete. So an agent asked to tidy a client list has exactly two options: leave the record alone, or destroy the only remaining account of what that client was billed and what was delivered. Those are not close enough together for a rule to pick between them. So the agent gathers instead. It posts the client name, the count of projects, invoices, estimates, and contacts underneath it, the total invoiced, whether any invoice is still unpaid, and whether any unbilled hours are still sitting on a project. The account lead decides. Most of the time the answer is to leave it, and the sweep exists to prove that with numbers rather than to argue for deletion. When the answer is to remove one, a person has said so with the full list of what goes with it in front of them.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

60 actions

Clients and Contacts

List Clients Lists the clients in the account, with paging and an updated-since filter for incremental syncs.
Get Client Reads one client by its ID.
Create Client Creates a client, which is the container its contacts, projects, and invoices hang off.
Update Client Updates a client. Only the fields you send are changed.
Delete Client Deletes a client and every project, invoice, estimate, and contact under it. This cannot be undone, which is why this page holds it behind a person.
List Contacts Lists the contacts in the account, or the contacts of one client.
Get Contact Reads one contact by its ID.
Create Contact Creates a contact under a client, which is where the email address an invoice is sent to usually lives.
Update Contact Updates a contact. Only the fields you send are changed.
Delete Contact Deletes a contact.

Projects and Tasks

List Projects Lists the projects in the account, or the projects of one client.
Get Project Reads one project by its ID, with its budget and rate settings. The read that tells a billing flow what the hours should be charged at.
Create Project Creates a project against a client, with its budget and rate settings.
Update Project Updates a project. Only the fields you send are changed.
Delete Project Deletes a project.
List Tasks Lists the tasks in the account, or the tasks of one project. Tasks are what tracked hours are booked against.
Get Task Reads one task by its ID.
Create Task Creates a task, which tracked hours can then be booked against.
Update Task Updates a task. Only the fields you send are changed.
Delete Task Deletes a task.

Time Tracking

List Hours Lists the tracked hours on a project, optionally only the unbilled ones. The source a billing run is built from.
Get Hour Reads one tracked hour entry by its ID.
Create Hour Records tracked hours against a project and task. The time is attributed to the staff user whose API token the connection holds, so which token you connect with decides whose timesheet this lands on.
Update Hour Updates a tracked hour entry. Only the fields you send are changed.
Delete Hour Deletes a tracked hour entry.

Invoices

List Invoices Lists the invoices in the account, or those of one client, project, or recurring schedule.
Get Invoice Reads one invoice by its ID, with its items and tax breakdown.
Create Invoice Creates an invoice with its line items, tax, and currency. The assembly step at the end of a billing run.
Update Invoice Updates an invoice. Line items are edited in place rather than replaced, so a single line can be corrected without restating the document.
Delete Invoice Deletes an invoice along with its items and its payments. This cannot be undone.
Send Invoice Emails an invoice to a list of addresses, optionally with the PDF attached and a copy to yourself.

Estimates

List Estimates Lists the estimates in the account, or those of one client or project.
Get Estimate Reads one estimate by its ID, with its items and its numeric status.
Create Estimate Creates an estimate with its line items, tax, and currency.
Update Estimate Updates an estimate, including moving it to accepted, declined, or canceled through its numeric status.
Delete Estimate Deletes an estimate.
Send Estimate Emails an estimate to a list of addresses, optionally with the PDF attached.

Payments

List Payments Lists the payments recorded in the account.
Create Payment Records a payment against an invoice, which is how a settlement captured elsewhere closes the document here.
Delete Payment Deletes a payment from an invoice.
List Payment Profiles Lists the stored payment profiles of a client, which is what recurring schedules charge.
Create Payment Profile Stores a payment profile against a client, so recurring schedules can charge it.
Delete Payment Profile Deletes a stored payment profile from a client, after which the schedules relying on it have nothing to charge.

Expenses

List Expenses Lists the expenses in the account, or those of one client or project, over a date range.
Get Expense Reads one expense by its ID.
Create Expense Records an expense, optionally against a client or project so it can be rebilled.
Update Expense Updates an expense. Only the fields you send are changed.
Delete Expense Deletes an expense.

Leads

List Leads Lists the leads in the account, which are prospects that have not become clients yet.
Get Lead Reads one lead by its ID.
Create Lead Creates a lead, which is a prospect that has not become a client yet.
Update Lead Updates a lead. Only the fields you send are changed.
Delete Lead Deletes a lead.

Recurring Schedules

List Recurring Schedules Lists the recurring invoice schedules in the account.
Get Recurring Schedule Reads one recurring invoice schedule by its ID, with its items.
Create Recurring Schedule Creates a recurring invoice schedule with its items, interval, and payment terms. The shape a retainer takes.
Update Recurring Schedule Updates a recurring invoice schedule. Items are edited in place rather than replaced.
Delete Recurring Schedule Deletes a recurring invoice schedule.

Staff

List Staff Lists the staff users on the account. Staff is read only through the API, so this is a lookup rather than a management surface.
Get Staff Member Reads one staff user by their ID, which is how a flow resolves whose timesheet an entry will land on.

Frequently Asked Questions

What can FlowRunner do with Clientary?

FlowRunner agents can run List Clients, Get Client, and Create Client in Clientary, plus 57 more actions.

Does connecting Clientary to FlowRunner require OAuth?

No. Clientary connects to FlowRunner with an API key, no OAuth flow required.

Can Clientary trigger a FlowRunner workflow automatically?

Clientary doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Clientary

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us