⚡ AI Analyst
Lovable connectors come in three types, and the type decides who sees your data. How a finance team should choose, verified September 2026.
Money Flock
Recommended Contents
Comments
MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.
On 23 September 2026, Lovable shipped five connectors in a single changelog entry: AWS API, Azure Cloud API, Azure Graph and Entra API, Google Cloud API, and Looker. A week before that it added Power BI and WhatsApp Business. The catalog is now large enough that, for most finance projects, whether your tool is supported is no longer the interesting question.
The interesting question is which of the three connection types you pick, because that one choice decides who can see the data moving through it. It helps to think of a connector less as a door and more as a keycard. Lovable issues three kinds: a building master key that every visitor to your published app shares, a personal key that only you carry, and a visitor badge that reception hands to each person who walks in. Give out the wrong one and a budgeting app quietly shows every user the same account balance.
This guide covers what Lovable connectors are, why the type matters more than the tool, a five step way to choose one for a finance stack, what changed in September 2026, and the mistakes that cost teams money. It is a selection guide, not a wiring tutorial. For the mechanics of pulling a live market feed into a dashboard, see the trading dashboard walkthrough.
Lovable connectors link the platform to outside tools, services, and APIs. You connect a tool once and Lovable handles the authentication, the stored credentials, and the requests from then on. Slack, Notion, HubSpot, Google Workspace, Stripe, Supabase, and several hundred others sit in one catalog inside the dashboard.
According to Lovable's own documentation, every connector lives in that same catalog. What differs is the connection type you choose when you click Add connection, and not every connector supports every type. The three are app plus chat connectors, chat connectors, and app user connectors.
Three further options cover whatever the catalog misses. A workspace admin can create a custom connector for any REST API, which has been open to admins and owners on every plan since 31 August 2026. You can connect your own MCP server for chat context. Or you can simply ask Lovable to write an integration against any API directly.
Three connection types, one catalog. The type is the security decision, and it is the part most third party guides skip entirely.
Screenshot of Lovable's own connection type table, captured 27 September 2026. Source: docs.lovable.dev/integrations/introduction
For a finance app the difference between the three types is not a technical detail. It is the difference between a product and an incident.
Picture a portfolio tracker. If you connect a brokerage or bank data account as an app plus chat connector, every visitor to the published app is looking through the same account. That is correct for a public markets feed and completely wrong for personal holdings. The same app built with an app user connector asks each visitor to sign in with their own account, and each one sees only their own rows.
There is a second rule worth reading twice. Lovable's admin documentation states that connection and client level access is not enforced after publishing: once a project is published, the live app is reachable regardless of who was granted access to the connection inside the workspace. Access settings govern who can build with a connection, not who can use the app you built with it.
A third rule protects individuals rather than apps. In Chats, Lovable will not use another member's connection to a personal account such as Gmail, Drive, Calendar, Outlook, GitHub, or Linear, even if that member shared it. Those show up labelled as a personal connection, restricted in chats. Shared connections to workspace tools like Slack, Notion, HubSpot, or Salesforce behave normally.
If you want the wider picture on where financial data sits when you build with Lovable, the data handling article covers storage, retention and the backend side.
Before you open the catalog, answer one question: does this data belong to the business or to the person using the app. Business data, such as your own Stripe revenue, your team's Looker measures, or a shared Slack channel, is an app plus chat connector. Personal data belonging to the end user, such as their brokerage account or their mailbox, is an app user connector. Your own working context while you build is a chat connector. Nothing else in the selection process matters as much as getting this right.
The catalog moved quickly through September 2026, and a connector you looked for a month ago may exist now. As of 27 September 2026 the recent additions include Looker and the three major cloud APIs on 23 September, Parallel on 22 September, the Lovable API connector on 17 September, Power BI and WhatsApp Business on 15 September, Cloudflare API on 10 September, Gong on 7 September, and GitLab API plus Firebase Cloud Messaging on 28 August. Search also tolerates typos now and offers the closest match.
The 23 September 2026 changelog entry, captured 27 September 2026. Source: docs.lovable.dev/changelog
Several research connectors now offer a Managed by Lovable option, which means you connect without holding an account or an API key with that vendor. Parallel arrived that way on 22 September 2026 for live web search and deep research. Firecrawl gained the option on 18 September. Perplexity gained it on 17 September, though the managed route covers the Search API only, and cited answers, deep research, and academic or securities filing search still need your own Perplexity key.
Managed connections are billed to the workspace that owns the project and appear under Run credits, so the convenience is real but it is not free. Note one more difference: a managed connection is shared with the entire workspace by default, where every other connection starts private.
This is where plan choice stops being about credits. On Free and Pro, any workspace member with the editor role or higher can create connections and clients. There is no control to change that. On Business and Enterprise, an admin sets each connector to No one, Admins, or Editors and admins, and the setting doubles as an availability switch. The Business default is Admins.
For a team handling client money, that is the difference between a documented approval step and a junior builder connecting a production data source on a Friday afternoon. The connector admin settings area is available on Business and Enterprise plans only.
Connector availability defaults by plan, captured 27 September 2026. Source: docs.lovable.dev/integrations/admin-controls
Verified on Lovable's pricing page on 27 September 2026: Pro is $50 a month at the 200 monthly credit tier and Business is $50 a month at the 100 credit tier. You pay the same headline price for fewer credits, and governance is what you get in exchange.
The full plan comparison, including what the credit tiers actually buy, sits in the pricing breakdown.
Whoever creates a connection chooses who can use it, on any plan, and that choice is separate from the admin controls above. The options are Private, which is the default and is marked with a Private label, Share with others by email, or Invite entire workspace. A connection can be made private again at any time. Managed by Lovable connections are the exception and start shared with everyone.
One consequence catches teams out: a project using a connection can only be shared with members who have access to that connection, and external collaborators lose access to the project entirely. Plan the sharing list before you link a connection to a client project rather than after.
Three patterns cover most of what a finance team actually builds.
A personal budgeting or net worth app. Bank data belongs to the end user, so this is an app user pattern, with each person connecting their own account. The bank data side of this is covered in detail in the Plaid guide.
An internal KPI or scorecard page. If your analysts already maintain measures in Looker or semantic models in Power BI, connect those rather than re-deriving the numbers. Looker runs queries against the measures and dimensions defined in LookML, so the figures in the app match the figures in the reports the team already signs off. Power BI queries semantic models with DAX and also supports per user access, where each viewer signs in with their own Microsoft work account and sees only the rows Power BI permits.
A research or due diligence assistant. Parallel and Perplexity cover live search and cited research, Firecrawl handles reading public pages and filings as clean text, and all three can run managed so there is no second vendor contract to sign. Budget for Run credits.
If several people will work on these projects together, roles and draft review are worth setting up first. The team workspace article covers that side.
This is the expensive one. An app plus chat connector runs on a single account for every visitor. In a finance app that usually means one person's data is visible to everyone, or everyone's writes land in one place. If the sentence "each user should see only their own" appears anywhere in your spec, you need an app user connector.
They do not. Connection level access controls who can build with the connection. Once you publish, the live app is reachable regardless. Authentication inside the app itself is a separate job that you still have to do.
On Free and Pro, every editor can create a connection to anything in the catalog, and there is no switch to stop them. If that is not acceptable for the data you handle, the control you want is on Business.
Since 31 August 2026, workspace admins and owners on any plan can define a custom connector for any REST API, which then appears in the catalog for the whole workspace to reuse. That is usually better than a one off integration buried in a single project, because the next project inherits it. Check the catalog, then check custom connectors, and only then write bespoke code.
A Managed by Lovable connection is convenient precisely because Lovable is paying the vendor and charging you. Those charges land on the workspace that owns the project, under Run credits. A research agent left running against live search is a recurring cost, not a one time setup.
They are prebuilt links between Lovable and outside tools. You add a connection once, Lovable stores the credential and handles requests, and your projects or your chats then use that tool without you writing authentication code.
Decide by data ownership, not by tool. Business data that every visitor may see is an app plus chat connector. Data belonging to the individual user is an app user connector. Context you want only while building is a chat connector.
Yes. App plus chat connectors and chat connectors are available by default on Free, Pro, and Business. What Free and Pro lack is the admin settings area that lets you restrict who may create connections, which is a Business and Enterprise feature.
Yes, in three ways. An admin can create a custom connector for any REST API so the whole workspace can reuse it, you can connect a custom MCP server for chat context, or you can have Lovable write a direct integration into the app.
The connection itself does not. Work does. Managed by Lovable connections such as Parallel, Firecrawl, and Perplexity search bill each request to the workspace under Run credits, and any build message that uses a connector costs build credits like any other message.
Yes to both, and both landed recently. Power BI arrived on 15 September 2026 and queries semantic models with DAX. Looker arrived on 23 September 2026 and queries the measures and dimensions your analytics team defines in LookML.
If you are building for yourself and nobody else touches the workspace, the connector controls on a personal plan are enough, and you can start building with Lovable and add connections as you need them.
If a team is involved and the data is somebody else's money, the Business plan is the one that carries the connector governance described above: per connector control over who may create a connection, with Admins as the default. That is the honest reason to choose it, and it has nothing to do with credits.
If you would rather have the selection and setup done for you, TJ Alam's certified Lovable Expert profile is in the partner directory.
The keycard holds up all the way through. Lovable makes it easy to open the building. Deciding which key each person carries is still your job, and on a finance product it is the one decision that is expensive to get wrong.
TJ Alam is a certified Lovable Expert (Website Builder track), founder of Digi Flock Enterprises, and built tjalam.com and cyberdance.in on Lovable.
MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.