FlowRunner
PricingContact
Theme
Start Free

Automate cPanel hosting administration from your flows. Agents provision and remove email accounts, list databases, domains, and FTP accounts, monitor disk usage, and call any UAPI or WHM function through generic escape hatches.

9 actions API key available
cPanel website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A client cancellation lands from the billing system
List Email Accounts inventories every mailbox on the client's domain
List FTP Accounts and List Databases complete the audit of what the account actually holds
The agent assembles the teardown plan: what needs exporting, what gets removed, and in what order
The plan posts to the operations channel with the mailbox list, FTP logins, and current disk usage attached
The account manager approves the teardown only after confirming the retention export completed
Delete Email Account removes each approved mailbox, and UAPI Call clears the remaining forwarders

What This Integration Enables

For agencies, MSPs, and anyone running client sites on cPanel servers, hosting administration is the purest form of operational toil: work too small to staff and too important to skip. A mailbox request is a five-minute task that waits two days in a queue. A disk quota fills silently until a client's site is down. An offboarded client's FTP account outlives the relationship by a year. This connector puts that entire category of work under agent control, with the two generic escape hatches, UAPI Call and WHM API Call, extending reach to any function cPanel or WHM exposes. - Provision and remove email mailboxes with quotas, as accounts are created and churned - Inventory domains, databases, and FTP accounts before migrations, rotations, and teardowns - Monitor disk-quota usage and alert before storage becomes an outage - Call any UAPI module and function, or any WHM API 1 function with a root or reseller token, when the dedicated actions do not cover it The lifecycle asymmetry drives the design: creating a mailbox is cheap and reversible, so agents do it freely. Deleting one destroys stored mail permanently, so that path runs through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate every time.

Without FlowRunner

Hosting by ticket queue Every mailbox request and quota bump waits behind a person with cPanel access
Offboarding that drifts Cancelled clients keep live mailboxes and FTP logins for months, at your cost and your risk
Disk full means site down Storage limits announce themselves as outages, usually on a weekend

With FlowRunner

Provisioning in minutes Accounts exist moments after the business event that justifies them
Teardown as a process Inventory, export, then approved deletion, in that order, with a record
Storage watched continuously Usage is swept on a schedule and the alert arrives while there is still headroom

Use Case Scenarios

Client onboarding without the setup ticket

A new client goes active, and the flow gets to work: List Domains confirms the client's domain is configured and finds its document root, Create Email Account provisions the branded mailboxes with quotas matching the plan, and UAPI Call adds the forwarders the dedicated actions do not cover. The welcome email with login instructions goes out through [Gmail](/integrations/gmail-service) before the account manager has finished the kickoff call.

The disk usage sentinel

Nightly, Get Disk Usage sweeps every managed account. Accounts crossing the warning threshold trigger a closer look: List Databases identifies which databases are consuming the space, and the finding posts to [Slack](/integrations/slack) with bytes used, the limit, and the growth trend from prior sweeps. The conversation about a quota upgrade happens with the client before their site goes down, which is a different conversation entirely.

The access audit that actually happens

Quarterly, an agent inventories every account: List FTP Accounts with home directories and quotas, List Email Accounts per domain, List Domains with addon and parked domains included. The inventory lands in [Google Sheets](/integrations/google-sheets) diffed against last quarter: FTP logins nobody can attribute, mailboxes for staff who left, domains still parked on expired projects. Each flagged item becomes a review task for a person, because an access audit that only lists things is a spreadsheet, not security.

Human-in-Loop Highlight

Delete Email Account does not just remove a login; it permanently destroys the mailbox and every message stored inside it, and cPanel offers no undo. In an offboarding, that mailbox may hold the only copy of years of client correspondence, the kind of record that legal holds and handover disputes are made of. So the teardown agent never deletes on its own schedule. It inventories the domain's mailboxes, checks the retention export against the list, and presents the account manager with exactly what is about to cease existing: "4 mailboxes on clientdomain.com, export completed yesterday, 2.1 GB total. Confirm deletion of each." Only the confirmed addresses are passed to Delete Email Account. Provisioning runs at machine speed because a wrong mailbox can be deleted; deletion waits for a person because a wrong deletion cannot be provisioned back.

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

9 actions

Generic API

2
  • UAPI Call Makes a generic cPanel UAPI call to any module and function on port 2083, with parameters as a JSON object, returning the standard UAPI envelope of data, status, errors, and messages. The escape hatch for every UAPI operation without a dedicated action.
  • WHM API Call Makes a generic WHM API 1 call to any function on port 2087, with api.version=1 added automatically. Requires a WHM-level root or reseller token. The route to server-administration operations across accounts.

Email

3
  • List Email Accounts Lists the POP/IMAP mailboxes on the account, optionally filtered by domain, returning each address, login, and domain. The inventory step before provisioning and before every teardown.
  • Create Email Account Creates a mailbox on a domain with the local part, a password, and an optional quota in megabytes, with 0 for unlimited storage.
  • Delete Email Account Permanently deletes a mailbox and its stored messages. Cannot be undone, which is why it sits behind this page's human gate.

Databases

1
  • List Databases Lists the MySQL and MariaDB databases on the account with each database's name, disk usage, and associated users. The inventory before backups, migrations, and grants.

Domains

1
  • List Domains Retrieves all domains configured on the account, including the main domain, addon domains, subdomains, and parked aliases with their document roots. The discovery step before creating mailboxes or DNS records.

FTP

1
  • List FTP Accounts Lists the FTP accounts with each login, home directory, and disk quota. The audit action before credential rotations and stale-access cleanup.

Statistics

1
  • Get Disk Usage Returns the account's disk-quota usage: bytes used, the total limit, and the remaining allowance. The sentinel action that turns storage limits into early warnings instead of outages.

Frequently Asked Questions

What can FlowRunner do with cPanel?

FlowRunner agents can run UAPI Call, WHM API Call, and List Email Accounts in cPanel, plus 6 more actions.

Does connecting cPanel to FlowRunner require OAuth?

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

Can cPanel trigger a FlowRunner workflow automatically?

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

Start building with cPanel

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