Clientjoy

Connect AI agents to Clientjoy, an agency CRM covering leads through invoices. Agents qualify leads into customers, send proposals, raise invoices and line items, and read the forms a client submitted.

33 actions API key available

Platform Documentation ↗

A signed proposal or a completed delivery milestone lands from the project system

List Workspaces confirms which client workspace the agent is writing into

List Customers matches the client so the invoice attaches to the right record

List Items and List Taxes resolve the catalog lines and tax codes to bill

Create Invoice raises the bill against the customer with those lines

The account lead is shown the drafted invoice, its workspace, and its total

Account lead approves before the batch of invoices is sent to clients

What This Integration Enables

Clientjoy is an agency's whole client lifecycle in one workspace: leads at one end, invoices at the other, with proposals, customers, contacts, catalog items, and forms in between. That breadth is the reason to automate it and also the reason to be careful. The same connector that qualifies a lead is the one that raises a bill, and the difference between those two writes is not technical, it is commercial. An agency automating Clientjoy is not connecting a CRM, it is putting an agent in the path between delivery and revenue.

FlowRunner agents work that path: listing and creating leads with their stage, source, assignee, and deal value, managing customers and their contacts, generating proposals and invoices from catalog items, reading forms and email records, and pulling the workspace reference data that keeps writes valid. Two things shape how those agents are built. First, one API token can reach several workspaces, and every request carries a configured Workspace ID header, so the workspace is a parameter rather than a property of the credential. Second, the public documentation enumerates the Create Lead body in full but not the customer, proposal, invoice, and item payloads, so those actions take a free-form data object whose fields must match the Clientjoy schema. Clientjoy ships no FlowRunner triggers; instead the Create Webhook action registers a Clientjoy webhook that posts to a URL of your choosing on lead, customer, proposal, and invoice events, and returns a secret key you can use to verify the delivery. Between the workspace header and the unenumerated bodies, the money-side writes are exactly where the digital andon cord belongs.

Without FlowRunner

Billing rebuilt from memory Someone reads the project notes and reconstructs what to invoice each month

Leads that sit outside the CRM Ad and form leads live in a spreadsheet until someone finds time to import them

Reference data hard-coded Stage, source, and tax IDs get pasted into scripts and go stale silently

With FlowRunner

Invoices drafted from delivery Completed milestones become invoice lines without a monthly reconstruction

Leads captured with their context Every inbound lead arrives with stage, source, assignee, and deal value set

Reference data read at run time Stages, sources, currencies, and taxes are resolved from the workspace each run

Use Case Scenarios

Inbound leads that land fully formed

Leads arrive from ad platforms and landing pages. The agent calls Get Lead Stages and Get Lead Sources to resolve this workspace's own pipeline values, List Users to pick an assignee, and Get Custom Fields to find the account's extra fields. Create Lead then writes the record with contact, company, stage, source, assignee, deal value, and currency populated, because Clientjoy's public documentation enumerates that body in full and the agent can fill it precisely. A row goes into Google Sheets for the acquisition report and the assignee hears about it in Slack. Nobody spends Monday importing a spreadsheet.

Onboarding that runs from the signed proposal

A proposal comes back signed. The agent calls List Proposals to confirm the record, then Create Customer to convert the lead into a client, List Items to pull the retainer and setup lines from the catalog, and Create Invoice to raise the first bill. List Currencies and List Taxes resolve the right currency and tax treatment for that client rather than assuming the workspace default. The kickoff email goes out through Gmail with the invoice detail attached. The account manager spends the hour on the kickoff call, not on the paperwork behind it.

A revenue view that does not require an export

On a schedule, the agent pages through List Invoices and List Proposals with the pagination limit the API allows, and writes the current state into a warehouse or a sheet. Invoices past their due date are named individually with the client, the amount, and the days overdue. Proposals that have sat unopened past the agency's usual response window are named separately, because that is a different problem with a different owner. The agency principal reads two short lists instead of a full export, which is the whole point of treating overdue and unanswered as automation exceptions rather than as report rows.

Human-in-Loop Highlight

An invoice is a claim for money made against a named client, and in Clientjoy it is also a write into whichever workspace the header says. Both halves of that sentence are places an automation can go wrong quietly. The Workspace ID is configuration, not credential, so an agency running separate workspaces per brand can point a correct token at the wrong ledger. And because the public documentation does not enumerate the invoice create body, Create Invoice takes a free-form data object, which means a malformed line item is a schema problem the agent cannot catch against a published contract. So the billing agent drafts and stops. It calls List Workspaces to resolve the configured ID into a human-readable workspace name, builds the invoices from delivery data, and posts the summary to the account lead in Slack: "Eleven invoices drafted in workspace Northlight Studio, total USD 84,200. Highest is Harbour Group at USD 19,500 across three retainer lines and one overage line. Two clients are on a currency other than the workspace default. Approve, or open the drafts?" Only after the answer does the agent run Create Invoice across the batch. Delete Invoice cannot undo an invoice a client has already received, so the check happens before the send, not after it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

