> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Firecrawl as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/firecrawl

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

[Firecrawl](https://www.firecrawl.dev) is a web scraping and crawling API. This connector syncs your Firecrawl account's operational data – job activity, credit and token usage, active crawls, and change-detection monitors – into the PostHog Data warehouse, so you can track your scraping usage and spend alongside the rest of your data.

## Prerequisites

-   A Firecrawl account.
-   A Firecrawl API key, which you can create in your [Firecrawl dashboard](https://www.firecrawl.dev/app/api-keys). A single key grants access to every table this connector syncs.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Firecrawl, you'll need:

-   **API key** – create one under [API Keys](https://www.firecrawl.dev/app/api-keys) in your Firecrawl dashboard. It starts with `fc-`.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Firecrawl tables are full refresh only. Firecrawl's account endpoints don't expose a server-side "updated since" filter, so each sync replaces the table with the current data from the API.

> **Note:** The `team_activity` table is a rolling log that Firecrawl only retains for the **last 24 hours**. Older activity can't be backfilled, so schedule frequent syncs if you want to accumulate a longer history of jobs in the warehouse.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `team_activity` | Job activity log. Firecrawl only retains the last 24 hours, so sync frequently to accumulate history - older activity cannot be backfilled. | Full refresh | — | id |
| `credit_usage_historical` | Credits used per billing period, month by month. | Full refresh | — | startDate |
| `token_usage_historical` | Tokens used per billing period, month by month. | Full refresh | — | startDate |
| `active_crawls` | Crawls that are currently in progress for your team. | Full refresh | — | id |
| `monitors` | Change-detection monitors that periodically re-scrape targets and report what changed. | Full refresh | — | id |
| `monitor_checks` | Change-detection runs, one row per check across every monitor. Off by default: it fans out one request per monitor. | Full refresh | — | id |

The `monitor_checks` table is disabled by default because it fans out one request per monitor. Enable it in the table picker if you use Firecrawl monitors and want their individual check runs.

## Troubleshooting

-   If the connection fails to validate, confirm your API key is active in your [Firecrawl dashboard](https://www.firecrawl.dev/app/api-keys) and that you pasted the full `fc-...` value.

-   If `team_activity` is empty, the endpoint only returns the last 24 hours of jobs. If your account hasn't run any jobs in that window, the table will be empty until it does.

-   If you hit rate limits, the connector automatically backs off and retries. Firecrawl enforces plan-based rate and concurrency limits.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.