Does fynk read my email?

No. Your email connector reads the mailbox and returns the content to the assistant. fynk only receives the values the assistant extracted, and only when it creates the document.

Which AI clients can I use?

Any client that supports MCP. The steps are the same in each one, only the connector screen looks different.

Do I need a fynk API key?

No. The MCP connection uses your normal fynk login and your existing permissions. API keys are only needed for automation platforms like Zapier.

What happens if the email does not mention something?

The assistant leaves the field empty and tells you. Mark anything that must not be guessed as mandatory with no default in your template, and you get a flag instead of a guess.

Can it send the document for signature straight away?

Yes, if you ask it to. We recommend leaving it in draft for anything that came from an unstructured source, so a person checks the extraction before it reaches a counterparty.

Which fields does fynk fill automatically?

For each party, fynk already handles first and last name, title and position, address, company name and signatory email. You only need dynamic fields for anything beyond those.

How to draft an NDA from an incoming email

The goal

Turn an inbound email and its attachment into a ready-to-review contract in fynk, without leaving your AI chat and without retyping a single detail.

Connect fynk and your mailbox to the same AI client
Ask the AI agent to read the email and draft the document
Review the draft in fynk and send it when you are ready

Step 1

Connect fynk and your mailbox to your AI client

Three tools share this job:

Your email connector: reads the inbox and extracts the text of the attachment.
The AI assistant: works out which value is the registered legal name, which is the signer, and what is missing.
The fynk MCP : looks up your template and creates the document.

To start, connect fynk MCP and your inbox (Microsoft 365 or Gmail) to AI agent of choice.

Your AI then:

Fetches the NDA template in fynk to see what information should be filled.
reads the email you mentioned to extracts the information,
Maps out the data between the two to create a new NDA for you.

Good to know: fynk never reads your emails.

MCP is the open standard that lets an AI client talk to tools like fynk and your mailbox directly, so you describe the outcome instead of copying data between tabs. The MCP server page lists everything fynk exposes.

When the input is always the same. A form asks the same questions every time, so an automation maps each answer to a field once and then runs on its own, which is what our guide on creating an NDA from a form sets up.

The MCP page in fynk account settings, showing MCP enabled and the AI clients connected by the organization

Step 2

Set up your NDA as a template in fynk

Import your NDA into fynk or create a new template in the editor. Your template should have:

dynamic fields : for everything that changes per deal like governing law, or confidentiality period.
Parties and signatories: one would be you and another is recipient.
Signature blocks per signer.

Then publish it.

Start from one of fynk’s ready-made templates, Mutual NDA or Non-disclosure agreement , and adjust the fields to what your counterparties usually tell you. Both already include the most common ones. The help center covers building a template .

Dynamic fields, parties and signatories in a published fynk NDA template

Step 3

Ask AI to create the NDA

Describe what you want in plain language, here’s an example:

Read the latest email from [sender name] about the NDA. Pull out the counterparty's legal name, the signer's name and email, and any term details they mention, including anything in the attachment. Then create a document in fynk from my [template name] template, fill those in, add the signer as signatory, and leave it in draft for me to review.

It names the source rather than the values, says to check the attachment, and asks for a draft. The registered legal name and the signer’s exact title usually sit in the attachment.

The assistant then reads the email and its attachment, looks up your template to see which fields it needs, states back what it extracted, creates the document, and attaches the signer to the right party.

If you missed something, your AI agent will ask for it or reports it to you.

What makes it fast?

No copying between inbox and contract tool
Details from the attachment, not just the email
Missing information flagged, not invented
One prompt instead of a mapping table

"I copied the email into fynk and asked the assistant whether what we'd agreed was actually legally binding. It went through the clauses and flagged that these confirmations needed signatures from both sides. Something I would most likely have overlooked otherwise."

Ariste Baumberger CEO of Honegger

YOU'LL ALSO LIKE

Read all

Smart templates

Fill once. Reuse everywhere.

See all templates

Mutual NDA

Non-disclosure (NDA)

Confidentiality

Vendor service

Consulting

MSA

Frequently asked questions.

No. Your email connector reads the mailbox and returns the content to the assistant. fynk only receives the values the assistant extracted, and only when it creates the document.
Any client that supports MCP. The steps are the same in each one, only the connector screen looks different.
No. The MCP connection uses your normal fynk login and your existing permissions. API keys are only needed for automation platforms like Zapier.
The assistant leaves the field empty and tells you. Mark anything that must not be guessed as mandatory with no default in your template, and you get a flag instead of a guess.
Yes, if you ask it to. We recommend leaving it in draft for anything that came from an unstructured source, so a person checks the extraction before it reaches a counterparty.
For each party, fynk already handles first and last name, title and position, address, company name and signatory email. You only need dynamic fields for anything beyond those.