Skip to main content
Firecrawl is a web scraping and crawling platform. The Firecrawl connector lets your Lovable app scrape URLs into clean markdown or structured JSON, crawl whole sites, search the web, and map site structure. It’s designed for apps that need to fetch, update, and structure information from websites rather than rely on one-time imports or static datasets. Firecrawl is available as an app + chat connector: one shared connection that works in the project chat while you build and in your published apps. With Firecrawl, your app can:
  • Turn any web page into clean text or structured data, including pages that load their content with JavaScript
  • Crawl a whole website, following its pages and sitemap
  • Search the web and get the content of the pages it finds
  • List every URL on a site before you crawl it
  • Re-check pages on a schedule so your data stays current
Firecrawl is a good fit for price monitors, job boards, lead enrichment tools, and content aggregators.

​
Common use cases and example apps

These examples show what you can build with Firecrawl, each with a prompt to start from.

​
How to connect Firecrawl

Who can create Firecrawl connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors. When adding a connection, you choose between two options:
  • Managed by Lovable: Lovable provides and manages the credentials for you. No registration needed. Usage spends workspace credits.
  • Use your own credentials: connect with your own Firecrawl API key and manage billing in Firecrawl.
When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in the project chat to link their project to it. Follow the setup steps below for the option you want.
Choose this option for the fastest setup. You don’t need a Firecrawl account or API key.
You can create one managed Firecrawl connection per workspace. If one exists, the Managed by Lovable option is unavailable in the form until you delete it.

​
Usage and billing

Requests through the managed connection use Firecrawl credits. Lovable charges them to the workspace that owns the project at the rate in Pricing below. See Credits and usage for how usage-based credits work.If the workspace runs out of credits, requests fail until you top up. The connection’s page shows its credit usage, which may not appear immediately.Lovable does not charge credits for managed connections created before usage billing started for your workspace.

​
Set up the managed connection

To create the managed connection:
1

Open Firecrawl in Connectors

Open Connectors and select Firecrawl. For the other places to open the catalog from, see Where to find connectors.
2

Add a connection

Click Add connection and select App + chat connector. The form is split into collapsible sections, Details, Configure connection, and Sharing.
3

Name the connection

Under Details, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection.
4

Choose Managed by Lovable

Under Configure connection, select Managed by Lovable. No credential fields appear for this option.
5

Choose who can use this connection

Managed connections are shared with the entire workspace by default. To limit who can use the connection, click Restrict to specific people under Sharing.See Who can use connections and clients for more information.
6

Connect

Above the button, a usage note explains that connecting lets Lovable send data to Firecrawl and deduct Lovable credits, with links to Pricing on this page and to Lovable’s provider rules for Firecrawl. Click Connect.
When connected, anyone building in a project can ask Lovable in the project chat to link their project to Firecrawl (based on configured connection-level access). Your Lovable apps can then scrape, crawl, and keep website data up to date with Firecrawl.

​
Pricing

With Managed by Lovable, usage costs 4 Lovable credits per 1,000 Firecrawl credits, or 2 Lovable credits on Business plans. Firecrawl credits measure API usage, and the number consumed depends on the feature you use. See Firecrawl billing documentation for credit usage by feature. Lovable charges the workspace that owns the project, and the usage appears under Run credits. With Use your own credentials, Firecrawl bills usage directly to your Firecrawl account, and Lovable credits do not apply.

​
Limitations

The Firecrawl connector cannot:
  • Use Firecrawl Monitor on a managed connection billed through Lovable credits. To use Monitor, connect with Use your own credentials and your own Firecrawl API key.
  • Rotate API keys automatically for connections that use your own credentials. To rotate, create a new key in Firecrawl and update the Lovable connection.
  • Support per-end-user Firecrawl login. Each connection represents a single Firecrawl account shared across all projects linked to it.

​
Troubleshooting

If requests through the connection fail, the sections below cover the most common errors and how to resolve them.
The workspace that owns the project has run out of credits. Top up credits for that workspace, and requests resume. See Credits and usage.
The Firecrawl account that owns the API key has run out of Firecrawl credits. Buy more credits or upgrade the plan in your Firecrawl account, and requests resume.

​
Manage your Firecrawl connection

Connections are managed from Connectors: select Firecrawl, then open the connection.
  • Unlink projects to remove Firecrawl access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
  • Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Firecrawl stop working until a new connection is added. See Delete a connection for the steps and who can delete.