Scrive

Run the full e-signature lifecycle in Scrive. Agents create documents from PDFs or reusable templates, start the signing process, remind signatories who have not signed, cancel or trash documents, and download the signed PDF with its audit trail.

9 actions Custom auth available

Scrive website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A deal moves to the closing stage in the CRM with the negotiated terms attached

Create Document From Template instantiates the master services agreement with the deal's parties and values filled in

Get Document verifies the draft's fields and signatories match the CRM record

The deal owner reviews the prepared contract, the counterparty names, and the amounts before anything leaves the building

Start Signing Process moves the document to pending and delivers invitations by each party's channel

Get Document polls signing status daily; unsigned parties past three days get Send Reminders

When the status reaches closed, Download Main PDF retrieves the signed contract with its audit trail page

The signed PDF files to contract storage and the deal channel gets the completion notice

What This Integration Enables

E-signature platforms all promise a faster close; the slow part was never the signature, it was everything around it: assembling the document, checking the terms, chasing the silent party, filing the executed copy. Scrive's document lifecycle, preparation to pending to closed, maps cleanly onto workflow steps, and that is what this connector automates. FlowRunner agents create drafts from PDFs or reusable templates, start the signing process, remind the unsigned, withdraw the obsolete, and pull the final PDF with its signature and audit page into your systems of record. - Send contracts, NDAs, and forms for signature straight from deal, order, and onboarding workflows - Instantiate Scrive templates with values from the triggering record - Track signing progress and remind only the parties who have not signed - Cancel documents sent in error or overtaken by renegotiation - File every executed PDF, with its audit trail, where finance and legal expect it The send itself is the moment that matters. A contract invitation is a legal act aimed at a real counterparty, which is why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate on this page sits directly in front of Start Signing Process.

Without FlowRunner

Contracts assembled by hand Every close means copying deal terms into a document, attaching the right signers, and hoping nothing was pasted wrong

Chasing signatures manually Someone keeps a mental list of who has not signed and sends awkward nudge emails

Signed PDFs scattered The executed copy lives in someone's inbox, the CRM has a stale draft, and audit season is archaeology

With FlowRunner

Contracts assembled from the deal record Templates instantiate with the CRM's own values, so the document and the deal cannot disagree

Reminders on a policy Unsigned parties get chased on a schedule, through their configured channel, without anyone tracking it

Every executed contract filed The signed PDF with its audit trail lands in storage and on the deal automatically

Use Case Scenarios

Close stage to countersigned without retyping

A deal in [HubSpot](/integrations/hubspot) hits the contract stage. The agent calls Create Document From Template against the MSA template, overriding party names, term, and value from the deal record. Get Document confirms the draft, the owner approves it, and Start Signing Process delivers invitations. The returned document ID writes back to the deal, so the CRM always knows which Scrive document governs which deal. On closed status, Download Main PDF files the executed copy and the deal advances automatically.

High-value orders that need a signature

An order above the credit threshold arrives from [Shopify](/integrations/shopify). Instead of shipping on open terms, the agent generates a purchase agreement with Create Document From Template, routes it through review, and sends it for signature. Fulfillment holds until Get Document reports closed. The customer signs on their phone in minutes when the terms are right, and when they are not, the order never shipped unsecured.

The signature chase that runs itself

Every morning, List Documents pulls everything in pending status. Documents unsigned past the reminder threshold get Send Reminders, delivered by each signatory's configured method, email or SMS. Documents approaching their timeout date escalate to the owner in [Slack](/integrations/slack) with the full signing status from Get Document: who signed, who opened, who has gone quiet. Deals that died get Cancel Document after the owner confirms, and closed-out clutter moves to Trash Document, which hides but never destroys.

Human-in-Loop Highlight

Start Signing Process is the point of no quiet return. The moment it runs, Scrive delivers signing invitations to every party by email or SMS, and a contract with the wrong amount, the wrong entity, or last quarter's terms is now sitting in a counterparty's inbox as a legally signable offer. Cancel Document can withdraw it, but the counterparty already saw it, and some damage does not cancel. So agents on this page prepare and verify, and a person releases: "MSA for Norrland Logistics AB, 24-month term, 38,400 EUR annual, signatories per deal record: CFO and their procurement lead. Send for signature?" The deal owner checks the names and the number, approves, and the invitations go out. Everything after that, polling, reminders, filing the signed PDF, is safely mechanical.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Document Creation

Create Draft From File Creates a draft document from a PDF at a public URL, with an optional definition for title and parties. The draft lands in preparation state, ready for review and sending.
Create Document From Template Instantiates a Scrive template as a fresh draft, copying its file, fields, and parties, with optional overrides. The step that turns deal records into ready-to-sign contracts.

Lifecycle

Start Signing Process Moves a draft from preparation to pending and delivers invitations to all signatories by their configured method. The legal send, and the action behind this page's human gate.
Send Reminders Sends reminder invitations to the signatories of a pending document who have not yet signed. The polite persistence nobody has to remember to apply.
Cancel Document Cancels a pending document, stopping the signing process. Used to withdraw contracts sent in error or overtaken by renegotiation.
Trash Document Moves a document to the trash, hiding it from the main list while keeping it restorable within Scrive. Cleanup without destruction.

Tracking and Retrieval

Get Document Retrieves a document's full state: status across the lifecycle, every party's signing status, fields, and files. The polling step behind progress tracking and closed-state detection.
List Documents Lists account documents with status filtering, full-text search, and pagination. The sweep behind the daily signature chase.
Download Main PDF Downloads the document's main PDF as base64: the signed PDF with its signature and audit trail page once closed. The retrieval step that files the executed contract.

Frequently Asked Questions

What can FlowRunner do with Scrive?

FlowRunner agents can run Create Draft From File, Create Document From Template, and Get Document in Scrive, plus 6 more actions.

Does connecting Scrive to FlowRunner require OAuth?

Scrive uses a custom authentication method to connect to FlowRunner.

Can Scrive trigger a FlowRunner workflow automatically?

Scrive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Scrive

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us