Resources · Zapier integration

Openum by Lleida.net Zapier integrationAutomate Openum by Lleida.net with Zapier.

The Openum by Lleida.net Zapier integration gives you 1 action, 0 triggers and 0 searches. Start Openum Signature takes a PDF from another app and opens a delivery process with its recipients. Something else has to start the Zap.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Openum by Lleida.net Zapier integration does

Openum by Lleida.net is an online service for sending documents as a registered delivery, with legal weight behind it. On Zapier it becomes one step: your automation hands it a PDF, a file name and a reference, and Openum starts the delivery to the recipients. The event that kicks things off has to come from another app.

Three outcomes people build with it, all on the same Start Openum Signature step. A contract sent once it is filed: a signed-off PDF lands in a shared folder and goes out to the client without anyone opening Openum. A formal notice from your CRM: a deal reaches a given stage, the generated PDF is picked up and sent with the deal number as reference. A traceable batch of documents: each PDF produced by your document tool leaves with its own reference, so you can find it later in Openum.

The reference field is the quiet star here. Openum uses it as the unique identifier of each delivery, so map it from something that changes every time, a contract number, a deal ID, a file ID, never from fixed text.

What Zapier does not do with Openum. There is no trigger, so a Zap cannot react to a delivery being opened, accepted or finished. There is no search step, so a Zap cannot check the status of a past delivery either. Data flows one way: into Openum, never back out. And the action only takes PDFs.

For a wider view of the tool, see our Zapier review or the comparison n8n vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Eight terms you will meet in the editor. They are used afterwards without a second explanation.

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 in an app that starts the Zap. With Openum, that event always comes from another app, such as a new file.
Action
What the Zap does once started: the step that writes, sends or moves something for you. Start Openum Signature is one.
Task
The unit Zapier bills. Every action your Zap completes successfully counts as one task on your plan.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant one is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app so later steps can use it. Openum has none on Zapier.
Connection
Your Openum account linked to Zapier once, then reused by every Openum step in every Zap you build.
Cost

What each Openum delivery costs on Zapier

Zapier bills tasks, and only actions that go through count.

  • Free plan100 tasks a month, two-step Zaps
  • Start Openum Signature1 task per successful run
  • Trigger and checksNever billed
  • Premium appNo

The trigger in the other app is free, and so are Zapier's checks on it. Each Start Openum Signature that succeeds is one task; one that fails is not counted. Add a step after it, a Slack message for instance, and that one counts too. Openum is not a premium app, so the free plan is enough: 100 tasks a month, two-step Zaps only. A filter, a search or a second action makes the Zap multi-step, which needs a paid plan.

Connect

Connect Openum by Lleida.net to Zapier in three steps

  1. 01

    Open your apps

    In Zapier, go to the Apps page of your account. You need an Openum account first, plus access to any document or folder you do not own but want the Zap to use.

  2. 02

    Add Openum

    Click + Add connection, type Openum by Lleida.net in the search box of the dialog that opens and select it. Confirm with Add connection to start signing in.

  3. 03

    Sign in and allow access

    A tab opens on Openum. Sign in and grant Zapier access to the account. The connection then shows up in your list, ready for every Zap that sends through Openum.

First Zap

Your first Zap: PDFs from a folder sent through Openum

GoalEach PDF saved in one Drive folder goes out as an Openum delivery, but only if it really is a PDF.

  1. 01

    Set the starting event

    Create a Zap and pick the app and event that start it, here a new file in a folder. Testing brings back the three most recent files so you map from a real one.

  2. 02

    Add a filter

    Add a Filter step: the field to check, the rule, the value. A text rule only works on text. With a filter, the Zap is multi-step and needs a paid plan.

  3. 03

    Add Start Openum Signature

    Choose Openum by Lleida.net as the action, then Start Openum Signature and your connection. Map the file and its name from the Drive step.

  4. 04

    Set a unique reference

    In the delivery reference, map a value that changes with each file, such as the file ID. Openum uses it as the delivery's unique identifier, so fixed text is a bad idea.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When the test delivery looks right, publish the Zap to switch it on.

Actions

The Openum by Lleida.net action on Zapier

Openum by Lleida.net gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Start Openum Signature

