Persona Console

Overview

Every persona product (salescron, gtmcron, leadercron, secronjob, bdrcron, cscron, partnercron, crocronjob) has a console at /<persona>/console. It is the same control-plane shell, branded to each persona. The console never runs agents itself — it drives the hosted runtime that runs headless on our servers on a schedule, so nothing depends on you keeping an app open.

Scoped to you. Your key, budget, schedule, and drafts are private to your account.

The two lanes

• Lane A — hosted (on by default). Deterministic detections (free, always available) plus budget-capped AI drafting, run on our server key. Output lands in your Draft queue — in-app, nothing sent anywhere.
• Lane B — your own n8n (optional). For workflows that must reach into your real mailbox or CRM, you run a small n8n on your own machine holding your own credentials. Those runs place real Gmail/Outlook drafts and write CRM records — on your infrastructure, never ours. Setup lives in your product docs. Nothing is ever auto-sent.

The four tabs

• Schedule. A master runtime on/off switch, plus every skill with its cadence and tier. Toggle a skill on or off, or run one right now. Deterministic skills are free; AI skills run under your budget cap.
• Draft queue. The drafts your hosted runs produced — view or dismiss each. With managed connectors on, → Gmail draft lands a draft in your real mailbox and → SF task logs a Salesforce task to review. Nothing is ever auto-sent. (Lane B drafts appear in your real mailbox too.)
• Runs. What ran, when, on which tier, and the outcome — read from the run ledger.
• Settings. Your budget/usage meter, your identity (fills the {{TOKEN}} values in the agents), bring-your-own-key, managed connectors, and the Deliver reports to Google Drive toggle.

Bring your own key (BYOK)

By default the runtime uses our key with a monthly budget cap priced into your subscription — so it works with no Claude plan of your own. In Settings you can instead supply your own Anthropic, OpenRouter, or Bedrock key; runs then meter to you and don't draw our budget. Keys are write-only: once saved, the console only ever shows whether a key is set, never the key itself.

Setting up Lane B (your own n8n)

1. Run an n8n on a machine you control (a corporate VM is ideal).
2. Import the workflow templates from n8n-templates/ — the shared console-api.json plus your persona's job(s), e.g. salescron/morning-draft-gmail.json.
3. Connect your Google (or Microsoft) account in n8n and re-attach that credential to the mailbox node — this is how drafts reach your real Drafts folder. Set your BYOK LLM key on the draft node.
4. Run node scripts/provision-n8n-kernel.mjs --url <your-n8n> --product <persona> to mint a console token and fill the templates.
5. In this console → Settings → Lane B, paste your n8n base URL + the token, then Connect. The console talks to your n8n browser-direct, so a firewalled corporate machine still works.

Your OAuth credentials and LLM key never leave your machine. The job workflows only ever create drafts — nothing is auto-sent.

Connect your CRM (managed) — no plugin install

In Settings you can turn on managed connectors. Link Salesforce, HubSpot, Gmail, or Google Calendar right in the browser; we custody your OAuth token, poll it on a schedule, and fill your accounts, opps, and contacts server-side — with no Claude Desktop or Cowork and no plugin to install. The panel shows each provider's connection state and last sync, and a Sync now button pulls your book immediately.

Opt-in and reversible. Token custody is a choice: a security-strict team can leave it off and use the Cowork path or their own n8n (Lane B) instead. Same as the Settings → Connect page, which carries the same panel.

Deliver reports to your Google Drive

In Settings, the Deliver reports to Google Drive toggle sends each hosted run's report into your Google Drive "Accounts" folder as a native Google Doc plus a raw .md copy, so you read the report where you already work. A run about a specific account lands in a per-account subfolder (Accounts/<account>); a general run lands in the Accounts root. The same deliveries show on your rollup under "Delivered to your Drive".

Off by default. The toggle needs managed connectors on and Google connected (Settings), because delivery uses your Google Drive access. Writing a file into your own Drive folder is delivery, not an outbound send — nothing leaves your account.

What runs it (no single-tool dependency)

The hosted runtime is server-side cron plus a bounded agent loop — it never draws a Claude Desktop or Cowork seat. A subscription is a chat entitlement, not API quota; scheduled work runs on a metered API key (ours by default, yours with BYOK). If you also use the Cowork plugin, both read and write the same account data — the console is simply the surface that lets you run and watch the same work without Cowork.