Most NDAs are routine, and the routine ones delay the rest
NDAs arrive constantly and mostly say the same things. They queue behind each other, and a deal waits three days for a document that matches your template almost exactly.
The flow addresses the queue rather than the review. A document that aligns with your accepted positions is sent to the existing delegation. One that does not is sent to a reviewer with the specific reason for the flag.
The important clauses are identified in advance: the length of the term, the definition of confidential information, whether the obligations last indefinitely, the presence of any embedded non-solicit or non-compete clauses, the choice of governing law, and the carve-outs that you require.
The flow never concludes that an NDA is acceptable. It only specifies which band a document belongs to according to your criteria. Signing authority remains exactly where your delegation has placed it.
How the ActionFlow runs on the canvas
The banding criteria are stored in an Airtable node. That table specifies which positions place a document in each band, and which band may proceed under the existing delegation.
The Email node reads the legal inbox, or the Webhook trigger picks up the submission. Document Upload with PDF4me extracts the document.
The Generate Object node examines each criterion and, for each one, returns the position identified, the text of the clause, and whether it is within your accepted range.
The Math node counts the checks that are outside the specified range. The If node applies the banding rules from the table rather than from the flow, so a legal lead can change the thresholds without changing the canvas.
A Switch node routes by band. Documents in the clear band are sent to the requester with a note that lists which checks ran. All the rest go to a Slack node in the Human in the Loop category, with the failing checks and clause text.
Any agreement that includes a non-solicit clause, a non-compete clause, or an indefinite obligation is sent to a reviewer, regardless of band, because those provisions have effects that extend beyond the immediate agreement.
Each classification is recorded in a Google Sheets node as the audit trail, with the band and the reason for it.
Nodes this ActionFlow uses
- Airtable (Integration): holds the banding criteria and which band may proceed under delegation.
- Email (Communication): reads the legal inbox. Webhook receives direct submissions.
- PDF4me (Data): extracts the document contents.
- Generate Object (AI Core): returns position, clause text, and in-range flag per criterion.
- Math (Util) plus If (Control): apply banding from the table rather than from the flow.
- Switch (Control): routes by band, with named clause types always going to a reviewer.
- Slack (Human in the Loop): carries flagged documents with the failing checks attached.
- Google Sheets (Integration): logs every classification as the audit trail.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.