33 actions

Leads

List Leads Returns leads with page and limit paging, up to the API maximum per page. Used for pipeline reporting and for syncing leads into a downstream system.
Create Lead Creates a lead with contact, company, stage, source, assignee, deal, and currency parameters, since this is the one create body the public documentation enumerates in full. Used to capture inbound demand at the moment it arrives.
Delete Lead Permanently deletes a lead. Cannot be undone, so agents put deletions behind a human decision.
Get Lead Stages Returns the workspace's pipeline stages. Used to resolve a real stage ID at run time rather than hard-coding one that will go stale.
Get Lead Sources Returns the workspace's lead sources. Used so attribution reporting reads values the workspace actually defines.

Customers and Contacts

List Customers Returns customers with paging. Used to match an incoming record against an existing client before creating a duplicate.
Get Customer Retrieves a single customer. Used to load billing and contact context before an invoice or proposal write.
Create Customer Creates a customer from a free-form data object whose fields must match the Clientjoy customer schema. Used to convert a won lead into a client record.
Update Customer Updates an existing customer. Used to keep billing details and ownership current from an external source of truth.
Delete Customer Permanently deletes a customer. Cannot be undone.
List Contacts Returns contacts. This resource is list-only in the public API, so agents read contacts rather than writing them here.

Proposals

List Proposals Returns proposals with paging. Used to track what has gone out and what has come back.
Create Proposal Creates a proposal from a free-form data object matching the Clientjoy proposal schema. Used to generate the client document as part of an onboarding flow.
Delete Proposal Permanently deletes a proposal. Cannot be undone.

Invoices and Catalog

List Invoices Returns invoices with paging. Used for revenue reporting and overdue detection on a schedule.
Get Invoice Retrieves a single invoice. Used to confirm state and totals before a reminder or a downstream accounting write.
Create Invoice Raises an invoice from a free-form data object matching the Clientjoy invoice schema. Because it is a claim for money in a specific workspace, agents draft and a person approves.
Update Invoice Updates an existing invoice. Used for corrections before delivery and for status changes after payment.
Delete Invoice Permanently deletes an invoice. Cannot be undone, and it cannot unsend one a client already has.
List Items Returns the catalog items available for proposals and invoices. Used to build billing lines from real catalog entries rather than free text.
Create Item Adds a catalog item. Used to keep the billing catalog in step with the agency's service list.
Update Item Updates an existing catalog item. Used when pricing or naming changes.
Delete Item Permanently deletes a catalog item. Cannot be undone.
List Taxes Returns the workspace's tax definitions. Used so an invoice carries the right tax treatment for the client's jurisdiction.

Forms and Email

List Forms Returns the workspace's forms. Used to resolve which form a submission belongs to.
Get Form Retrieves a single form. Used to read the field definitions behind a submission before mapping it onto a lead.
List Emails Returns email records. This resource is list-only in the public API, so agents read the email history rather than sending through it.

Workspace Reference Data

List Currencies Returns the currencies available in the workspace. Used to bill a client in the currency they contracted in.
List Users Returns the workspace's users. Used to assign leads and customers to real people.
List Workspaces Returns the workspaces the API token can reach with their IDs. Used to resolve the configured Workspace ID into a name a person can recognize before a batch write runs.
Get Custom Fields Returns the workspace's custom field definitions. Used to drive validation and enrichment in other steps of a flow.

Webhooks

Create Webhook Registers a Clientjoy webhook that posts to a URL of your choosing on lead, customer, proposal, and invoice events, returning a secret key used to sign delivered payloads. Used to fan events out to chat or email, since this connector ships no triggers of its own.
Delete Webhook Removes a registered webhook. Cannot be undone, so a subscription other flows depend on is removed deliberately.

Frequently Asked Questions

What can FlowRunner do with Clientjoy?

FlowRunner agents can run List Leads, Create Lead, and Delete Lead in Clientjoy, plus 30 more actions.

Does connecting Clientjoy to FlowRunner require OAuth?

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

Can Clientjoy trigger a FlowRunner workflow automatically?

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

Start building with Clientjoy

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us