Claude is the best fit for Ken's agent templates today. A Cowork scheduled task runs in the cloud at a fixed time, even with your computer off, and Claude's custom connector can send a Ken API key in a request header, so a run never stops for a sign-in. For how the templates work and stay safe, see Run Ken's agent templates in your own AI tool.

Before you start

  • A paid Claude plan. Scheduled tasks run on Pro, Max, Team and Enterprise.
  • Agent templates on for your workspace. If Claude says Ken's agent tools are missing, they aren't on for your workspace yet.
  • An Admin or Editor role in the Ken workspace. The agent edits campaigns, and you approve its proposals.
  • A Ken API key made for this task. See Create a key for a scheduled agent.

What to know first

  • Claude acts as you, with your role in Ken. It can do what you can do in Ken. The template tells it to change campaigns only through Ken's agent_team tools, and Ken decides what to apply and what to turn into a proposal.
  • Use the API key in a request header, not a sign-in. A sign-in can expire and stop a scheduled task without warning. A key in the connector's header doesn't.
  • Never paste the key into a chat. It goes only in the connector's Request headers.
  • Switch off Ken's other write tools on the connector, so the task can only read and use agent_team_write (step 7 below).
  • Credits. Claude's thinking runs on your Claude plan and costs no Ken credits. Ken actions cost what they cost in the app: a lead top-up pays for the emails Ken finds and the AI work that follows, the same as when you add the leads yourself. See How credits work.

Add Ken as a custom connector

Add a second Ken connector for scheduled tasks, even if you already connected Ken with a sign-in.

  1. In Claude, open Customize, then Connectors.
  2. Click + Add, then Add custom connector.
  3. Name it Ken agent, and paste https://mcp.ken.so/mcp as the server URL. If you belong to several Ken workspaces, add the workspace, such as https://mcp.ken.so/mcp?workspace=42.
  4. Under Authentication, choose No sign in.
  5. Under Request headers, add Authorization with the value Bearer followed by your Ken API key.
  6. Save the connector.
  7. Open the connector's tools and switch off every Ken tool whose name ends in _write, except agent_team_write. Leave load_skill and the read tools on. The template never calls the others.

For several workspaces, add one connector per workspace, each with its workspace in the URL and named after it, such as Ken agent - Acme.

On Team and Enterprise, an owner adds custom connectors in Organization settings, then Connectors. If the owner puts a key in the header, everyone who uses that connector acts as the key's owner, so keep the key on a connector only you use.

Test it once in a chat

  1. Start a new Cowork chat. Click +, then Connectors, and turn on Ken agent. Leave any other Ken connector off.
  2. Set the permission setting in the message box to Manual, so Claude shows each Ken call before it makes it.
  3. Paste the starter prompt from Agent templates reference.
  4. Check that Claude loads the skill, reads what changed in Ken, and calls only load_skill, Ken's read tools (names ending in _read) and agent_team_write. If it asks to call anything else that changes a campaign, decline.

Schedule it

  1. Click Scheduled, then New task, then Create with Claude.
  2. Paste the starter prompt and ask for "every Monday at 07:00" in your time zone. Claude proposes a name, a schedule and instructions.
  3. Check the schedule and the time zone, then turn on Ken agent for the task.
  4. Let the task run Ken's tools without asking. A run that waits for a click in Claude stalls, and Ken already decides what waits for a person.
  5. Confirm, then run the task once by hand.

Claude Duet

Claude Duet is Anthropic's proactive assistant, a research preview since Oct 21, 2026, for Pro and Max in the US, by invite. It can't run a template on a fixed schedule yet:

  • No fixed time. Duet sends a morning brief and checks in every few hours. You can't set "Monday at 07:00".
  • Custom connectors aren't documented. Your Claude connectors carry over to Duet, but Anthropic doesn't say custom ones do.
  • It asks before it sends, pays, signs or deletes. Ken never needs Duet to approve anything: changes outside Autopilot wait in Ken.

If you have an invite:

  1. Add the Ken agent connector in Claude, as above.
  2. In Duet, ask: "Load Ken's skill keep-campaigns-running and tell me its first step." If it can't, use a Cowork scheduled task instead.
  3. Paste the starter prompt, and treat Duet as a regular check-in, not a Monday run.

Check the first run

  1. Open Scheduled in Claude and read the run. It lists what Ken applied, with each undo deadline, and what it proposed.
  2. Open Today in Ken and approve or skip each proposal.
  3. Ask Claude: "What changed in Ken this week?" It reads Ken's change log, where each change names who made it.

To undo a change, ask Claude to undo it before its deadline.

If Claude says something changed and Ken shows nothing, the call never reached Ken.

Good to know

  • Use Cowork scheduled tasks, not Claude Code routines. Custom connectors couldn't be attached to Claude Code routines when we checked.
  • A new key needs the header updated. If you replace the key, update Request headers the same day and run the task once by hand. An expired or revoked key stops the task.

Next: Agent templates reference, Use Ken from Claude or ChatGPT or What Ken does on its own.