Integration
Connect Parseur to Browserless
When something happens in Parseur, 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 Parseur 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 Parseur and Browserless
Triggers and actions 6 triggers · 22 actions
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
New Document Processed (With List Items)Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
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.
Each app on its own
Reviews