WHMCS
FinanceConnect AI agents to WHMCS, the billing and automation platform for hosting businesses. Agents manage clients, create and pay invoices, place and accept orders, work support tickets, record transactions, and call any other WHMCS API action directly.
What This Integration Enables
WHMCS is the system of record for a hosting business: clients, invoices, orders, provisioning, and support in one install. What it automates well is the chain inside itself, a paid invoice activates a service, an accepted order provisions a server. What it cannot see is everything that happens outside the install: the Stripe charge that cleared on another page, the signup that landed in a storefront, the reseller order placed over email. FlowRunner agents work those seams, feeding external events into WHMCS through its admin API and pulling billing truth back out. - Onboard customers end to end: create the client, place the order, and accept it to trigger provisioning - Reconcile external gateway payments onto the right invoice so the paid-invoice workflow fires - Open, read, and reply to support tickets as part of a broader helpdesk automation - Sync clients, services, and transactions into reporting tools without exports - Reach any other WHMCS API action through Call API Action when a workflow needs domain registration or module operations The connector's write operations are where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline matters: agents do the matching and drafting at machine speed, and the operations that provision infrastructure or lock out a customer wait for a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signup to provisioned service without the overnight gap
An order lands in [Shopify](/integrations/shopify) or a signup form posts to the flow. The agent calls Get Clients to check for an existing account, then Add Client to create one, then Add Order for the hosting plan with the right billing cycle. Clean orders get Accept Order immediately and the customer's welcome email goes out minutes after purchase. Orders that trip a risk check wait in Pending until a person clears them. The provisioning chain WHMCS already owns takes it from there.
The gateway payment that marks its own invoice paid
A payment settles in [Stripe](/integrations/stripe). The agent matches the charge to the client with Get Clients, finds the open invoice with Get Invoices filtered to Unpaid, and calls Add Invoice Payment with the gateway transaction ID. WHMCS fires its paid-invoice workflow: service activation, receipt, done. Charges that match no open invoice do not get guessed at, they go to a person with the candidates listed, and Add Transaction records the payment once someone names the destination.
Support that reads the account before it replies
A new ticket appears. On a schedule, the agent sweeps Get Tickets for open items, pulls each thread with Get Ticket, and gathers the client's context: Get Client Products for service status and due dates, Get Invoices for anything overdue. It posts the assembled picture to [Slack](/integrations/slack) and drafts a reply. A support engineer edits or approves, and Add Ticket Reply posts it as the operator. The lookup work disappears; the judgment stays human.
Human-in-Loop Highlight
Accept Order is the point of no return in a hosting business. Accepting a pending order provisions real infrastructure, runs registrar and module actions, and sends the customer a welcome email with credentials. Accept a fraudulent order and you have handed an abuser a server under your IP space; claw-backs, abuse reports, and blacklist damage follow. So the onboarding agent accepts only orders that pass every check, and posts the rest: "Order 4412, first-time client, billing country and card country differ, 24-month plan paid upfront. Accept, hold, or mark fraud?" A person answers, and only then does Accept Order run. The same discipline applies to Close Client, which locks a customer out of their own account: an agent can recommend it for confirmed abuse, but a person confirms it.
Agent Capabilities
22 actionsClients
5- Get Clients Retrieves a paginated client list with free-text search across name, email, and company, plus status filtering. The lookup step before any client write.
- Get Client Details Retrieves the full profile of a single client by ID or email, including billing information, custom fields, and optional account statistics.
- Add Client Creates a new client account with contact details and address. Can suppress the welcome email and assign a client group, currency, or language.
- Update Client Updates a client's profile fields. Only the fields provided change, which makes it safe for targeted enrichment passes.
- Close Client Closes a client account so they can no longer log in, while records and history are retained. Reversible via Update Client, but gated in practice because it cuts off a customer.
Invoices
5- Get Invoices Retrieves invoices filtered by client or status such as Unpaid or Overdue. The sweep behind dunning and reconciliation workflows.
- Get Invoice Retrieves one invoice in full: line items, taxes, totals, status, and recorded transactions.
- Create Invoice Creates an invoice with line items, dates, payment method, and an option to email it to the client on creation.
- Update Invoice Updates an invoice's top-level fields such as status, dates, and notes.
- Add Invoice Payment Records a payment against an invoice, marking it fully or partially paid. Applying a payment can trigger service activation and receipts, so agents attach the gateway transaction ID for an auditable trail.
Orders
3- Get Orders Retrieves orders filtered by client or status. The review queue for signups awaiting acceptance.
- Add Order Places an order for a product or domain with a billing cycle, promo code, and optional auto-provisioning flags.
- Accept Order Accepts a pending order and triggers provisioning. The operation this page's human gate exists for.
Products
2- Get Products Retrieves the product catalog with per-cycle pricing, filterable by product or group.
- Get Client Products Retrieves the services a client owns, with status, next due date, recurring amount, and assigned server. The context step behind support and renewal workflows.
Tickets
4- Get Tickets Retrieves support tickets filtered by client, department, status, or subject.
- Get Ticket Retrieves one ticket with its full chronological reply thread.
- Open Ticket Opens a ticket in a department on behalf of a client, with subject, message, and priority, optionally linked to a service or domain.
- Add Ticket Reply Adds a reply posted as a client or as an admin, with control over the resulting status and notification emails.
Billing
2- Get Transactions Retrieves recorded payment transactions filtered by client, invoice, or gateway transaction ID, including amounts, fees, and gateway.
- Add Transaction Records a standalone transaction, optionally linked to a client or invoice. Used for logging manual or external payments.
Advanced
1- Call API Action Calls any WHMCS API action by name with arbitrary parameters. The escape hatch for operations without a dedicated action, such as domain registration or module commands. Credentials are added automatically.
Frequently Asked Questions
What can FlowRunner do with WHMCS?
FlowRunner agents can run Get Clients, Get Client Details, and Add Client in WHMCS, plus 19 more actions.
Does connecting WHMCS to FlowRunner require OAuth?
No. WHMCS connects to FlowRunner with an API key, no OAuth flow required.
Can WHMCS trigger a FlowRunner workflow automatically?
WHMCS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with WHMCS
$100 in credits. No card required. Connect in minutes.