Resources · Make integration

OkaySend Make integrationAutomate OkaySend with Make.

Signed, declined or expired: what should happen next in your other tools? The OkaySend Make integration gives you 16 modules, 14 of them triggers. This guide shows how to link your account, build a first scenario and pick the right module.

Try the OkaySend integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OkaySend Make integration automate?

The OkaySend Make integration links your OkaySend account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Make spots what changes in OkaySend, such as a signature request that gets completed or declined, and passes it to your other apps, or creates clients and sends document requests for you.

Onboarding without retyping. A client record appears in OkaySend, Watch Created Client picks it up, and Send a Document Request asks that client for the files you need. Nobody has to open the request form by hand.

Chasing signatures that stalled. Watch Declined Signature Requests and Watch Expired Signature Requests catch the requests that went nowhere, so a sales rep or account manager can be told in the tool they already read, whatever other app you connect there.

A clean trail of each signer. Watch Signer Signed reacts to each signature, which suits contracts with several people who must sign one after the other.

Know the limits before you start. All 14 triggers are scheduled (Make only lists their names, so the type is read from those): Make asks OkaySend for news on a timer, it does not hear about events the moment they happen. Make also flags its OkaySend documentation as limited, with no description of the modules, so the module names are your main guide and a test run tells you the rest. The Make troubleshooting guide helps when a run fails, and the Make training covers scenario basics step by step. Still weighing tools? The n8n vs Make comparison sets out the criteria.

Connect

How do you connect OkaySend to Make?

  1. 01

    Add an OkaySend module

    Open your scenario, click the + and search for OkaySend. Pick any module, then click Create a connection. A connection is your OkaySend account linked to Make one time, then reused by every OkaySend module you add later.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps once you work with more than one account. Something like the team or the client it belongs to makes the right one easy to spot in the list later on.

  3. 03

    Authorize Make, then save

    Depending on what OkaySend asks, either approve Make on the OkaySend page that opens, or paste the key your OkaySend account gives you. Click Save, and the module can now read your data.

First scenario

Your first scenario with OkaySend

GoalWhen a new client is created in OkaySend, Make sends that client a document request.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + in the middle. That empty circle is where your first module, the one that starts everything, will sit.

  2. 02

    Set the trigger

    Search for OkaySend and choose Watch Created Client. Select your connection, or click Create a connection if this is your first OkaySend module, then fill in the fields Make shows.

  3. 03

    Add the document request

    Click the + on the right of the trigger and add Send a Document Request. Map the client coming from the trigger into it, so each request goes to the person who was just created.

  4. 04

    Test with Run once

    Create a test client in OkaySend, then click Run once. Open the bubble above each module to read the bundles it received, one bundle being one item passed along, here one client.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default; keep that or change it within what your plan allows, then switch the scenario on.

Triggers

Which OkaySend triggers can start a scenario?

14 modules start a scenario when something happens in OkaySend. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by OkaySend as soon as it happens.

OkaySend1Watch Archived Document Requests

Watch Archived Document Requests

triggerIn the docs only

Hands your scenario the document requests someone archived in OkaySend, so a closed file can be closed in your other tools too. Make publishes no description of this module, so its name is the only guide: check the first bundle before you map anything.

How it fires
scheduled. Make checks OkaySend on the scenario's schedule, every 15 minutes by default.
When to use it
your team archives a request once a client file is finished, and a tracking sheet elsewhere should show it as done.
OkaySend2Watch Completed Document Requests

Watch Completed Document Requests

triggerIn the docs only

Lets you act once a client has returned everything a document request asked for, instead of opening OkaySend to find out. This is the natural start for any follow-up that needs the full set of files.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a completed request shows up at the next check.
When to use it
tell the person in charge of the file that it is ready for review, or move the client to the next step of your process.
OkaySend3Watch Completed Signature Requests

Watch Completed Signature Requests

triggerIn the docs only

Gives you a signal once a signature request is fully done, which is what most people mean by a signed contract. Pick it over Watch Signer Signed when only the final state matters to you, not each individual signature.

