Skip to main content

Platform guide

Everything in camolabs happens inside a site workspace, one per public domain you connect. This is how you take a site from connected to live for agents, and how you show your team it's working.

Pages​

Pages is where your site becomes agent-ready.

Point camolabs at your domain and run a scan. It crawls your public pages, reads each one, and builds an agent-ready version backed by the real content. A page that fails, say a timeout or a blocked crawler, is listed with the reason and can be retried without restarting the scan.

Every page stays a draft until you publish it. Open one to see the agent-ready version beside its source, the facts and links it kept, the forms and CTAs it found, and any Actions attached to it. Nothing reaches an agent before you publish.

Rescan whenever your site changes. Pages that changed come back as fresh drafts to review; published pages keep serving until you replace them.

Actions​

A scan makes your pages readable. Actions let agents act on them.

An Action is one of your CTAs, like request a demo, contact sales, get a quote, or join a waitlist, that you allow an agent to complete for a buyer. You create Actions yourself and attach each one to the pages where it belongs. A scan never invents them.

Two kinds:

  • Email relay delivers the agent's request as a message to an address you verify. camolabs records that it happened, never the contents.
  • Webhook posts the request to your endpoint as structured JSON, with any fixed fields and signing secret you set.

An Action goes live only once it's configured, active, and attached to a published page. Email relay also needs its destination address verified. Until then agents can't see it.

CTAs camolabs can't complete for an agent, such as anything behind a login or a third-party booking widget, stay on the page as ordinary links.

Tasks​

Tasks answer the question your team will actually ask: can an agent get through this?

Pick a goal (find pricing, request a demo, reach sales), an agent, and a target: your live site, an agent-ready page, the installed route, or a competitor. camolabs runs the journey and records what happened, including whether it finished, how many steps it took, the path it found, and where it stalled. Run the same goal against your original site and the agent-ready version to see the gap close.

Task runs are marked as test traffic and stay out of your live numbers by default.