Connect your app to Scrive for e-signatures and eID
Scrive lets your app send documents for digital signatures or verify customer identities using national electronic IDs. You connect your Scrive account or security token in your workspace settings, then prompt Lovable to build the workflow.
Anyone who needs customers to sign legal documents or prove their identity during onboarding.
Do this, in order
- 1
Go to Connectors in your Lovable dashboard, select Scrive, and click Connect.
This starts the setup wizard to connect your Scrive service to Lovable.
- 2
Choose whether you are setting up Scrive eSign for document signatures or Scrive eID Hub for identity verification.
Each Scrive product requires its own distinct connection type.
- 3
For eSign, choose the permissions you want to grant, click Connect, and approve access in the Scrive pop-up window.
This securely links your Scrive account so your app can create and send documents.
- 4
For eID Hub, select your environment, paste your Scrive-provided security token, and click Connect.
Lovable tests your token immediately against Scrive to ensure it works before saving.
- 5
Open your project chat and tell Lovable to link your new Scrive connection and build your feature.
Connecting Scrive in workspace settings does not activate it in a project until you ask Lovable to link and use it.
Paste this into your project
Use Scrive and build a page where our sales team uploads a contract PDF, adds the customer as a signatory, and sends it for signature. Show each contract's signing status in a table.
Words decoded
- eID
- Official electronic identity systems, like Swedish BankID or Danish MitID, that citizens use to prove who they are online.
- Scopes
- Specific access permissions you grant to an app, such as reading documents or creating new ones.
- Testbed
- A safe testing sandbox where you can try features using dummy data before going live.
Where people get stuck
- Scrive eSign only connects to live accounts, meaning all test documents sent are real and will email actual recipients.
- eID Hub tokens are strictly tied to either testbed or production; a test token will fail if connected to the production setting.
- You must create two separate connections if your project requires both document signing and identity verification.
- All signature requests and identity checks incur billing from Scrive according to your Scrive subscription plan.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.