Legito

Connect AI agents to Legito, a no-code document automation and contract lifecycle platform. Agents generate documents from templates, manage records through their lifecycle, control sharing, and react to workspace events.

1 trigger 64 actions Custom auth available

Platform Documentation ↗ Capability data verified 2026-08-04

On Document Event fires when a Document Record reaches the chosen state, through a Legito Push Connection this flow registers on activation

Get Document Version Data returns the values that were filled into the record

The agent checks required values against List Properties and the record's Document Record Type before anything renders

Generate Document renders the record from its Template Suite into the requested format

Download Document pulls one rendered file, so a person reads the actual output rather than the input data

The contract owner receives the rendered sample, the Template Suite it came from, and the counterparty it is bound for

The owner approves the clause set, and Create External Link issues the counterparty link only on that answer

What This Integration Enables

Legito is a no-code document automation and contract lifecycle platform, and the most important thing to understand about automating it is which object carries the risk. A Document Record is an instance. A Template Suite is the thing that decides what every instance says. Generate Document renders one against the other, which means the quality of a hundred generated contracts is a property of the template, not of the hundred requests that produced them. An agent operating here is fast at instances and completely blind to the template it is invoking.

The connector covers the lifecycle end to end. Document Records are listed, created, updated, deleted, and anonymised. Documents are generated from a Template Suite or directly from JSON, their version data is read and written, and the result is downloaded into FlowRunner file storage as PDF, DOCX, or another supported format so the rest of a flow can use it. Object Records hold the structured data templates draw on, so a flow can keep a counterparty list or a rate card current in Legito rather than passing it in on every call. Files are uploaded, downloaded, listed, and deleted. Users, user groups, permissions, and notification settings are fully manageable, which makes provisioning and deprovisioning workspace access a workflow step rather than an administrative chore.

Sharing deserves separate mention because it is where documents stop being internal. Share With User and Share With User Group grant access to people inside the workspace. Create External Link does something different in kind: it produces a door into a document for someone who has no Legito account at all. Update External Link changes it and Delete External Link closes it, but closing a link ends future access rather than recalling what has already been read.

This connector has a real trigger. On Document Event fires when a chosen Document Record event occurs in the workspace, including created, updated, signed, shared, and workflow status changed. It works by registering a Legito Push Connection webhook for the selected event type when the flow is activated and removing it when the flow is torn down, so FlowRunner genuinely receives the event rather than polling for it. The two actions in the Events group are read-only inventory around that mechanism: List Events reports the event types the workspace supports, and List Push Connections reports the registrations that currently exist. Neither creates a subscription and neither delivers anything to a flow.

Without FlowRunner

Contract data retyped into a template Values already captured in a CRM or a form are entered again by hand into the document

Template changes discovered downstream Nobody notices a clause changed until a counterparty asks about it

Sharing is ad hoc Documents leave the workspace as email attachments with no record of who has which version

With FlowRunner

Records generated from source data Values flow from the system that captured them into the Document Record and the rendered file

One sample read before a batch goes out A person confirms the rendered clause set once, before it reaches anyone outside

External access is a tracked object Counterparty links are created, updated, and revoked as workflow steps with a record of each

Use Case Scenarios

A contract that assembles itself and still gets read

A sales team closes a deal in HubSpot. The flow creates a Document Record of the right Document Record Type, writes the negotiated values into it with Update Document Version Data, and calls Generate Document against the standard Template Suite. Then it downloads the rendered PDF and stops. The contract owner reads the actual document, not the field values, because a template can be perfectly populated and still say the wrong thing. On approval the flow calls Create External Link and sends the counterparty their link through Gmail, then records the link and the document identifier against the deal. The generation was instant. The reading was not skipped.

Reacting to the signature rather than asking about it

On Document Event is configured for the signed event type. When a counterparty signs, the flow wakes without anyone polling. It calls Download Document to pull the executed file, uploads it into the matter folder in SharePoint, writes the executed date and the document reference back onto the opportunity record, and posts to the deal channel in Slack. Then it calls Delete External Link to close the counterparty's access, because a link that was needed for signature is not a link that should stay open afterwards. The whole sequence runs in the minutes after signature rather than the days after somebody checks.

