Skip to main content
One dated entry per release. Each says what changed, how widely it is switched on, and which page to read for the rest of the story.
New sidebar entries, the surfaces switched on per workspace, and what moved to Legacy.

New in the sidebar

AI Agents and Web Forms each carry a small New chip. They are the only two entries with one.Both also sit behind their own switch. AI Agents is switched on across this release; Web Forms is not switched on everywhere, so that entry (and its chip) is missing from some sidebars. AI Agents overview · Connect a web form

Switched on per workspace

These entries stay in the menu tree for everyone but only appear where their switch is on. A switch is turned on for everyone at once or for a single workspace at a time.The switch is not the only thing that can hide one of these. Every entry above also needs its own read permission on your role, so two people in the same workspace can see different sidebars.

Moved to Legacy

AI Campaigns (Legacy), AI Engine and Google My Business moved into a Legacy group, and Manual Search into a lead-generation group of its own. Both groups are hidden by default, because lead generation now lives inside AI Agents and Prospects.Nothing was deleted. Turning a hidden group back on for one workspace is a single toggle (none of the four pages is hidden on its own account), and each can still be switched on or off by itself afterwards.

New on the public API

/api/v1 is a versioned public contract, separate from the internal routes the app uses to talk to itself. POST /leads and POST /leads/batch create leads, GET /leads/{id} reads one back, GET /tags lists your tags, and GET /me tells you which workspace a key belongs to.Every call is authenticated by an API key rather than a session, and the workspace comes from the key. No endpoint takes a workspace of its own. Each route except GET /me also requires a scope on the key: leads:write to create, leads:read to read a lead back, tags:read to list tags. API overview · Create a lead

Early-access and legacy features

What is available only in some environments, what replaced what, and how to tell which state a feature is in.

Feature availability matrix

Every surface in the product, how you reach it, the permission it needs, the roles that hold it and what hides it.