Integration
Connect Swiftype to Browserless
When something happens in Swiftype, your agent does the next thing in Browserless. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Swiftype and Browserless to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Swiftype and Browserless
Triggers and actions 1 trigger ยท 26 actions
Trigger
New DocumentTriggers when a new Document is created.
Action
Add domainAdd a crawler domain to an Engine. POST /api/v1/engines/{engine_id}/domains.json with url.
Action
Add engineCreate a new Engine (index). POST /api/v1/engines.json with name.
Action
Create DocumentCreates a new Document.
Action
Delete documentDelete a document by document_id from a document type. DELETE /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}.json
Action
Delete domainRemove a crawler domain from an Engine. DELETE /api/v1/engines/{engine_id}/domains/{domain_id}.json
Action
Delete engineDelete an Engine by id. DELETE /api/v1/engines/{engine_id}.json
Action
Get documentRetrieve a single document by external_id from a document type. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{external_id}.json
Action
Get engineRetrieve a single Engine by id or name. GET /api/v1/engines/{engine_id}.json
Action
List documentsList documents within a document type/engine. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents.json
Action
List domainsList crawler domains configured on an Engine. GET /api/v1/engines/{engine_id}/domains.json
Action
List enginesList all Engines for the account. GET /api/v1/engines.json
Action
Recrawl domainTrigger a recrawl of a domain's crawled content. PUT /api/v1/engines/{engine_id}/domains/{domain_id}/recrawl.json
Action
Search documentsPerform full-text search over documents within an Engine. GET/POST https://search-api.swiftype.com/api/v1/public/engines/search.json with engine_key + q. Returns matching records grouped by document type.
Action
Update documentUpdate fields on an existing document. PUT /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}/update_fields.json
Action
Bypass bot detectionLoad a URL through Browserless's /unblock endpoint to bypass CAPTCHAs and bot detection, returning rendered content, cookies, and/or a screenshot per requested data flags.
Action
Capture a ScreenshotTakes a screenshot from a URL.
Action
Crawl a websiteAsynchronously crawl an entire site via Browserless's /crawl endpoint, scraping every page within the given depth/path filters and returning structured page data.
Action
Discover site URLsLoad a page in a real browser and return every link address found on it.
Action
Download a fileRun JavaScript code via Browserless's /download endpoint and retrieve a file that Chrome downloads during execution.
Action
Extract DataSearch for data within a website.
Action
Fetch a Site's HTMLScrapes the full HTML contents of a website.
Action
Generate a PDFGenerate a PDF from a URL.
Action
Measure a Website's PerformanceGet stats on a website's performance. (Google's Lighthouse tool)
Action
Run BQL QueryExecutes a Browser Query Language (BQL) script for sequential automation steps.
Action
Run custom functionExecute server-side Puppeteer JavaScript code (with optional context object) via Browserless's /function endpoint and return the function's result.
Action
Search the webQuery Browserless's /search endpoint for web results, optionally scraping the result pages and returning structured JSON.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.