Contract intake
Typeform requests become Notion matters and Slack pings.
FOR LEGAL TEAMS
Contracts move without the inbox chase
Intake forms, approval threads, renewal dates, and NDAs scatter across email and shared drives. WEXTL routes requests, logs decisions, and nudges owners before dates slip — on a canvas counsel can audit.
Deploys this workflow into your workspace — you'll connect your own accounts.
Legal intake workflow from Typeform to Notion and Slack
- GDPR
- Data Encryption
- 2FA
- Local Data Region
* Illustrative example, not measured customer data.
Legal automation, at a glance
Approval routing
Email attachments branch by value and wait for sign-off.
Renewal tracking
Notion renewal pages trigger reminders before expiry.
NDA tracking
NDA submissions land in Airtable with owner alerts.
Legal ops with an audit trail
Contract requests that land in one place
Watch Typeform submissions, create Notion pages, notify legal Slack.
- Trigger — a contract request is submitted through the Typeform intake form, or forwarded to the legal intake alias in Gmail.
- Information collected — requester, counterparty name, contract type (MSA, SOW, DPA, NDA), estimated value, and any deadline.
- Connected applications — Typeform for the intake form, Gmail for forwarded requests, Notion for the matter page, Slack for the legal team channel.
- Decision logic — contract type picks the right matter template and queue (procurement-side, sales-side, or vendor); missing counterparty or value routes to hold instead of opening a matter.
- AI step — classifies the contract type and extracts counterparty, value, and term length from an attached draft when one is included.
- Human approval — none required to open a matter page; an owner is assigned automatically based on contract type and value, reassignable by the legal team.
- Actions — creates a Notion matter page pre-filled from the intake fields, posts a link to the legal Slack channel, and assigns an owner.
- Exception handling — a request missing counterparty or value is held and sent back to the requester with what's missing, instead of opening an incomplete matter.
Legal intake workflow from Typeform to Notion and Slack
What legal ops actually fights all day
None of it is legal work. A contract sits in a shared inbox for two days because nobody's sure whose queue it's in. An approval thread balloons to six people cc'd because nobody's sure who has signing authority, and it stalls the moment the one person who could approve it steps into a client meeting. A renewal auto-fires because the opt-out deadline was a date buried in a PDF footer nobody was re-reading.
- Step 1
Contracts stuck in a shared inbox
No one owns the queue, so nothing moves until someone happens to check.
- Step 2
Approval threads with six people cc'd
Nobody's sure who has signing authority, so everyone gets looped in just in case.
- Step 3
Auto-renewal dates buried in a footer
The clause that mattered was on page 14, and nobody re-reads page 14.
None of it needs a law degree. All of it needs someone paying attention to a queue or a date.
Example: automate contract approval routing
A concrete run, start to finish — the kind of approval workflow a legal ops team clones from the template library and tunes to its own value thresholds and playbook.
Trigger: a contract needing sign-off is forwarded to the legal intake alias, or a Notion matter's status changes to “Ready for review.”
WEXTL checks: the contract's dollar value against saved threshold tiers, whether any clause (indemnification, liability cap, auto-renewal without a notice window) falls outside the standard playbook, the counterparty's risk flag, and who the assigned approver is for that department.
Human judgment
Whether a flagged clause is actually acceptable, and any exception to the playbook, is a legal call — the workflow flags and routes, it never approves a contract itself.
- Step 1
1. Contract arrives
A forwarded email or a matter status change starts the run.
- Step 2
2. Check the tier and scan for nonstandard clauses
Compares contract value against saved thresholds, and flags indemnification, liability, or auto-renewal language that falls outside the playbook.
- Step 3
3. AI drafts the summary
Pulls the flagged clauses and value into a one-paragraph approval request.
- Step 4
4. Route to the right approver
Sends to the department head, Finance, or the GC alias based on the tier and any clause flag.
- Step 5
5. Wait for a decision, escalate on silence
Pauses on the assigned approver's reply in Slack or email; no response inside the SLA window forwards to the alternate approver or GC automatically.
- Step 6
6. Send for signature and log the run
An approved contract routes straight to e-signature, and every check, route, and decision is recorded for the approval record.
Step 1
1. Scheduled check runs
Compares every contract's end date against today, on a set cadence.
Step 2
2. Flag auto-renewal risk
Separates contracts with an open opt-out window from ones simply approaching their end date.
Step 3
3. Filter to the reminder windows
Surfaces anything inside 90, 60, or 30 days out.
Step 4
4. Draft the reminder
AI summarizes the contract terms, renewal value, and the deadline to decide by.
Step 5
5. Notify the owner
Sends the reminder to the contract's assigned owner, not a shared inbox.
Step 6
6. Log the row, and ping legal for anything inside 30 days
Adds the contract to the rolling renewal tracking sheet, and anything that close gets posted to the legal Slack channel, not just emailed.
Example: automate contract renewal tracking
The same logic, applied to renewals: catch the notice-period deadline before it passes, not after.
Trigger: a scheduled check runs against the contract register and compares today's date to each contract's end date and notice-period deadline.
WEXTL checks: whether the contract has an auto-renewal clause and, if so, whether its opt-out window is still open; the contract's owner and renewal value; and whether it falls inside the 90/60/30-day reminder windows.
Human judgment
Renew, renegotiate, or let it lapse is a decision for the contract owner and legal — the workflow surfaces the deadline with enough lead time, it doesn't decide the contract's fate.
Who legal workflow automation is for
Not every legal function needs this on day one. It's built for the parts of the job that repeat across a lot of contracts, a lot of counterparties, or a lot of departments asking for sign-off.
In-house counsel handling high contract volume
— The same intake and approval logic runs per contract, not once.Contracts managers and specialists
— Templates, thresholds, and routing rules they maintain without engineering help.Legal ops teams supporting several departments
— Sales, procurement, and HR all send contracts through the same intake, each hitting the right queue.General counsel and deputy GCs
— Escalation only reaches them for the value tier or clause type they've actually asked to see.Paralegals tracking NDAs and renewals
— A register that flags what's due instead of a spreadsheet someone has to remember to open.Procurement-adjacent legal reviewers
— Vendor contracts routed by risk flag before they reach the negotiating table.
WEXTL is not trying to be outside counsel or a CLM's redlining tool — it handles the routing, tracking, and reminding so legal spends its time on the clauses and decisions that actually need a law degree.
Connect the contract tools legal already uses
Legal doesn't pick its own tools in a vacuum — the CLM, the e-signature platform, and the intake form are usually already decided. Whatever gets automated has to meet them where they are.
These are the integrations most Legal workflows actually use. An HTTP step reaches a CLM or e-signature API without a native connector.
Developer Tools
- OneflowContract lifecycle platform — creation, redlining, and signature status feed the matter page directly.
- FynkContract lifecycle management for teams standardized on Fynk instead of Oneflow.
- DocumensoOpen-source e-signature for teams that need signing without a per-seat vendor lock-in.
- SigneasyEnvelope and template-based e-signature for standard NDAs and routine agreements.
- NotionMatter pages and the contract register, built from your own template.
Sales
See the full catalog — every app we support, plus an HTTP step for anything else.Explore all WEXTL integrations
25+ apps for Legal
Integrate Legal workflows with the tools your team already uses.
Supported integrations
Legal ops, by hand vs. with WEXTL
| Task | By hand | With WEXTL |
|---|---|---|
Contract intake | Email forwards and lost attachments | Supported |
Approvals | Ad hoc email chains | Policy routes with wait steps |
Renewals | Calendar reminders per lawyer | Supported |
NDA tracking | Shared folder chaos | Structured records + alerts |
Frequently asked questions
No. WEXTL routes, tracks, and reminds around your CLM or Word/Google Docs redlining — it doesn't rewrite clause language. Connect GitLaw's AI agent if you want an AI-drafted redline suggestion, but that draft comes back as a document for a human to accept, never applied automatically.
Two things, not just dollar value: the saved value-tier thresholds (auto-clear, department head, Finance, GC), and a separate scan for clause types — uncapped liability, indemnification outside policy, auto-renewal without a notice window — that force GC review regardless of the tier.
A wait step pauses for their decision in Slack or email. No response inside the SLA window you set escalates automatically to the alternate approver or the GC alias — it doesn't sit in an inbox until someone remembers to follow up.
Yes. The renewal check separates contracts that have an open auto-renewal opt-out window — where missing the date locks you into another term — from contracts simply approaching their end date, and flags the auto-renewal risk earlier.
The counterparty name from the intake form is matched against the NDA register before a new record opens. A match gets flagged for review as a possible duplicate instead of quietly creating a second NDA for the same counterparty.
Each step — who was notified, what tier or clause flag triggered the route, when the approval or signature landed — is recorded per contract, so the answer doesn't depend on reconstructing an email thread.
Oneflow and Fynk for contract lifecycle management, PandaDoc, Documenso, Signeasy, SignWell, and Yousign for e-signature, and GitLaw for AI-assisted drafting and review. An HTTP step reaches a CLM or e-signature API that isn't natively connected.
Clone contract-intake or approval-route from the Legal solution and connect your intake form plus Slack and an e-signature tool first — those two workflows compound: the matter page intake creates also feeds the approval route's contract-type and value fields.
Start automating with Legal or browse more workflows
Start automatingDrop this workflow into your WEXTL workspace and connect your own accounts.
Browse solutions & templatesExplore team solutions and ready-made workflow templates.