Overview

The BizDev stays in Agent (codex/Claude), or mentions @z-claw in Slack. When a question needs the Zooly code, the database, a script, or a dashboard, the machine does that work and the answer comes back in the same chat or the same Slack thread.

He does not install software, open a shell, or receive a database password. Someone on the team gives the agent the setup page and the connector token once. After that he just talks.

The machine is at z-claw.zooly.ai. The site is HTTPS, and the certificate renews on its own. The home page says the host is up and links to agent setup. File drop and report links open on that same host.

Before it describes a job, the agent reads the public docs at docs.zooly.ai so it understands the product. The machine still does the lookup.

The site and the machine come back on their own after a restart.

What he can ask for

• A question about the product data
• A script that creates or updates rows
• A short report or a dashboard, which comes back as a link in the chat
• An agency from a website or a spreadsheet, with a claim link he can send them
• In Slack, a debug of a problem. The reply is everyday words. The link is the technical page for the developers
• A search for an existing issue, or a new issue in the current release
• What AI usage cost between two dates, either for all of Zooly or for this machine alone, from the billed amount on each request

If the request is unclear, or a detail is missing, it asks and waits. It does not fill that in on its own.

The machine answers with Grok 4.7, through the same model gateway the rest of Zooly uses.

Where to go next

• Connect an agent — the one-time connection
• Jobs — how a request runs and how a follow-up stays in the same conversation
• Files and reports — sending a file in, and opening a dashboard
• Slack — mention @z-claw in a channel it has joined