How it fires
scheduled. Make polls OkaySend on the scenario's timer, 15 minutes apart on the default setting.
When to use it
a signed quote should open a project in your task tool or update the deal stage in your CRM.
OkaySend4Watch Created Client

Watch Created Client

triggerIn the docs only

Starts your scenario with each new client record added in OkaySend, so the rest of your stack learns about that client without anyone copying details across. It is the entry point used in the first scenario above.

How it fires
scheduled. Make asks OkaySend for new clients each time the scenario runs on its schedule.
When to use it
a new client should also exist in your CRM or mailing list, or receive a first document request.
Watch out
if another scenario creates clients with Create a Client, this trigger will see those too.
OkaySend5Watch Declined Signature Requests

Watch Declined Signature Requests

triggerIn the docs only

Surfaces the signature requests a recipient turned down, so a refusal gets a reply instead of sitting unnoticed in OkaySend. Pairing it with a message to the owner of the deal is the usual move.

How it fires
scheduled. Make looks for declined requests on the scenario's schedule rather than being told right away.
When to use it
a declined contract should alert the account manager in your team chat or reopen a task so someone calls the client back.
OkaySend6Watch Expired Signature Requests

Watch Expired Signature Requests

triggerIn the docs only

Catches the signature requests that ran out before anyone signed, the silent failures that are easy to miss. With this module, an expired request turns into a reminder for a human rather than a lost deal.

How it fires
scheduled. Make checks OkaySend whenever the scenario runs, every 15 minutes unless you change it.
When to use it
expired offers should land in a follow-up list, or create a task to resend the request.
OkaySend7Watch Field Completion

Watch Field Completion

triggerIn the docs only

Reacts at a finer level than the whole request: judging by its name, it spots fields your clients fill in. Make gives no detail on which fields it covers, so run it once and look at the bundle before relying on it.

How it fires
scheduled. Make queries OkaySend on the scenario's schedule and returns what changed since the last check.
When to use it
one answer is enough for you to move on, without waiting for the client to finish every other item.
OkaySend8Watch Sent Document Requests

Watch Sent Document Requests

triggerIn the docs only

Keeps a record of every document request that leaves OkaySend, whoever sent it. That gives you one place to see what is out with clients and waiting for an answer.

How it fires
scheduled. Make checks for newly sent requests each time the scenario runs.
When to use it
log each request in a shared sheet, or start a follow-up sequence in your email tool.
Watch out
requests sent by Send a Document Request in another scenario will show up here as well.
OkaySend9Watch Sent Signature Requests

Watch Sent Signature Requests

triggerIn the docs only

Tracks each signature request as it goes out, so your pipeline shows a contract as sent the same day it leaves. Choose it to start a timeline; the completed, declined and expired triggers close that timeline later.

How it fires
scheduled. Make polls OkaySend on the scenario's clock, not at the exact moment of sending.
When to use it
move a deal to a sent stage in your CRM, or add a row to a sheet that lists every contract out for signature.
OkaySend10Watch Signer Signed

Watch Signer Signed

triggerIn the docs only

Follows each person who signs, one signature at a time, instead of waiting for the whole request to close. On a contract with several signers, you see who is done and who is still pending.

How it fires
scheduled. Make checks OkaySend for new signatures on the scenario's schedule.
When to use it
notify the next signer's contact at your company, or record each signature in the client file.
Watch out
each bundle a module processes costs one operation, so several signatures mean several operations.
OkaySend11Watch Updated Client

Watch Updated Client

triggerIn the docs only

Brings client changes made in OkaySend back into your other tools, so an edit made there does not stay trapped in one app. Use it next to Watch Created Client, which only sees new records.

How it fires
scheduled. Make asks OkaySend for updated clients on the scenario's schedule.
When to use it
keep a CRM contact or a billing record in line with the OkaySend client.
Watch out
never update the same client back in OkaySend from this scenario, or it can wake itself up again.
OkaySend12Watch Viewed Signature Requests

Watch Viewed Signature Requests

triggerIn the docs only

