Write Node.js code, ship npm-style
Each module is a folder with index.js, package.json and any npm dependencies you need. Edit files in your editor of choice — VS Code, Cursor, JetBrains — Afina watches and re-signs on demand.
RPA modules — Node.js code inside your flows
Write your own Node.js modules with npm dependencies and call them from RPA flows through the executeModule block. Signed execution, isolated runtime, full reusability — the bridge between no-code automation and real engineering.
Node.js • npm • executeModule
When clicks aren't enough, drop into code
Most RPA flows live happily on the visual canvas. The hard 10% — custom API calls, niche libraries, complex data transforms — wants real code. Afina modules are full Node.js packages with npm dependencies, an Ed25519 signature for execution safety, and a clean form-based UI in the parent flow.
Call modules from RPA flows
A new executeModule block accepts the module hash + a form payload. Module function receives the args, talks to the browser through Afina's helpers, returns a value back to the flow. Native interop with the rest of the scripts-and-automation stack.
Full npm ecosystem
Bring your favourite packages — axios, cheerio, ethers, sharp, anything. Afina installs dependencies in the module folder; the runtime allowlist limits node API surface so a misbehaving module can't kill your machine. Ideal companion to the local API.
Ed25519-signed execution
Every module has an Ed25519 signature over an md5 manifest of its files. The executor refuses to run an unsigned or stale module — protecting you from accidental corruption and supply-chain swaps. Combined with the MCP server, AI agents can author modules safely too.
Custom Node.js inside your antidetect browser
Write a module, sign it, drop it into a flow — your code, signed and isolated, running on a real browser.
Modules in Afina let you write real Node.js code that runs inside the antidetect browser context, call it from RPA flows, reuse it across profiles, and ship it with cryptographic signatures so nothing runs unsigned. Bring the npm ecosystem to your automation without trading off security.
Why modules sit between RPA blocks and the API
Visual RPA blocks cover 80% of automation; the local HTTP API covers the engineering-heavy 10%. Modules close the gap — when a flow needs a custom API call, a crypto signature, a complex parser or a private SDK, you write a Node.js module once, sign it, drop it into the RPA library, and every flow can use it.
What's inside Afina modules
1. Write in Node.js with the full npm ecosystem
Standard CommonJS / ESM modules. Use any npm package (axios, ethers, jsonwebtoken, sharp, your private SDK). Modules run in a Node.js subprocess with the profile context handed in.
2. Reuse across RPA scripts
Call a module from any RPA flow via the executeModule block. Pass input, get output, continue the flow. One module — every script benefits. Avoids the copy-paste hell of writing the same Puppeteer logic in 30 scripts.
3. Ed25519-signed execution
Every module carries an Ed25519 signature over an md5 manifest of its files. The executor verifies before each run. One altered byte — refusal to run. Part of the zero-knowledge model: no silent supply-chain swaps, no malicious dependency update going through unnoticed.
4. AI-friendly code generation
Via the MCP server, an LLM can create a module, edit files, run it, and re-sign it through the resign_module tool. Agents build flows end-to-end without ever leaving the host editor.
5. Local-first, optional sync
Modules live in your moduleDirAbs on disk. Push to the Afina cloud or your Google Drive to share across team and machines — opt-in per module.
Where modules shine
Crypto workflows that need to sign transactions on-device (no key ever leaves the machine). Custom integrations with internal SaaS APIs that have no public web UI. Heavy parsing — PDF extraction, OCR post-processing, marketplace HTML scraping. CAPTCHA solver integration. Any time you'd write a script in Puppeteer or Playwright but want per-profile fingerprint context and shared reuse across the RPA library.