Can a prompt replace Bardeen?

Build a browser extension that extracts data from the page you're currently viewing and sends it to one connected service — working on sites that don't have their own API, which is Bardeen's actual differentiator over a pure API-to-API tool like this catalogue's Pipedream entry. Use a Chrome extension (Manifest V3) with a content script that, when triggered by a keyboard shortcut or a right-click context-menu item, extracts structured data from the current page using CSS selectors you define per site, such as product name, price, and URL from an e-commerce page. Send the extracted data to one connected service's API — a spreadsheet, a note-taking app, or a CRM, pick one — using that service's documented API and OAuth or API key. Show a confirmation preview of the extracted data before sending, so a broken selector from a site redesign is caught before bad data gets sent, not after. Store a small library of site-specific extraction configs, which CSS selectors map to which fields per domain, locally, editable when a site changes and breaks extraction. Do not build a library of many pre-built playbooks across dozens of sites and services, or a visual no-code builder — those are out of scope; this handles exactly the site/service combinations you configure yourself. Needs a domain for OAuth callback handling and an OAuth app registration with your chosen destination service.