Create leads, new/existing clients, and tasks in SingleOps (tree care and landscape business management software) via its Lead Entry API
domain: docs.singleops.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Contact support@singleops.com to provision a dedicated API user and obtain a user_email/user_token pair for the target account (API access is not available on all pricing tiers)
Call GET https://app.singleops.com/api/v1/operations and /api/v1/custom_inputs to resolve the operation (division) ID and any custom input field IDs needed for the lead
Call GET https://app.singleops.com/api/v1/clients/search_by_field with search_field=email or phone to check for an existing client before creating a duplicate
POST to https://app.singleops.com/api/v1/jobs with a JSON body containing job, portal_lead, and visit objects to create the lead (include client_id for an existing client, or full contact fields under portal_lead for a new one)
Optionally set job_task_create=true and include a task object in the same POST to create a follow-up task alongside the lead
Check the response's success/error/id fields to confirm the lead was created
Known gotchas
Each account (including sub-accounts in an account group) needs its own unique API user — a user from one account cannot call the API against a sibling account even with in-app access
Leads created through this API follow the Customer Portal workflow and require manual confirmation before the client/location is considered valid
Field length limits are strict and silently truncatable in some clients (e.g., job.name max 41 characters, notes fields max 4000 characters) — validate client-side before submitting
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?