Verify credentials work. If this fails, all other tools will too.

Hits /operations as a low-cost liveness probe (a single small GET that exercises the auth + network path).

List operations (divisions) configured in the account.

Operations are the divisions a green-industry business runs under — e.g. "Maintenance", "Install", "Irrigation", "Tree Care", "Snow". Each lead (Job) must be assigned to exactly one operation, so this list is the entry point for any lead-creation flow.

Returns the list of operation objects with id, name, and any division- specific metadata the account has configured.

List custom input fields configured for the account.

Custom inputs are per-account fields that augment the default lead/job/ client/item schema — e.g. "Lead Source", "Property Acreage", "Service Tier". Each entry has a key, label, type, and the entity it applies to. Cache this list; the lead-creation endpoint accepts custom field values keyed by the custom input's key.

Find clients by email address (prefix match, up to 50 per page).

Use this before creating a lead to check whether the prospect already exists in the SingleOps account. Returns 0-50 matching clients; paginate with the page parameter when the count approaches 50.

Common pattern: search the prospect's email; if found, reuse client_id when creating the lead instead of supplying a portal_lead block.

Find clients by phone number (prefix match, up to 50 per page).

Use this when a prospect's email is unknown (e.g. a phone call comes in) to find their existing record before creating a new lead. Sometimes clients have multiple phone numbers or extensions, so the prefix match lets the search catch those variations.

Create a lead (Job) for an existing client already in SingleOps.

Use after search_clients_by_email / search_clients_by_phone to attach a new lead to an existing client record. The lead moves through the SingleOps Job workflow (Lead -> Proposal -> Schedule -> Complete -> Invoice).

client_id is the SingleOps client.id (NOT email, NOT name). Look it up with one of the search tools first.

operation_id is the SingleOps operation.id for the division the work belongs to (look it up with list_operations).

visit_stage_id defaults to 8 (the standard "Lead" stage) but can be set to whatever stage IDs your account has configured.

Create a lead (Job) for a brand-new client, in a single call.

Use this when the prospect is NOT yet in SingleOps. The new client profile is created under the "portal_lead" object inside the same request — the lead is attached to that new client automatically.

At minimum pass first_name + last_name. Providing email or phone is strongly recommended so SingleOps can later deduplicate if the same person contacts you again.