Keeping the data behind the templates current

Templates in Legito draw on Object Records, which is where things like entity details, standard rates, and approved counterparty terms live. When any of those change in the source system, the flow calls List Object Records to find the matching entry and Update Object Record to correct it, or Create Object Record when it is new. Because this data feeds every future generation, the flow treats it as a controlled update rather than a sync: changes are batched, diffed against what List Object Records currently returns, and posted for review before they are applied. The same discipline covers List Labels, Create Label, and the Document Record Type actions, which shape how records are classified across the whole workspace.

Human-in-Loop Highlight

The gate belongs on Create External Link, and the argument for it starts one step earlier. When an agent calls Generate Document for a batch of records, every document in that batch inherits whatever the Template Suite currently contains. Nobody in the flow reads a clause. The agent supplies values and receives files, and a template revision made last week by someone in a different team is applied to all of them silently and identically. That is usually fine and occasionally very much not, and the difference is invisible from inside the request. Then Create External Link changes the situation qualitatively: it issues access to someone with no account in the workspace, typically a counterparty, and what they read they have read. Delete External Link revokes future access. Update External Link changes the link. Neither of them reaches into somebody's inbox. And Anonymize Document Record, the only other irreversible operation here, destroys the record rather than correcting the document. So the flow generates the batch, downloads exactly one rendered file, and asks a person to read that one: "12 NDAs generated from the Standard Mutual NDA suite for the Q3 partner list. Sample attached, rendered from the live template. Confirm the clause set before external links are issued to all 12." A contract owner reads a real document, once, and the batch goes out on that answer. This is human-in-the-loop sized to the actual risk: reviewing twelve identical documents is theatre, reviewing the one thing that determines all twelve is the job.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

64 actions

Workspace

Get Workspace Info Returns the workspace's configuration and identity. The orientation call for a flow that runs across more than one Legito workspace or datacenter region.

Document Records

List Document Records Lists Document Records in the workspace with filtering. The starting point for lifecycle sweeps, renewal checks, and reconciliation against a CRM.
Create Document Record Creates a new Document Record of a given type. The container that a generated document belongs to.
Update Document Record Updates an existing Document Record's metadata. Used to move a record through a lifecycle as external facts change.
Delete Document Record Removes a Document Record. A destructive operation on the container and everything hanging off it.
Anonymize Document Record Anonymises a Document Record, stripping the personal data it holds. Irreversible, and intended for data subject erasure rather than cleanup, so it should never be reached by an ordinary retention rule without a person in the path.

Document Generation

Generate Document Renders a document for a Document Record from its Template Suite. The central action in this connector, and the one that silently applies whatever the template currently says to every record in a batch.
Generate Document From JSON Renders a document directly from a supplied JSON payload rather than from an existing record's stored values. Useful when the data lives entirely in the flow and no record needs to persist.
Update Document Version Data Writes values into a document version. How a flow populates a contract from a CRM, a form, or an upstream agent's output.
Get Document Version Data Reads the values held on a document version. Used to check what was filled in before rendering, and to extract agreed terms back out after signature.
Download Document Downloads a generated document in PDF, DOCX, or another supported format into FlowRunner file storage, returning a URL the rest of the flow can use. The action that puts a real rendered file in front of a person.

Files

List Files Lists files held in the workspace.
Upload File Uploads a file into the workspace, for attaching supporting documents to a record.
Download File Downloads a workspace file into FlowRunner file storage and returns its URL.
Delete File Removes a file from the workspace.

Users

List Users Lists the workspace users. The basis of any access review.
Create User Creates a workspace user. Used to provision access as part of an onboarding flow rather than by hand.
Update User Updates an existing user's details.
Delete User Removes a user from the workspace. The deprovisioning counterpart, and worth running from the same joiners and leavers flow that provisions.
Get User Permission Reads a user's permissions. The read to run before changing anything, and the read that makes an access review possible at all.
Update User Permission Changes a user's permissions. A quiet but consequential write, because permissions decide who can see which contracts.
Get Notification Settings Reads a user's notification settings.
Update Notification Settings Changes a user's notification settings, useful when a flow takes over a notification that a person used to receive by email.

