Installs in ~2 min· 3 assets · 4 steps

Move contracts through legal and management with risks already flagged

Legal, then management, then executed, with the risky clauses already circled.

Contracts get stuck in two places: waiting on legal, and waiting on whoever legal is waiting on. This recipe makes both stages one tap. A requester submits the contract with its key terms and the draft file. AI rates the risk (auto-renewal, uncapped liability, indemnification, exclusivity, missing terms) so neither reviewer is reading cold. Legal clears it, management signs off, and the requester is emailed at every stage, including which stage sent it back.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Contract Submission Form is submitted
Every run starts from one submission.
Transform
AI Risk Review
AI reads the input and returns a structured result.
Logic
Legal Review
Pauses for a person to approve or reject.
Logic
Management Approval
Pauses for a person to approve or reject.
Action
Notify & Email the Decision
What gets built

3 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormContract Submission Form

Where a requester submits a contract for approval, types the key terms for AI risk review, and attaches the draft. Publishing it auto-creates the Contracts response sheet, the single system of record.

EmailContract Decision

Tells the requester the outcome at every stage (executed, or returned by legal or by management) with the AI risk notes and next steps.

WorkflowRoute Contract for Approval

Logs each contract, produces the AI risk summary from the typed key terms, routes it through sequential legal and management approvals, then marks it executed or emails the requester if either stage returns it.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Approval And Notification
Slack *

Posts the legal and management review requests with the secure review link, and announces executed contracts to your contracts channel. Swap for Telegram, Discord or Google Chat.

Decision Email
Gmail *

Emails the requester the decision at every stage, executed, or returned by legal or management. Swap for Brevo.

How it works

Step by step, once it is running.

  1. 01
    A Contract Is Submitted

    The requester completes the Contract Submission Form (title, counterparty, type, value, dates) types the key terms in their own words (payment terms, renewal, liability, exclusivity, IP, termination), and attaches the draft file. Submitting logs the contract and fires the workflow. Write the key terms out properly, those are what the AI risk review reads. The attached draft travels with them to both human reviewers.

  2. 02
    AI Flags the Risk

    The AI Risk Review step reads those typed key terms and rates the contract's risk, calling out auto-renewal, uncapped liability, indemnification, exclusivity, and terms that are simply missing. Anything at or above the high-value threshold you set at install is treated as high-risk on value alone. The point isn't to replace legal review, it's so legal opens the request already knowing where to look.

  3. 03
    Legal Reviews, Then Management Signs Off

    Legal receives the contract, key terms, risk notes, and file link in Slack, and either approves it forward or returns it to the requester. Legally-cleared contracts then go to management for a final one-tap approval. Two real stages, in order, each one a link away. Swap Slack for Telegram, Discord, or Google Chat at install.

  4. 04
    It's Executed, or Returned

    Fully approved contracts are marked executed, your contracts channel is notified, and the requester is emailed. A rejection at either stage sends the contract back to the requester by email, naming which stage returned it and carrying the AI risk notes, so they know what to fix rather than what to guess.

What you walk away with
FAQ

Questions about Contract Approval Workflow.

What does the AI actually check?
It reads the submitted contract and flags the clauses worth a second look before a reviewer opens it, so legal starts from a marked-up view rather than a cold read. The human decision is still entirely the reviewer's.
What do I need to connect?
Slack and Gmail. Slack carries the approval requests to your legal and management reviewers, and Gmail sends the decision notification. Google Chat, Telegram, Discord and Brevo are supported swaps at install.
Can high-value contracts follow a different path?
Yes. high_value_threshold is set at install. Contracts above it get the fuller review path, and you nominate the specific legal and management approvers by their Slack IDs so requests reach a named person rather than a channel.
What happens to a rejected contract?
It is returned rather than silently dropped. The record is updated with the outcome and the submitter is emailed the decision, so a rejection is a visible answer with a trail instead of a request that never came back.
Is there an audit trail?
Every submission opens a row that carries the contract details, the AI risk flags, each approval step and the final decision. That record is the audit trail, and it stays queryable in your workspace after the contract is executed.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.