Create NDA contracts from a Slack message | fynk

Create and send NDAs for signing directly from Slack

With fynk, Slack and Zapier, a structured Slack message turns into a ready to sign contract on its own. Nobody opens the template or types the same details twice.

Video transcript

Click any line to jump there

Hi and welcome.In this video I'll show you howto create and send an NDA forsignature directly from Slack.To set up this automationyou need fynk, Slack,and Zapier to glue these togetherusing a zap.Let's start by creatingyour NDA template in fynk.open fynk and click on thisbutton to create a new template.I'll give it a name and createit and just paste my text here.

Now I have to createtwo parties for my NDA.One would be the recipientand the other my company.So let's go to the partiesand signatories tab.First I add the recipient.Just give it a namelike recipient and save.And now I add another party which ismy company as the internal party.And I choose this user tobe the signatory as well.By adding a signatory,you can also add the signature blockat the end of document by clickingthis button.

And if we go back to the documentcontent, we can see that two setsof new fields have been createdby fynk.These are the name, address,and signature blocks of each party.So I just drag the signature blockof the recipient and place itnext to my own signature block.Then what I'm going to do is toreplace these static placeholderswith the fields that I just created.

I'm just gonna change the name andaddress of each partywith these fields.

Since I have other placeholders thatI need to fill with the Slackmessage that I’ll be sending, I'mgoing to create a dynamic fieldfor each of these values.For example, for the email address,job title,and of course for the restrictionperiod.

Our template is now complete andall we have to do is to publish it.

Now we have everything that we needto set up the automation in Zapier.But before we do that,I need to explain something aboutthe message that you sent in theSlack.So as we saw in the NDA templates,we need several piecesof information that theautomation can collectfrom our Slack message.In this example, we need seven values,the person's first name,family name, address, job title,company name,and the confidentialityrestriction period.And of course their email address.But here's the important thing.You should always keep thevalues in the same order.For example, if you write theemail address and then nameand family name, in the nextmessage you shouldkeep the same order.So you cannot first add thename and then email address.This is important because the Zapierdoesn't read the message and workout what each line means, itsimply counts the lines, separates it, andthen map out each ofthese values with aspecific dynamic field thatwe just created in theTemplate.So long story short, always keepthe same order for your information.It's time to build the Zap.Open Zapier and click onCreate to start a new Zap.

The first step is the trigger.This tells Zapier when tostart the automation.

Search for a Slack and select it.For the trigger event chooseNew Message Posted to Channel.Then make sure that yourSlack account is connected.Next, in the Configure page,choose the channel thatwill receive this request.I've created dedicated channelcalled NDA so I select that one.Because this channel onlyhandles NDA requests,every new message can start theautomation.So make sure that you use thatchannel only for this purposeor if you use it for anyother purposes as well,make sure that you create afilter at the next step so thatonly the messages with the specialword or any other filter get through.Before testing the trigger,post an example request of yourmessage in the Slack channel using theThe format that I described to you.

So our next step is to split thatblock of text into seven separatevalues.So in the next step

Choose formatter and as anaction event choose text.In the next window we haveto choose split text here.

We can now choose our input fromthe previous step, which is text.So I just search for textand choose this one.

As a separator, you can useanything you like,for example comma, buthere I'm going to use thenew line and put it betweena bracket and a column.And finally as a segmentindex choose the last option.which is all as separate fields.

Then we hit continue and test it.You should now see severalseparate results in the sameorder as your originalSlack message.Now that we have all the values asseparate fields,we can now map the partydetails.Add a new step and choosefynk as the action app.As an action event,choose Create Document from Template.Make sure your account isconnected and in the next step

Choose a name for your document.You can choose something like NDA andthen from the previous step choose thefamily name of the recipient.Then choose the template that youhave in fynk, in my case is NDAs.And as you do,all of the fields that need tobe mapped out will appear here.And if you scroll down here,you can see the dynamicfields that we created.And now I'm going to choosefrom the previous step thecorrect value for each of these.

So I just go aheadand map these fields.And at the very end,you have this option to move yourdocument to the signing stage.Now we have to test whetherthis automation works or not.So I just test it out.Now if I open my fynk,you can see the new NDAin my account set onsigning already, which means it'snow safe to publish our Zap.

