Contractbook
DocumentsManage contract lifecycle in Contractbook, covering documents, templates, spaces and automations. Agents draft from templates and move contracts through their stages, and stop for a person before anything is sent for signature.
What This Integration Enables
Contractbook is contract lifecycle management, and the lifecycle is the part that matters. A contract has states, and the connector exposes the transitions between them. A document starts as a draft, which is the only state in which it can be freely changed. Create Document From Template produces one. Update Document amends one, and will only work on drafts and stored contracts, and only when the version you supply matches the version on the server. Send Document For Signature takes it out of draft and puts it in front of a counterparty. Everything about how you should build on this API follows from that shape.
The rest of the surface supports it. List Documents and Get Document read state, with filtering by title, state, type, tags, context and signed or updated date ranges, plus cursor pagination, so reporting contract status into the CRM is a scheduled read rather than a manual check. Get Document PDF returns a location URL for a rendered copy, which is what makes review possible on the actual document rather than on a description of it. Share Document and Unshare Document control who can see a contract by email address and role, with granular options covering which data fields a filler may update and whether they can see private comments and history or send for signature themselves. Spaces organise the account, and Get Space Tree and Create Child Space let a flow keep that structure aligned with how the business is actually divided. Upload Attachment brings a file in from a public URL, accepting PDF, Word, Excel, PowerPoint and common image formats.
Automations deserve a specific note because they change what this integration is for. List Automations returns the automations configured for a given trigger type, and Run Automation executes one against an external object. The supported trigger today is a Salesforce flow being executed, which tells you where Contractbook expects contract creation to originate: the CRM, at the moment a deal is done. Pair this with Salesforce or HubSpot and the drafting work disappears from the deal desk's afternoon. Put the review step in Slack and the approval happens where the deal owner already is, rather than in an inbox.
What an agent should not do here is decide. It can assemble a draft faster and more accurately than a person copying figures between two windows, and it can hold that draft indefinitely without getting bored. The transition out of draft is a different kind of act, and the next section is about why.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Closed-won to draft contract without retyping a figure
A deal closes. The agent reads the counterparty details, term length, seat count, price and jurisdiction from the CRM record, calls List Templates to find the right template for that product and jurisdiction, and calls Create Document From Template with the parties and data field values written straight from the deal. It then calls Get Document PDF and holds the location URL. The draft that reaches the approver is not a description of what the contract will say, it is the contract, rendered. The approver reads it, and the only thing they are asked to do is confirm the numbers and the counterparty, because the assembly is already done and already correct against the record it came from.
Contract status reported back where the deal lives
On a schedule the agent calls List Documents filtered by state and updated date range, walking pages through the cursor. It maps each document back to its deal through the tags or context set when the draft was created, and writes the current state onto the CRM record: still a draft, out for signature, signed, or stored. Nobody has to ask whether a contract went out, and nobody has to open a second system to answer. Where a document has sat out for signature past the point the team considers normal, the same read is what raises it, and the follow-up is a person's call rather than an automatic nudge to a customer.
Access that ends when the engagement does
An external adviser is brought in on a specific agreement. The agent calls Share Document with their email address and the appropriate role, restricting which data fields they may update and withholding access to private comments and private history, because the restriction options exist and using them costs nothing. When the engagement concludes or the record in the source system flips to closed, the agent calls Unshare Document and the access ends on the same day the reason for it did. This is the workflow nobody remembers to run by hand, and it is the one that leaves a third party holding a live contract link a year later.
Human-in-Loop Highlight
The gate on this connector is Send Document For Signature, and the case for it is unusually concrete. That single action is the door out of draft, and it is a one-way door in three separate senses.
The first is the obvious one. A contract sent for signature has left your building. The counterparty has it, they have read it, and no API call unsends it. Delete Document exists and it permanently deletes, which removes your copy and does nothing whatsoever about theirs. The second is a property of this API specifically: Update Document only works on drafts and stored contracts. Once a document is out for signature it is no longer a draft, so the correction you would want to make is not available to you, not to the agent, and not to the next flow you write. Draft is the only state in which anything is fixable, and Send Document For Signature is precisely the act of leaving it. The third is the option that makes the first two sharper. Send Document For Signature can auto-sign on behalf of the sending party where that party is a signee. Used carelessly, that turns a fully automated pipeline into one that applies your own company's signature to a document nobody read, and the resulting artefact is not a draft with a mistake in it. It is a binding offer with a mistake in it.
Consider what actually goes wrong. Nothing dramatic. Create Document From Template writes data fields from whatever the upstream record held, so a deal where somebody entered monthly price into an annual field produces a template that renders perfectly, reads professionally, and offers a twelfth of the intended contract value. A renewal picking up last year's seat count produces a document that is internally consistent and commercially wrong. Neither of these is a failed API call. Both complete successfully, and both are indistinguishable from a correct run until a person looks at the figures.
So FlowRunner puts a person exactly there, and only there. The agent does everything up to the door: it resolves the template, writes the parties and the data fields from the source record, uploads any attachments the agreement references through Upload Attachment, renders the document through Get Document PDF, shares it with the deal owner through Share Document, and posts the link with a plain-language summary of the commercial terms it wrote. Then it stops and raises a human-in-the-loop step in the channel the team already uses: "Draft ready for Nordgren Logistics AS. 24 month term, 45 seats, 38,400 EUR annual, Danish law, auto-renew on. PDF attached. Send for signature, send with auto-sign off, or return it to me with changes?" Nothing goes out until that answer arrives, the approver is recorded against the send, and if the answer is a correction the document is still a draft and therefore still fixable.
That is the digital andon cord doing the job it was named for. The agent is not slow and it is not uncertain. It stops at the last moment where stopping is still free, because one step later the cost of being wrong stops being an edit and starts being a conversation with a customer about a contract you already sent them.
Agent Capabilities
16 actionsDocuments
8- List Documents Retrieves a paginated, filterable list of documents covering drafts, contracts and stored contracts. Filter by title, state, type, tags, context and signed or updated date ranges, sort the results, and page through with cursor-based pagination. Set Include Full Data to also return data fields and full party details. This is the read behind status reporting: run it on a schedule to write contract state back onto the deal record, and use the state filter to find documents that have been out for signature longer than the team expects.
- Get Document Retrieves a single document by ID, including its parties, data fields, state and version. The version matters beyond simple curiosity: Update Document requires the current version and will refuse the change if it does not match the server's, so read before you write.
- Update Document Updates a document, supplying the fields to change in the Document Data object, which covers title, tags, parties and data fields among others. Only drafts and stored contracts can be updated, and the version you supply must match the latest version on the server. That state restriction is the single most important fact about this connector: a document out for signature cannot be amended here, so any correction has to happen while it is still a draft.
- Delete Document Permanently deletes a document specified by its ID. There is no recovery, and deleting a document that has already been sent removes your copy without affecting the counterparty's. Treat it as an administrative cleanup action for drafts that were never sent, and put anything broader behind an approval.
- Get Document PDF Retrieves a PDF copy of a document by ID, returning a location URL from which the generated file can be downloaded. The URL may take a moment to become available while the PDF is generated, so a flow should expect to wait rather than to fail. This is the action that makes review meaningful, because the approver reads the rendered document rather than a summary of what it is supposed to contain.
- Send Document For Signature Sends a document that is in a draft state for signature, optionally auto-signing on behalf of the sending party where that party is a signee. This is the transition that ends the ability to change anything, and the auto-sign option is the setting that decides whether a human being has looked at the agreement your company is about to be bound by. It belongs behind an approval in every flow that reaches a counterparty.
- Share Document Shares a document with a user identified by email address and assigns them a role. The granular options are worth using rather than skipping: restrict which data fields a filler may update, and control access to private comments, private history and the ability to send for signature. Sharing a document with someone who can send it for signature is functionally the same as granting them the send, so set that deliberately.
- Unshare Document Removes a user's access to a document, identifying them by email address. This is the closing half of any external-collaborator workflow, and the half most often skipped when it is done by hand. Tie it to the same source-system event that ended the engagement rather than to somebody's memory.
Templates
3- List Templates Retrieves the contract templates available in the account, optionally excluding templates that belong to Spaces. Resolving a template by name at run time rather than storing an ID keeps a drafting flow working when the legal team revises the template library.
- Get Template Retrieves a single contract template by ID, including its metadata and structure. Use it to confirm which data fields a template expects before a flow attempts to populate them, so a missing field surfaces as a check rather than as a blank line in a rendered contract.
- Create Document From Template Creates a new document as a draft from a template, setting title, language, tags, parties and data field values, with an Additional Document Data object for advanced fields not exposed as individual parameters. This is the drafting action, and everything it produces is still fixable, which is exactly why an agent should be trusted to run it unattended and not trusted to send what it produced.
Spaces
2- Get Space Tree Retrieves a space and its full tree of nested child spaces by ID. Use it to discover where a document should live before creating it, so filing follows the account's actual structure rather than a default.
- Create Child Space Creates a new child space within a parent space. Useful where the contract structure should mirror something the business already maintains, such as a new subsidiary, region or client engagement, so the organisation of contracts is created at the same time as the thing it organises.
Automations
2- List Automations Retrieves the automations configured in the account for a given trigger type, with an optional trigger filter object. Use it to discover what the account already automates before adding a flow that duplicates it.
- Run Automation Runs a specific automation by ID against an external object. Currently supported for automations whose trigger is a Salesforce flow being executed, taking the external object type and ID, and optionally Salesforce contact IDs and publicly accessible attachment links. This is where Contractbook expects contract creation to start, at the deal record in the CRM, and it lets a FlowRunner agent invoke logic the legal team has already configured rather than reimplementing it.
Attachments
1- Upload Attachment Uploads a file to Contractbook from a publicly accessible URL and returns URLs for the stored original and a preview. Accepted types include PDF, Word, Excel, PowerPoint and common image formats. Note the requirement that the source URL be publicly accessible, which is a deliberate decision about a document rather than a technical detail to work around.
Frequently Asked Questions
What can FlowRunner do with Contractbook?
FlowRunner agents can run List Documents, Get Document, and Update Document in Contractbook, plus 13 more actions.
Does connecting Contractbook to FlowRunner require OAuth?
No. Contractbook connects to FlowRunner with an API key, no OAuth flow required.
Can Contractbook trigger a FlowRunner workflow automatically?
Contractbook doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Contractbook
$100 in credits. No card required. Connect in minutes.