Lumin Make integrationAutomate Lumin with Make.
What happens after someone signs, declines or opens a Lumin document? The Lumin Make integration gives you 7 modules: 5 instant triggers on signature requests and 2 actions. This guide is for teams that send documents for signature, and it walks you through the connection and a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Lumin Make integration do for you?
The Lumin Make integration lets Make react to your signature requests and push files into Lumin, with no code. A scenario (the automation you build in Make) starts the moment Lumin reports an event, such as a request that every signer has approved, then passes the details to the next step.
Close the deal record once the last signature lands. Watch Fully Approved Signature Request fires when all signers are done, so a sales team can update its CRM or tell the account manager without checking Lumin by hand.
Follow up on refusals right away. Watch Declined Signature Request and Watch Cancelled Signature Request flag the requests that will not close. A legal or HR team can route them to whoever owns the document and fix the wording before sending it again.
Feed Lumin with the files that arrive elsewhere. Upload a Document places a file into Lumin from another app of the scenario, for example a quote generated by a form tool, so it is ready to be sent for signature.
Know the limits before you build. Make's own documentation for Lumin is limited, because little public information exists about the app, so field details are thin. When a listed module falls short, Make an API Call reaches the rest of the Lumin API with the same connection. If you are also looking at n8n, the n8n vs Make comparison sets the two side by side, the Make pricing page explains plans, and the Make training covers scenario building from scratch.
How do you connect Lumin to Make?
- 01
Add a Lumin module
In a scenario, add any Lumin module, then click Create a connection. A connection is your Lumin account linked to Make once, and every Lumin module of your scenarios reuses it afterwards.
- 02
Name it and authorize
Give the connection a name if you manage several Lumin accounts. Then follow what Lumin asks: either authorize Make on the Lumin page that opens, or paste the key Lumin gives you.
- 03
Save and check the module
Click Save. The Lumin module now shows your account, and you can fill its settings. The same connection then appears in every other Lumin module you add later.
Your first scenario with Lumin
GoalWhen a new quote file lands in your cloud storage, Make uploads it to Lumin so it is ready for signature.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. That first module decides when the whole scenario starts.
- 02
Start from your storage app
Pick the trigger of the app where your quotes are saved, such as a module that watches a folder, and connect that account. Lumin comes in at the next step.
- 03
Add Upload a Document
Click the + on the right, search for Lumin, choose Upload a Document and click Create a connection. Then map the file sent by the first module into it.
- 04
Test with Run once
Click Run once after dropping a test file in the folder. Each module shows the bundle it received, one item passed from a module to the next, so you can check the file reached Lumin.
- 05
Schedule and switch it on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each new quote now ends up in Lumin without a manual upload.
Lumin triggers in Make
5 modules start a scenario when something happens in Lumin. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Lumin as soon as it happens.
Watch Cancelled Signature Request
Instant triggerIn Make“Triggers when owner cancels the document.”
You learn the moment the owner of a document calls off its signature request, so nobody keeps waiting on a contract that was withdrawn. The scenario receives the cancelled request and can tell the people involved.
Watch Declined Signature Request
Instant triggerIn Make“Triggers when a signer declines the document.”
This trigger tells you when a signer refuses to sign, which is usually the signal that someone needs to pick up the phone. Your scenario gets the declined request and can route it to the right owner.
Watch Fully Approved Signature Request
Instant triggerIn Make“Triggers when document has been signed by all signers.”
This trigger waits until every signer has signed, so your next step always runs on a finished document. The scenario receives the completed request, ready to be logged or shared.
Watch New Signature Request
Instant triggerIn Make“Triggers when a new signature request is created.”
Every new signature request becomes a record you can keep, without anyone copying it by hand. The scenario starts as soon as a request is created in Lumin and hands its details to the next module.
Watch Signer Viewed Signature Request
Instant triggerIn Make“Triggers when a signer opens the document.”
You see when a signer actually opens the document, which turns silence into a useful signal for timing a follow-up. The scenario starts with the request that was just viewed.
Lumin actions in Make
Lumin gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This module reaches any part of the Lumin API that the other modules leave out, using the connection you already created. It is your way around the short module list.
Upload a Document
ActionIn Make“Uploads a file to Lumin.”
Upload a Document puts a file into Lumin from an earlier step of the scenario, so it is there when you need to send it for signature. The file usually comes from another app, like a form tool or cloud storage.
Need help automating Lumin with Make?
A person reads every message.
