RPA for platforms without APIs
If your operation depends on uploading, downloading, or reconciling data in platforms that have no API (compliance portals, legacy systems, regulatory platforms), we automate that layer without asking the provider for anything.
The problem nobody wants to solve
Many industries depend on platforms imposed by their clients or regulators, with no documented API. Supplier compliance portals, client-owned HR systems, closed ERPs, government systems.
The usual option is to hire someone to do it manually, with the latency and errors that implies. A document expires and nobody notices until the client calls. A credential is rejected and 48 hours pass before retrying.
Typical scenarios we solve:
- → Document upload in compliance portals of large clients (mining, salmon farming, construction) that impose proprietary platforms.
- → Daily extraction from regulatory or government systems (filings, certifications, paperwork).
- → Sync between closed ERPs without connectors and your internal management systems.
- → Keeping field-worker documentation up to date across multiple platforms, each with its own format and expiration dates.
How we solve it
We automate that layer with Playwright plus AI-assisted analysis, handling login, two-factor authentication when applicable, navigation, file uploads, rejection detection, and alerts when the platform changes.
Robust authentication
Login with secure credentials, persistent session management, automatic 2FA resolution via TOTP or SMS capture. If the platform logs you out, the bot re-authenticates without intervention.
Navigation and file upload
The bot navigates the platform like a human user: opens forms, fills fields, attaches files, submits. We handle complex paths, dynamic menus, and multi-step forms with per-stage validation.
Smart rejection and error detection
We use AI to interpret error messages, detect document rejections, and classify the reason. The bot doesn't just try: it knows when it failed and why.
Alerts on platform changes
UIs change. When the provider updates the platform, the bot detects it and alerts. We adjust the flow within hours, not days.
Human-in-the-loop model for hard cases
When there's aggressive anti-bot protection (Cloudflare Turnstile, reCAPTCHA v3, visual captchas), we adapt the solution to a human-assisted model for critical steps. The bot does 95% of the work, a human operator authorizes protected steps.
What we deliver
Production RPA bots per platform
A scraper or automated flow for each critical platform, running on dedicated infrastructure with 24/7 monitoring.
Unified compliance dashboard
Single view showing the state of each platform, each document, and each pending operation, with traffic-light indicators for expiration and rejection.
Configurable alert system
Email or WhatsApp notifications when a document is rejected, a platform changes its UI, or an expiration is near.
Audited traceability of every operation
Detailed log of each attempt with screenshots, timestamps, response codes, and result. Evidence for internal or external audits.
Monthly maintenance contract
UIs change. Service includes adjustments when the platform updates, within the agreed SLA. You don't pay per change.
Frequently asked questions
Is it legal to automate a platform without the provider's permission?
If you have legitimate credentials and are performing operations that already belong to you as a user (uploading your own documents, downloading your own data), automating those operations is your right. We don't scrape third-party data or access information that isn't yours. We always work from inside your account, with your credentials, doing what an employee of yours would do manually.
What if the platform detects the bot?
We use human-like navigation techniques (realistic delays, movement patterns, correct headers). If the platform has aggressive anti-bot protection (Cloudflare Turnstile, visual captchas), we apply the human-in-the-loop model: the bot does 95% of the work automatically, and a human operator authorizes protected steps with 2 or 3 clicks.
What happens when the platform changes its interface?
The system detects the change automatically and alerts. Adjustments are included in the monthly maintenance contract and don't generate extra charges. Typically the adjustment takes 1 to 3 business days depending on the scope of the change.
How long until the first bot is in production?
A simple bot (one platform, basic operations like document upload) can be in production in 3 to 6 weeks. Complex systems with multiple platforms and interconnected flows, 8 to 12 weeks. The first week is diagnostic: we map each platform and define scope.
Does your operation depend on a platform without an API?
Let's talk about your case. We'll tell you if it's feasible to automate and which model fits best.