Managing sites and keys
Connect, scope, name and prune — before you have thirty of each.
Sites
A site is a WordPress installation plus a stored credential, an approval policy and its brand voice notes. Add one from Sites in the dashboard, or have an agent call create_connect_link and hand you the link. Each site gets a short handle — that is what agents pass as the site parameter, and it is what list_sites returns.
- Rename or re-probe a site at any time; the handle stays stable so agent instructions do not break.
- Disconnecting removes the stored credential and frees the plan slot. Posts already on WordPress are untouched.
- After disconnecting, also revoke the Application Password in WordPress. Removing our copy does not invalidate it on your site.
Agent keys
Keys are for custom or self-hosted agents that cannot do OAuth. MCP clients such as Claude sign in with OAuth and need no key at all.
- A key is shown once, at creation. Pressbotics stores only a hash, so it cannot be shown again — losing it means creating a new one.
- Scope each key to the sites it needs. A key scoped to one site cannot touch the others.
- Give each key a monthly cap when it drives an automation.
- Name keys after where they run, not after what they do. "n8n-prod" is findable in six months; "blog key" is not.
Housekeeping
- 1Revoke keys you cannot account for. Revocation is immediate.
- 2Disconnect sites you no longer publish to rather than leaving credentials sitting there.
- 3Check Activity for keys still publishing that you thought were retired.