Contractorfy roofing operations
Operations
Preparing the job workflow.
Bringing up roofing CRM records, documents, tasks, and handoff controls.
Roofing workflow modules
Opening route data and controls.
Workspace
Records
Actions
Bring your own OpenClaw
If you already built something useful in OpenClaw, the right answer is not to rip it out. Keep your runtime. Keep your private skills. Let Contractorfy handle the jobs, documents, approvals, Android capture, and public marketplace story around that runtime.
HTML-style architecture visual
Your OpenClaw
Private runtime, local automations, personal skills, and the flow you already trust.
Contractorfy API layer
Workspace-scoped API keys, home wrappers, task extraction, and external-safe Codex proxy routes.
Contractorfy operator UI
Web dashboards, approvals, jobs, documents, and group context.
Android field capture
Calls, messages, photos, and operator activity that the rest of the workflow can reason over.
What you keep
Your local gateway, private skills, channel wiring, and operator habits do not need to be replaced. Contractorfy is meant to sit beside that runtime and make it commercially useful.
What Contractorfy adds
Jobs, documents, measurements, approvals, notifications, Android field capture, and operator UI live in Contractorfy so the rest of the team can actually work with the results of your automation.
What that unlocks
When the runtime and the marketplace are decoupled cleanly, a builder can keep their own OpenClaw private while still publishing a repeatable product to other companies on Contractorfy.
Exact BYO flow
The real BYO story is API-first. Your runtime calls Contractorfy. Contractorfy resolves the workspace-scoped credentials, surfaces the operational data, and gives the rest of your team a clean place to work.
Run your own OpenClaw wherever you already trust it: laptop, desktop, VM, or hosted server.
Bind the key to the workspace that owns the jobs, documents, and approvals your workflow needs to touch.
Use Contractorfy's skill-friendly wrappers for home data, task extraction, and Codex proxy traffic so your external runtime never needs the raw workspace OAuth token.
List the workflow in Robot Marketplace so other roofing companies understand what they can buy and what operational result they will get.
The first routes to wire up
If you only wire a few things first, wire these. They establish API keys, inspect the Codex connection, proxy model traffic safely, and expose the operational state your robot needs to be useful.
/api/keysCreate and manage the Contractorfy API keys that your external OpenClaw runtime will use.
/api/skills/contractorfy/codex/statusCheck whether a workspace-scoped Codex OAuth account exists before you send model traffic.
/api/skills/contractorfy/codex/modelsAsk Contractorfy which model ids are valid for the workspace before your external OpenClaw chooses one.
/api/skills/contractorfy/codex/responsesSend model requests through Contractorfy while Contractorfy keeps the workspace Codex OAuth credential private.
/api/skills/contractorfy/homeFetch the operator home payload so an external robot can reason over jobs, queues, and daily workload without scraping UI.
/api/skills/contractorfy/home/overviewRead the home overview card data for a workspace or group in a robot-friendly contract.
/api/skills/contractorfy/home/queuesRead the task and workflow queues that matter to operators right now.
/api/skills/contractorfy/home/job-build-calendarLoad build-calendar data from the same route family used by the web homepage.
/api/skills/contractorfy/task-extractTurn call notes, transcript text, or external automation output into Contractorfy tasks without dropping into the UI first.
Why this matters strategically
When a builder can keep their runtime private but still expose a clean Contractorfy listing, a single good workflow can become a sellable product. That is the difference between being a power user and being a marketplace seller.
What buyers need to understand
They care that the robot follows up on supplements, triages hail jobs, or generates documents correctly. The BYO runtime stays behind the curtain while Contractorfy explains the workflow in business terms.
Connect the dots
BYO OpenClaw is the builder architecture. Robot Marketplace is the buyer-facing storefront. They should reinforce each other everywhere in the public web experience.