Actions31
- Account Actions
- Agent Actions
- Browser Actions
- Crawling Actions
- Extract (Legacy) Actions
- Interact Actions
- Map & Search Actions
- Scraping Actions
Browser → Browser context
AI-generatedOverview
The Firecrawl node with the Browser resource and Browser context operation provides an interface to interact with a cloud-based browser sandbox environment. It allows users to create isolated browser sessions, execute code within those sessions using multiple languages (Node.js, Python, Bash), list active sessions, and delete sessions to manage resources efficiently. This node is beneficial for automating web interactions, scraping data, testing web applications, and performing multi-step browser workflows without local setup.
Use Case Examples
- Create a new browser session to automate login and data extraction from a website.
- Execute JavaScript code in an existing browser session to navigate pages and interact with elements.
- List all active browser sessions to monitor usage and manage resources.
- Delete a browser session to free up resources and save credits.
Properties
| Name | Meaning |
|---|---|
| Context | Provides detailed instructions and context about the Firecrawl Browser Sandbox environment, including available tools, typical workflows, and key guidelines for usage. This property must be set before using other browser operations and can be customized to tailor the instructions for specific use cases. |
| Use Custom Body | Determines whether to use a custom request body for the operation. Defaults to false. |
| Request Options | Configurable options for the HTTP request such as batching parameters, SSL certificate validation, proxy settings, and request timeout. These options help control how requests to the Firecrawl API are made and managed. |
Output
JSON
sessionId- The unique identifier for the created or managed browser session.status- The current status of the browser session (e.g., active, destroyed).cdpWebSocketUrl- The Chrome DevTools Protocol WebSocket URL for interacting with the browser session.liveViewUrls- URLs for live viewing the browser session's activity.timestamps- Timestamps related to the session lifecycle, such as creation and destruction times.result- Output data from executed browser code, such as console logs or print statements.
Dependencies
- Requires an API key credential for Firecrawl API access.
Troubleshooting
- Ensure a browser session is created before attempting to execute code; otherwise, the node will fail due to missing session context.
- If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option to bypass validation (use with caution).
- Verify proxy settings if requests fail to connect through a proxy server.
- Monitor request timeout settings to avoid premature request abortion, especially for long-running browser operations.
- Always delete browser sessions when finished to avoid unnecessary credit usage and resource leaks.
Links
- Firecrawl Browser Sandbox Documentation - Official documentation for using the Firecrawl Browser Sandbox, including session management and code execution.