Lumin Zapier integrationAutomate Lumin with Zapier.
The Lumin Zapier integration follows your signature requests and drops files into Lumin: 5 triggers, 1 action, 0 searches. All five triggers are instant, which changes what the free plan can do for you. Here is how to use them well.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lumin Zapier integration actually does
Lumin is a cloud PDF editor where you edit, share and send documents for signature. Zapier, the service that links your apps without code, listens to the life of each signature request in Lumin and can push new files into it. Five moments to react to, one way in.
Three results come back again and again. A closed deal that moves on by itself: when a contract is signed by every signer, Signature Request Is Fully Approved starts the next step, such as updating your pipeline or telling finance. A stalled request caught early: Signature Request Is Declined and Signature Request Is Cancelled tell you a deal is off before anyone has to chase it. A document that lands in Lumin without a manual upload: Upload File takes a file or a public link from another step and stores it in your account.
Here is the unusual part: every Lumin trigger is instant. Lumin warns Zapier as soon as something happens, so even on the free plan nothing waits for a 15-minute check.
What Zapier does not do for Lumin: it cannot create a signature request, edit a PDF or find an existing document, since the only action is an upload and there is no search. If you also work on another platform, our Lumin Make integration page lists what Make exposes.
Zapier vocabulary in one minute
Seven words you will meet in the editor, each explained once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, like a signature request that gets declined. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or uploads something. Upload File is the one Lumin action.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer set by your plan. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What a Lumin Zap really costs
Lumin is not a premium app: the free plan accepts it. Zapier bills in tasks, and only successful actions count.
- Lumin premium appNo, free plan works
- Lumin triggers5, all instant
- Free plan100 tasks per month
- Cost of a trigger0 task
None of the five triggers costs a task, however many signature requests go through. Each step after the trigger that completes successfully costs one: an Upload File, or an action in another app. A failed action is not counted. The free plan gives 100 tasks a month in two-step Zaps. Since all Lumin triggers are instant, the interval grid below does not apply to them, even on the free plan. The catch is elsewhere: reacting only to some requests means a filter, and a filter makes the Zap multi-step, so paid.
Connect your Lumin account to Zapier
- 01
Add the connection
In Zapier, open Apps and click + Add connection. Type Lumin in the search box of the dialog and pick it from the list of results that comes up under the box.
- 02
Sign in to Lumin
Click Add connection. A new tab opens on Lumin: sign in with the account that sends your signature requests, since the five triggers follow that account.
- 03
Allow access
Grant Zapier access to your Lumin account. The connection then appears in your Apps list and is reused by every Zap that listens to Lumin or uploads into it.
Your first Lumin Zap, step by step
GoalWhen a signature request is fully approved, keep a copy in Lumin, but only for requests whose title mentions a contract.
- 01
Create the Zap and pick the trigger
Create a Zap, choose Lumin and Signature Request Is Fully Approved. Test it: Zapier brings back the three most recent approved requests, so you work on a real one.
- 02
Add the filter
Add a Filter step from the plus icon. Choose a text field from the test record, a text rule and the word contract. The filter makes this a paid, multi-step Zap.
- 03
Add Upload File
Pick Lumin again and Upload File. Give it a file name, then map a field from the test record that holds a file or a public link, if one is there.
- 04
Test the upload
Run the test and open Lumin to see the file. If nothing arrived, the field you mapped was not a file or a public link: pick another one.
- 05
Publish
Click Publish to switch the Zap on. Only requests approved after that moment are handled. Earlier ones stay as they are.
The 5 Lumin triggers
5 events start a Zap when something happens in Lumin, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
New Signature Request Created
Instant triggerIn Zapier“Triggers when a new signature request is created.”
Starts the Zap each time a new signature request is set up in Lumin, before anyone has signed. It marks the beginning of a signing cycle.
Signature Request Is Fully Approved
Instant triggerIn Zapier“Triggers when document has been signed by all signers.”
Runs once every signer has signed the document, and not before. A request with three signers starts the Zap only after the third signature.
Signature Request Is Cancelled
Instant triggerIn Zapier“Triggers when owner cancels the document.”
Fires when the owner of the request cancels the document. It is the sender pulling the plug, not a signer refusing.
Signature Request Is Declined
Instant triggerIn Zapier“Triggers when a signer declines the document.”
Reacts when one of the signers declines the document. The deal is not dead yet, but someone needs to call.
Signature Request Viewed
Instant triggerIn Zapier“Triggers when a signer opens the document .”
Goes off when a signer opens the document. Opening is not signing, but it tells you the document has reached the person.
The Lumin action on Zapier
Lumin gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Upload File
ActionIn Zapier“Upload a file to Lumin.”
Puts a file into your Lumin account from another step of the Zap. It takes a name and the file, sent either as an actual file or as a public URL.
When the Lumin Zap breaks
Zapier links no help article to Lumin and lists no app-specific limit. What breaks comes from the upload rules and from Zapier's general behavior.
On the trigger side, Lumin pushes events to Zapier, so delays are rare. Problems come from what you send to Upload File, and from what you expect the Zap to remember. Our Zapier troubleshooting page covers the general error cases in more depth.
The file type is refused
Upload File accepts PDF, DOCX, PNG, JPG, JPEG, XLSX and PPTX. Anything else, such as a ZIP or a text file, has no place to go.The link is not public
The File field takes an actual file or a public URL. A link that needs a login to open is not public, so Lumin cannot fetch it.Past requests are not replayed
A Zap only reacts to events after it is published. Requests already signed or declined before that stay out; handling them is a separate job.A burst of events is held back
If a large batch arrives at once, after a bulk send for example, Zapier's flood protection can hold the Zap instead of running every item.
Need help automating Lumin with Zapier?
A person reads every message.
