CONNECT APP
Build with FireCrawl
Web & App Development
- API key
MCP
Give your agent FireCrawl tools
Every FireCrawl action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's FireCrawl account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "firecrawl",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Crawl URL:
const result = await mcp.callTool({
name: "firecrawl-crawl-url",
arguments: {
url: "URL",
prompt: "Prompt",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "firecrawl",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Crawl URL:
result = await session.call_tool("firecrawl-crawl-url", {
"url": "URL",
"prompt": "Prompt",
})API PROXY
Call the FireCrawl API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the FireCrawl API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.firecrawl.dev/v0/crawl",
})
// Any allowed FireCrawl endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.firecrawl.dev/v0/crawl
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZmlyZWNyYXdsLmRldi92MC9jcmF3bA?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run FireCrawl actions from your backend
Connect a user's FireCrawl account once, then run Crawl URL on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "firecrawl-crawl-url",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
firecrawl: { authProvisionId: "apn_xxxxxxx" },
url: "URL",
prompt: "Prompt",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="firecrawl-crawl-url",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"firecrawl": {"authProvisionId": "apn_xxxxxxx"},
"url": "URL",
"prompt": "Prompt",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "firecrawl-crawl-url",
"configured_props": {
"firecrawl": { "authProvisionId": "apn_xxxxxxx" },
"url": "URL",
"prompt": "Prompt"
}
}'TOOLS
FireCrawl actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Crawl URL
actionCrawls a given URL and returns the contents of sub-pages. See the documentationWritev1.1.2 -
Extract Data
actionExtract structured data from one or multiple URLs. See the documentationWritev0.0.5 -
Get Crawl Data
actionObtains the status and data from a previous crawl operation. See the documentationRead-onlyv0.0.6 -
Get Extract Data
actionObtains the status and data from a previous extract operation. See the documentationRead-onlyv0.0.4 -
Map URL
actionMaps a given URL using Firecrawl's Map endpoint. Optionally, you can provide a search term to filter the mapping. See the documentationWritev0.0.3 -
Scrape Page
actionScrapes a URL and returns content from that page. See the documentationWritev1.0.4 -
Search
actionSearch the web and get full content from results. See the documentationRead-onlyv0.0.3
EVENTS
FireCrawl triggers
Event sources your backend can deploy for users and receive through a webhook.
No FireCrawl triggers are available yet.
MULTI-APP
Use FireCrawl with other popular apps
Most products don't stop at one integration. Pair FireCrawl with the other apps your users rely on, and ship use cases that span both.
- App slug
- firecrawl
- Authentication
- API key
- Categories
- Web & App Development
- Actions
- 7
- Triggers
- 0
- API proxy
- Available