Action

In Zapier“Initiates a delivery process with the recipient/ies, to deliver the supplied document”

Opens an Openum delivery process for the PDF you pass in, so the document reaches its recipients through Openum with your reference attached.

When to use it
a landlord's office wants each lease, once exported as a PDF, sent to the tenant without retyping anything.
Watch out
the file must be a PDF and the reference must be unique, so map both from the previous step rather than typing them.
When it breaks

When an Openum Zap breaks

Zapier ties no help article to Openum by Lleida.net, so these are the general traps that hit any Zap built around this action.

Most failures start one step earlier, with the file that arrives. For a methodical check, the Zapier troubleshooting page goes through the usual causes.

  • Old documents are not sent

    A Zap only reacts to what happens after you switch it on. Files already sitting in the folder will not go out through Openum; that backlog is a separate job.

  • A loop through your folders

    If a later step saves a copy back into the folder the trigger watches, the Zap fires on its own output again and again and eats your tasks.

  • A bulk upload gets held back

    Dropping a large batch of files at once can make the trigger return a huge set. Zapier's flood protection may hold it back rather than send everything.

  • No file is sent twice

    On a polling trigger, Zapier remembers what it has already seen, so the same file does not start a second delivery.
Need help

Need help automating Openum by Lleida.net with Zapier?

A person reads every message.

FAQ

Openum by Lleida.net Zapier integration: frequent questions

01Is the Openum by Lleida.net Zapier integration free?
Yes, on the Zapier side. Openum by Lleida.net is not a premium app, so it works on the free plan. That plan gives 100 tasks a month and builds two-step Zaps only: a trigger from another app, then Start Openum Signature. Adding a filter, for example to keep only PDFs, or a second action makes the Zap multi-step, and that needs a paid plan. Zapier's checks on the trigger app never cost a task, so a month without new documents costs nothing on that side.
02How many tasks does an Openum delivery use?
One per successful run. Each time Start Openum Signature completes, Zapier counts one task. The trigger that started the Zap is free, and so are Zapier's checks for new items. A run that fails is not counted. If you add another action after Openum, for example a message to the team, each successful action counts on its own, so that Zap uses two tasks per document. Size your plan on the number of documents you expect to send each month.
03Does Openum by Lleida.net work in real time with Zapier?
That depends on the app that starts the Zap, since Openum has no trigger. If that app has an instant trigger, it tells Zapier straight away and the plan interval does not apply. If it uses a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Once the Zap has started, Start Openum Signature runs as the next step, so the delay to watch is the trigger's.
04What does it take to connect Openum by Lleida.net to Zapier?
An Openum account, plus access to any document or folder you do not own but want the Zap to use. From the Apps page in Zapier, click + Add connection, search for Openum by Lleida.net, confirm with Add connection, then sign in to Openum in the tab that opens and grant access. The connection is saved once and every Zap that sends through Openum reuses it, so there is nothing to redo for the next automation you build.
05Why does Start Openum Signature reject a file?
Check the PDF rule first. Both File name and File to send must point to a PDF, and the delivery reference is required too. If the app that starts the Zap produces Word files or images, the step has nothing valid to send. Convert the document upstream, or add a filter that only lets PDFs through, keeping in mind that a filter makes the Zap multi-step. Then check that the reference is mapped and not left empty.
06What if the Openum operation you need is not on Zapier?
Then this integration does not offer it today. Zapier shows one visible operation for Openum by Lleida.net: Start Openum Signature. There is no trigger to react to a finished delivery and no search to read its status. If you need that information back in another tool, the Zap cannot fetch it; follow up in Openum itself. Check the app page on Zapier before you design a flow, since that list is exactly what the editor will offer you.
07Zapier, Make or n8n for Openum by Lleida.net?
Choose on criteria rather than a ranking. On Zapier, Openum only receives documents, through one action, and a two-step Zap fits the free plan. So ask yourself: do you only need to send PDFs, or also to react when a delivery is completed? How many documents a month, and how many steps per document? Do your files arrive as PDFs already, or do they need a conversion step first? Answer those, then compare each tool on the same points.
Same platform

Other docs you might need on this stack.

Browse all integrations