Crawlbase
by @gora050
Crawlbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Crawlbase data.
clawhub install crawlbaseπ About This Skill
name: crawlbase description: | Crawlbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Crawlbase data. compatibility: Requires network access and a valid Membrane account (Free tier supported). license: MIT homepage: https://getmembrane.com repository: https://github.com/membranedev/application-skills metadata: author: membrane version: "1.0" categories: ""
Crawlbase
Crawlbase is a web crawling API that helps developers extract data from websites. It handles proxies, CAPTCHAs, and JavaScript rendering, so users can reliably scrape data at scale. It is used by data scientists, researchers, and businesses needing web data for analysis or other applications.
Official docs: https://crawlbase.com/docs/
Crawlbase Overview
When to use which actions: Use action names and parameters as needed.
Working with Crawlbase
This skill uses the Membrane CLI to interact with Crawlbase. Membrane handles authentication and credentials refresh automatically β so you can focus on the integration logic rather than auth plumbing.
Install the CLI
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli@latest
Authentication
membrane login --tenant --clientName=
This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.
Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:
membrane login complete
Add --json to any command for machine-readable JSON output.
Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness
Connecting to Crawlbase
Use membrane connection ensure to find or create a connection by app URL or domain:
membrane connection ensure "https://crawlbase.com/" --json
This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.
If the returned connection has state: "READY", skip to Step 2.
#### 1b. Wait for the connection to be ready
If the connection is in BUILDING state, poll until it's ready:
npx @membranehq/cli connection get --wait --json
The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.
The resulting state tells you what to do next:
READY β connection is fully set up. Skip to Step 2.CLIENT_ACTION_REQUIRED β the user or agent needs to do something. The clientAction object describes the required action:clientAction.type β the kind of action needed:
- "connect" β user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
- "provide-input" β more information is needed (e.g. which app to connect to).
- clientAction.description β human-readable explanation of what's needed.
- clientAction.uiUrl (optional) β URL to a pre-built UI where the user can complete the action. Show this to the user when present.
- clientAction.agentInstructions (optional) β instructions for the AI agent on how to proceed programmatically. After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get to check if the state moved to READY.
CONFIGURATION_ERROR or SETUP_FAILED β something went wrong. Check the error field for details.Searching for actions
Search using a natural language description of what you want to do:
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
You should always search for actions in the context of a specific connection.
Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).
Popular actions
| Name | Key | Description | | --- | --- | --- | | Get Storage Total Count | get-storage-total-count | Get the total count of items stored in Crawlbase Cloud Storage. | | Delete Stored Results in Bulk | delete-stored-results-bulk | Delete multiple stored crawl results from Crawlbase Cloud Storage in a single request. | | List Stored Request IDs | list-stored-rids | Get a list of Request IDs (RIDs) stored in Crawlbase Cloud Storage. | | Get Stored Results in Bulk | get-stored-results-bulk | Retrieve multiple stored crawl results from Crawlbase Cloud Storage in a single request (max 100 RIDs). | | Delete Stored Result | delete-stored-result | Delete a stored crawl result from Crawlbase Cloud Storage by Request ID (RID). | | Get Stored Result | get-stored-result | Retrieve a previously crawled page from Crawlbase Cloud Storage by Request ID (RID) or URL. | | Get Account Stats | get-account-stats | Get account usage statistics including successful/failed requests, credits remaining, and domain-level stats for the ... | | Crawl URL with POST | crawl-url-post | Crawl a web page using POST method, useful for submitting forms or API requests that require POST data. | | Crawl URL | crawl-url | Crawl a web page and retrieve its HTML content using Crawlbase's proxy network. |
Running actions
membrane action run --connectionId=CONNECTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
The result is in the output field of the response.
Proxy requests
When the available actions don't cover your use case, you can send requests directly to the Crawlbase API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers β including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|------|-------------|
| -X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| -H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
| -d, --data | Request body (string) |
| --json | Shorthand to send a JSON body and set Content-Type: application/json |
| --rawData | Send the body as-is without any processing |
| --query | Query-string parameter (repeatable), e.g. --query "limit=10" |
| --pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
Best practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.π Tips & Best Practices
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.