Skip to main content
Scrive is a European provider of electronic signatures and electronic identification (eID). The Scrive connector lets your Lovable app work with two Scrive products:
  • Scrive eSign: create documents, send them for signature, and track their signing status, including multi-party Flow signing workflows.
  • Scrive eID Hub: verify who your app’s users are, or have them sign, with national eIDs such as Swedish BankID, Danish MitID, Norwegian BankID, Freja, Smart-ID, and itsme.
Each connection uses one of the two products. To use both, create one connection for each. Scrive is available as an app + chat connector: one shared connection that works in the project chat while you build and in your published apps.

​
Common use cases and example apps

These examples show what you can build with Scrive, each with a prompt to start from.

​
How to connect Scrive

Who can create Scrive connections depends on your plan and workspace settings. App + chat connectors are available by default. On Business and Enterprise plans, Who can create connections and clients starts at Admins. Some Enterprise workspaces start at No one, which disables the connector. An admin or owner changes it in Connectors → Admin settings → App + chat connectors. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

​
Prerequisites

Before connecting Scrive, make sure you have:
  • For Scrive eSign: a Scrive account with access to eSign.
  • For Scrive eID Hub: an eID Hub API token issued by Scrive for your company. Scrive sets up eID Hub accounts and issues tokens, so contact Scrive if you don’t have one. Tokens are issued per environment: testbed first, then production after Scrive has validated your integration.
  • Permission to create connections in your Lovable workspace (see Who can create connections and clients).
Signatures and eID transactions your app makes through this connector are billed by Scrive under your Scrive agreement, not by Lovable. See Scrive’s pricing page.

​
Set up your Scrive connection

The setup depends on which Scrive product the connection uses. Scrive eSign connects with your Scrive account, and Scrive eID Hub connects with your company’s API token.
1

Open Scrive in Connectors

Open Connectors and select Scrive. For the other places to open the catalog from, see Where to find connectors.
2

Add a connection

Click Connect on the connector page. The form is split into collapsible sections, Details, Configure connection, and Sharing.
3

Name the connection

Under Details, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection.
4

Select Scrive eSign and choose scopes

Under Configure connection, select Scrive eSign. The Scopes list shows the permissions Lovable requests from your Scrive account:
  • Read documents (doc:check): list documents and read signing status. Required.
  • Keep connected (offline_access): refresh access when the access token expires. Required.
  • Create documents (doc:create): upload PDFs and update documents and signatories.
  • Send documents (doc:send): start signing processes.
  • Full account access (full): required for Scrive Flow, the multi-document signing workflows. Clear it if your app only works with single eSign documents.
All scopes are selected by default. Clear the ones your app does not need. For example, an app that only shows signing status needs the two required scopes.
5

Choose who can use this connection

Under Sharing, the connection is private to you by default and shows a Private label. To share it, click Share with others. Then add workspace members by email, or click Invite entire workspace to make the connection available to everyone in your Lovable workspace.See Who can use connections and clients for more information.
6

Connect to Scrive and authorize

Click Connect. The Scrive authorization window opens, so make sure your browser doesn’t block pop-ups. If it does, Lovable redirects you instead.Sign in to Scrive if prompted, review the requested permissions, and authorize the app.You’ll be redirected back to Lovable with a confirmation.
Documents your app sends through this connector are real signing requests from your Scrive account, and signatories receive them. Only link the connection to projects that should be able to send documents, and test with your own email address first.
When connected, anyone building in a project can ask Lovable in chat to link their project to Scrive (based on configured connection-level access). Your Lovable apps can then send documents for signature or verify users with eIDs, depending on the product the connection uses.

​
How eID verification works

Scrive eID Hub verifies a user in a transaction. Your app creates the transaction with the eID provider and whether the user should authenticate or sign, sends the user to Scrive’s hosted eID page, and reads the verified result (such as the user’s name and personal number) when the user comes back. A transaction ends as either complete or failed. Not every eID supports both authentication and signing. For example, MitID, iDIN, and OneID support authentication only. For the full list of eIDs and what each supports, see Scrive’s eID provider guide.

​
Limitations

The Scrive connector cannot:
  • Connect a Scrive eSign testbed account. Scrive eSign connections use Scrive’s production service, so test documents are real signing requests.
  • Support per-end-user Scrive login. Each Scrive eSign connection represents a single Scrive account shared across all projects linked to it.

​
Manage your Scrive connection

Connections are managed from Connectors: select Scrive, then open the connection.
  • Unlink projects to remove Scrive access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
  • Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Scrive stop working until a new connection is added. See Delete a connection for the steps and who can delete.