Lovable: Auto-Detects Connectors from Pasted API Keys
LovableLovable now recognizes when a pasted API key in project chat belongs to a supported tool and automatically offers to set up a connector for it, instead of leaving the key as a plain project secret. The resulting connection lives at the workspace level, so it can be reused across projects, and users choose who else can access it. The key itself is still saved as a project secret either way, so nothing changes about the underlying credential's security.
Key Takeaways
- Lovable recognizes pasted API keys automatically, and dropping a key into project chat is enough to trigger a connector setup offer with no manual panel required.
- Connections are created at the workspace level, so once set up this way, a connector can be reused across every project in the workspace, not just the one where the key was pasted.
- Access is controllable per connection, with users choosing who else in the workspace can use a connector created from a pasted key.
- The key still lands as a project secret either way, so even if a user doesn't turn it into a connector, the pasted credential is preserved.
- It follows directly on custom REST API connectors, shipping one day after Lovable let admins define connectors for virtually any REST API, making that system easier to discover.
- The change targets discoverability, not new integration coverage, routing existing connector setup through a more natural, chat-first entry point rather than adding new third-party services.
Lovable Recognizes API Keys Pasted Into Chat
On September 1, 2026, Lovable shipped a small but practical workflow change: when a user pastes an API key into a project's chat, Lovable's agent now attempts to identify which tool the key belongs to and offers to set it up as a connector on the spot.
From Paste to Connector
Previously, connecting a third-party tool meant navigating to Lovable's dedicated connectors panel, finding the right integration, and entering credentials there. Now, if a builder is mid-conversation and pastes a key for a service Lovable already supports, Lovable recognizes the pattern and proposes wiring it up as a proper connector rather than leaving it as a one-off secret.
Workspace-Level Reuse
The resulting connection is created at the workspace level rather than scoped to a single project, meaning it can be reused across every project in that workspace once it exists. Builders also choose who else in the workspace can use the connection, keeping shared credentials under some access control instead of making them available to everyone by default. Regardless of whether the paste becomes a full connector, the key itself is still saved as a project secret, so nothing about the security of the underlying credential changes.
Why It Matters
This is a friction-reduction feature more than a new integration: the underlying connector system already existed, alongside Lovable's custom-connector support for arbitrary REST APIs shipped just one day earlier. What changes is discoverability. Builders who don't know a dedicated connectors panel exists, or who don't want to break away from chat mid-build, get automatically routed toward the more reusable, access-controlled workspace connector pattern instead of leaving keys scattered as loose project secrets.