How to Add E-Signatures to Your Bubble.io App: The Firma.dev Plugin Walkthrough

Building e-signature into a Bubble.io app the hard way means stitching together a PDF renderer, a signing flow, and some kind of audit trail before you can call a contract signed. Most teams don't get past step one. The Firma.dev plugin skips all of that: install it, connect two API keys, and your app can start collecting e-signatures that are legally valid in 55+ countries the same day.

Watch the Bubble.io e-signature walkthrough

The video above walks through the full Bubble.io e-signature setup in under two and a half minutes. Everything below covers the same steps in writing.

Prerequisites

• A Bubble.io account with an app you're actively building

• A free Firma.dev account, no credit card required

Step 1: Install the e-signature plugin in Bubble.io

From your Bubble editor, open the Plugins tab and click Add plugin. Search for firma.dev and install it directly from Bubble's plugin directory. No custom API connector setup, no manual endpoint configuration.

Step 2: Get your API keys

Once installed, the plugin asks for two things: an API key and a test (developer) key.

Log into your Firma.dev dashboard and you'll see a live API key and test API key sitting at the account level. These belong to what Firma.dev calls your Protected Workspace, the one workspace every account gets by default, and they can reach every workspace, key, and webhook on the account... useful for a quick test, but not what you want wired into a production app.

Instead, create a workspace. Every workspace you create gets its own live and test key pair, scoped to that workspace only. Most builders create one workspace per customer or department, which keeps signing activity, and the keys that unlock it, cleanly seperated instead of running everything through one global credential.

Step 3: Wire e-signatures into your Bubble app

Copy the workspace's live API key and test key into the plugin's settings fields in Bubble. That's the entire integration... from here you keep building your app exactly as you would otherwise, with signing requests, embedded editors, and signer workflows available as native plugin actions.

Common gotchas

• Don't ship the Protected Workspace key. It's account-wide by design, so a leak or a bug in your app logic exposes everything, not just one customer's documents.

• Test keys don't burn credits. Build and QA your signing flow against the test key, then swap to the live key when you're ready to send for real.

• One workspace, one key pair. If you're building a multi-tenant app, create a workspace per tenant up front rather than retrofitting it later.

What Bubble.io e-signatures cost

Firma.dev is pay-as-you-go at €0.049 per envelope (~5¢ USD), with no monthly minimums, no per-seat fees, and no contract. Compare that to DocuSign's retail API pricing, which starts around $4 to $5 per envelope, and the plugin runs 97 to 99% cheaper.

Next steps

Once the plugin's installed and your workspace key is in place, the rest is standard Bubble.io app-building. Add a signing request action wherever your flow calls for a signature, and Firma.dev handles the rest... signer email, completed document, audit trail included.

Get started with Firma.dev for free, no credit card required. Full setup docs, including API key authentication, are at docs.firma.dev. Stuck on something? Email support@firma.dev.