User Groups

List User Groups Lists the user groups defined in the workspace.
Create User Group Creates a user group, typically to mirror a team or a matter in the workspace access model.
Update User Group Updates a user group's definition.
Delete User Group Removes a user group, along with the access it conferred.
Add User To User Group Adds a user to a group, granting them everything the group can reach.
Remove User From User Group Removes a user from a group. The fastest way to revoke a set of access in one call.

Sharing

List Shares Lists the shares on a document or record. The audit read that answers who currently has access.
Share With User Grants a named workspace user access to a document.
Remove User Share Revokes a named user's access.
Share With User Group Grants a user group access to a document, which scales access with team membership rather than with individual grants.
Remove User Group Share Revokes a user group's access.
Create External Link Creates a link that grants access to a document for someone outside the workspace, with no Legito account required. This is the moment a document leaves the building, and the write this page argues should always be preceded by a person reading the rendered output.
Update External Link Updates an existing external link's configuration.
Delete External Link Deletes an external link, ending future access through it. It does not recall anything already read, so it closes a door rather than undoing a disclosure.

Object Records

List Objects Lists the object definitions available in the workspace, meaning the structured data types templates can draw on.
List Object Records Lists the records held against an object. The read to diff against before applying any bulk update to reference data.
Create Object Record Creates a new object record, adding an entry to the structured data behind the templates.
Update Object Record Updates an object record. Because templates read this data, a change here reaches every document generated afterwards.
Delete Object Record Deletes an object record.

Metadata

List Template Suites Lists the Template Suites available. The read that tells a flow which templates exist and which one a generation will actually use.
List Template Tags Lists template tags.
Create Template Tag Creates a template tag, used to organise templates across a large suite library.
List Categories Lists workspace categories.
List Document Record Types Lists the Document Record Types defined, which determine the shape and required values of a record.
Create Document Record Type Creates a Document Record Type. A structural change to how the workspace classifies documents.
Update Document Record Type Updates a Document Record Type, which changes the shape of records already classified under it.
Delete Document Record Type Deletes a Document Record Type.
List Labels Lists the labels defined in the workspace.
Create Label Creates a label for classifying records.
Delete Label Deletes a label, removing that classification wherever it was applied.
List Properties Lists the properties available on records. Used to validate that a payload carries everything a template will need before generation runs.
List Property Groups Lists property groups, which organise properties into the sets a template expects.
List Advanced Styles Lists the advanced styles available for rendering.
List Workflows Lists the workflows defined in the workspace, meaning the approval and lifecycle paths documents follow inside Legito.
Get Workflow Revision Retrieves a specific revision of a workflow, which is how a flow learns what path a document is actually on rather than what path it was designed for.

Reference Data

List Countries Returns the country reference list used by templates and records.
List Currencies Returns the currency reference list.
List Languages Returns the language reference list, which decides which language version a document generates in.
List Timezones Returns the timezone reference list.

Events

List Events Lists the Document Record event types the workspace supports. A read-only inventory of what can be subscribed to, not a subscription itself.
List Push Connections Lists the Legito Push Connection registrations that currently exist. Read-only, and useful for auditing which webhooks are live in a workspace, including ones this connector did not create.

Triggers

1 triggers

Event Triggers

On Document Event Fires when a chosen Document Record event occurs in the workspace, including created, updated, signed, shared, and workflow status changed. On flow activation this registers a Legito Push Connection webhook for the selected event type, and removes it when the flow is torn down, so events are delivered to FlowRunner rather than polled for. Use it to react at the moment a contract is signed, a record changes hands, or a workflow status moves, instead of running a sweep and hoping the interval is short enough.

Frequently Asked Questions

What can FlowRunner do with Legito?

FlowRunner agents can run Get Workspace Info, List Document Records, and Create Document Record in Legito, plus 61 more actions.

Does connecting Legito to FlowRunner require OAuth?

Legito uses a custom authentication method to connect to FlowRunner.

Can Legito trigger a FlowRunner workflow automatically?

Yes. Legito supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Legito

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

Start Building Free Talk to us