Tells you a recipient has opened a signature request, a sign of interest that often comes before the signature itself. It is the right time to be ready for questions from that client.

How it fires
scheduled. Make finds viewed requests when the scenario runs, so the alert comes at the next check.
When to use it
send the sales rep a short message saying the client has the contract open, so the call happens while it is still on the table.
OkaySend13Watch for Field Approval

Watch for Field Approval

triggerIn the docs only

Signals, as its name suggests, that a field submitted by a client was approved on your side in OkaySend. Make documents nothing more, so treat the first test bundle as the real description of what you receive.

How it fires
scheduled. Make checks OkaySend on the scenario's schedule for newly approved fields.
When to use it
an approved item should unlock the next task in your project tool or update a checklist the client can see.
OkaySend14Watch for Field Rejection

Watch for Field Rejection

triggerIn the docs only

Flags a field that was rejected, going by the module's name, so the client can be asked to fix it without delay. It mirrors Watch for Field Approval and suits the corrective path of your process.

How it fires
scheduled. Make looks for rejections each time the scenario runs.
When to use it
a rejected document should create a task for the team member who follows that client.
Watch out
Make publishes no description of this module; test it with Run once before building on it.
Modules

What can OkaySend do inside a scenario?

OkaySend gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

OkaySend1

Create a Client

ActionIn the docs only

Adds a client record to OkaySend from data that lives elsewhere, such as a signed deal in your CRM or a web form entry. Your client list stays complete without anyone typing it twice.

When to use it
a lead becomes a customer in another app and needs to exist in OkaySend before any request goes out.
Watch out
an action works on one bundle, so a batch of contacts creates one client per bundle and uses one operation each.
OkaySend2

Send a Document Request

ActionIn the docs only

Sends a client a document request from OkaySend without opening the app, triggered by whatever event you choose in Make. This is the module that turns an automation into files actually requested.

When to use it
right after a client is created, or once a signature request is completed and you need the paperwork that follows.
Watch out
Make lists no description of its fields; check them in the module before mapping data into them.
Need help

Need help automating OkaySend with Make?

A person reads every message.

FAQ

Questions about the OkaySend Make integration

01Is the OkaySend Make integration free?
Yes, OkaySend is a standard app in Make, available from the Free plan. That plan has real limits though: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits, with a minimum interval of 1 minute and unlimited active scenarios. Make counts usage in credits, one operation being one module run on one bundle. Your OkaySend subscription itself is a separate matter.
02What do you need to connect OkaySend to Make?
An OkaySend account and a Make account are enough to start, since the Make documentation lists no other prerequisite. You add an OkaySend module, click Create a connection, give it a name if you like, then either approve Make on the OkaySend page or paste the key your account provides, and click Save. Make gives no OkaySend-specific connection steps, so those are the generic ones. The connection is created once and every OkaySend module in your scenarios can reuse it.
03Do OkaySend triggers in Make work in real time?
No, as far as the documentation shows. All 14 OkaySend triggers are listed as scheduled, a type read from their names: Make checks OkaySend at the interval set on the scenario, it is not notified by the app when something happens. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. So a signed contract or a new client reaches your other tools at the next check, not the instant it happens. For most follow-up work that delay is fine.
04What if the OkaySend module you need is missing in Make?
It depends on what is missing. OkaySend has no Make an API Call module in Make, so you cannot call its API directly from a scenario. The 16 modules available are 14 triggers plus Create a Client and Send a Document Request. Make also marks its OkaySend documentation as limited. If your need goes beyond that, look at whether another app in your process can do the step, or ask the agency team to review the case with you.
05Should you use Make or n8n for OkaySend?
It depends on the tool you already run. In Make, OkaySend comes with 16 ready modules, mostly scheduled triggers around signatures, document requests and clients, so a first scenario needs no code. The same app often has an n8n node too; check that one exists for OkaySend and what it covers before you choose. Compare the modules each side offers for your exact workflow, then pick the tool your team will actually maintain. There is no single right answer for every team.
Same platform

Other docs you might need on this stack.

Browse all integrations