Now that our Zap is up and running,let's try the completeworkflow once again.So return to the NDAchannel in the Slack.I send a new message using new valuesbut with the same order that we used.Now if we go back to fynkafter a few seconds we shouldbe able to see the newNDA.Here's my new NDA completely createdonly by a message to a Slack channel.You can also adapt this setupto other types of contracts.Choose a different template andthe same workflow could createemployment offers, freelanceragreements, or vendor contracts.Thanks for watching and I'llsee you in the next video.

The goal

Send an NDA for signature by posting one message in Slack. Zapier reads the message, splits it into the values your template needs, and fynk creates the document and moves it straight to signing.

Step 1

Prepare your NDA template in fynk

Create a new template in fynk and paste in your NDA text. Then:

  1. Add two parties: the recipient, and your own company as the internal party.
  2. Pick the user who signs on your side and add the signature blocks to the end of the document.
  3. Replace the static details in your text, such as the recipient’s name and address, with the party fields fynk created for you.

Anything else the Slack message should carry needs its own dynamic field:

Publish the template so Zapier can use it.

Agree on the message format

Pick a Slack channel for NDA requests and decide what each message contains. One value per line, always in the same order:

  1. First name
  2. Family name
  3. Address
  4. Job title
  5. Company name
  6. Restriction period
  7. Email address

The order is the whole trick. Zapier never reads a line to work out what it means, it maps line one to the first field, line two to the second, and so on. Swap two lines and every value lands in the wrong place.

Build the Zap

Open Zapier, click Create, and build three steps:

  1. Slack: New Message Posted to Channel. Connect your Slack account and pick the channel. Post one example request there before you test, so Zapier has something real to read.
  2. Formatter by Zapier: Split Text. Take the text from the trigger, use the new line as the separator, and set the segment index to “All as separate fields”. Testing it should return your seven values, in order.
  3. fynk: Create Document From Template. Name the document, for example “NDA” plus the recipient’s family name, then pick your template. Map each split value to the matching party field or dynamic field, and switch on Move to Signing Stage.

What if the channel is used for other things too?

Add a filter step straight after the trigger and let the Zap continue only when the message matches, for example when it contains a keyword you agree on. Everything else stops there and never reaches fynk.

Where to find your fynk connection

If your fynk account is not connected to Zapier yet, open Settings in fynk, go to API integrations, choose fynk API, and create a token to paste into Zapier. If you don’t see that option, your account owner can create the token for you.

Test it, then send one from Slack

Test the fynk step and open fynk. The NDA should be sitting in the signing stage with the values from your example message. Check that each field picked up the right line, then publish the Zap and switch it on.

Now post a real request in the channel. A few seconds later the NDA is in fynk, filled in and on its way to the recipient, and you can follow it with signature tracking. Nobody opened the template or typed anything twice.

What makes it fast?

Frequently asked questions.

Because Zapier splits the message by line and maps line one to the first field, line two to the second, and so on. It never works out what a line means. Change the order and every value lands in the wrong field.

Yes, but add a filter step right after the trigger so only real requests continue, for example messages containing an agreed keyword. A dedicated channel is simpler if you can have one.

Only if you switch on Move to Signing Stage in the fynk step. Leave it off and the document waits in draft in fynk, so someone can check it before it reaches the recipient.

No. The Zap runs on your fynk connection, so colleagues only need access to the Slack channel. That is what makes this work for teams outside Legal.

Yes. You connect fynk to Zapier with a token from Settings, API integrations, fynk API. If you don't see that option, your account owner can create one for you.

Yes. The workflow does not care what the template is. Point the fynk step at a different template, match the message format to its fields, and the same Zap creates employment offers, freelancer agreements, or vendor contracts.

The split step returns fewer values than the mapping expects, so the run fails or a field stays empty. Zap History in Zapier shows what came through, and the fix is always the message rather than the Zap.

Yes. Only the trigger changes. Swap Slack for Microsoft Teams in the first step and keep the formatter and fynk steps exactly as they are.