Resources · Zapier integration

LicitaLab Zapier integrationAutomate LicitaLab with Zapier.

LicitaLab Zapier integration: 8 triggers, 0 actions, 0 searches. Every trigger is instant: LicitaLab tells Zapier as soon as something moves on a tender you follow or a purchase order arrives. Zapier cannot write anything back into LicitaLab.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What LicitaLab and Zapier do together

The LicitaLab integration on Zapier turns what happens on your public tenders into a starting signal for other tools. LicitaLab reports eight kinds of events, from a new purchase order to a published result, and Zapier passes each one to the apps you choose. The flow only goes out of LicitaLab, never in.

Three results people build first. A won-or-lost log kept up to date: Opportunity Result Published fires when a result comes out, and its Result field tells won from lost, so a filter can send each case to the right place. A deadline that nobody misses: Opportunity Date Changed fires when a key date of a followed tender is rescheduled, and you can narrow it by Date Type. A purchase order that reaches the right person: New Purchase Order Received fires when an order tied to your account's tax number arrives.

The limits are just as clear. There are no actions and no searches, so Zapier cannot create, update or look up anything inside LicitaLab. Seven of the eight triggers only watch tenders you follow, so nothing fires on a tender you have not sent to tracking. If you need two-way sync, Zapier will not provide it for this app (see n8n vs Zapier before you choose a platform).

The upside: all eight triggers are instant, so speed does not depend on your plan, and LicitaLab is not a premium app.

Vocabulary

Zapier vocabulary in one minute

Seven words carry this page. Here is each one in plain English.

Zap
The automation you build on Zapier: one event that starts it, then one or more steps that run each time that event happens.
Trigger
The event that starts the Zap. LicitaLab offers eight, all tied to tenders you follow or to purchase orders received.
Action
The step that does the work once the Zap has started. LicitaLab has none, so actions always live in other tools.
Task
The unit Zapier bills: one action completed successfully. A LicitaLab trigger firing never counts as a task.
Polling vs instant
A polling trigger is checked on a timer set by your plan. An instant one, like all eight here, is pushed by the app at once.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, such as a lost result.
Search step
A step that looks up something already stored in an app for later steps. LicitaLab offers no search step.
Cost

What a LicitaLab Zap costs

Zapier bills tasks, and LicitaLab itself never generates one: its triggers are free, only the actions after them count.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Premium appNo, LicitaLab works on the free plan
  • Trigger speedInstant on every plan

When a LicitaLab trigger fires, nothing is billed. Each action that follows in another tool and succeeds is one task; a failed one is not counted. The free plan gives 100 tasks a month and two-step Zaps: one LicitaLab trigger, one action. A filter, for instance to keep only lost results, makes the Zap multi-step (anything past one trigger and one action), which needs a paid plan. The interval grid below applies to polling triggers only: all eight LicitaLab triggers are instant, so they fire straight away on every plan, Free included.

Connect

Connect your LicitaLab account

  1. 01

    Open Apps

    In your Zapier account, go to Apps. A connection lives there: your LicitaLab account linked to Zapier once, then reused by every Zap that uses it. You need a LicitaLab account first.

  2. 02

    Add LicitaLab

    Click + Add connection, type LicitaLab in the dialog, pick it from the results, then confirm with Add connection. A new browser tab opens for the sign-in.

  3. 03

    Sign in and grant access

    Log in to LicitaLab in that tab and allow Zapier to use the account. The triggers watch what this account follows, so connect the account that actually tracks your tenders.

First Zap

Your first LicitaLab Zap

GoalEach published result on a tender you follow is logged in your spreadsheet, but only when the result is the one you choose.

  1. 01

    Create the Zap

    Start a new Zap, pick LicitaLab as the app that starts it, then choose Opportunity Result Published as the event. Select your LicitaLab connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from the connected account, so you see a real result and its Result field before mapping anything.

  3. 03

    Add the filter

    Use the plus icon, choose Filter, then set the field to look at (Result), the rule and the value. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the spreadsheet step

    Add your spreadsheet as the action and map the tender details from the trigger into the columns. Test it and check that the row really appears.

  5. 05

    Publish

    Click Publish to switch the Zap on. Since the trigger is instant, each new result is handled as soon as LicitaLab reports it.

Triggers

LicitaLab triggers on Zapier

8 events start a Zap when something happens in LicitaLab, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Purchase Order Received

Instant trigger

In Zapier“Triggers when a purchase order (orden de compra) associated with your LicitaLAB account's tax number is received.”

Starts the Zap when a purchase order linked to the tax number of your LicitaLab account comes in. It is the only trigger here that does not depend on a tender you follow, so it catches orders directly.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a new order should be recorded or passed on to the right colleague, without anyone checking LicitaLab first.
Watch out
only orders tied to the tax number on the connected account are picked up.
2

Opportunity Date Changed

Instant trigger

In Zapier“Triggers when a key date of an opportunity you follow is rescheduled. Filter by Date Type (close, awarding, field_visit, …) to narrow it down.”

Fires when one of the key dates of a tender you follow is moved. The Date Type field lets you narrow it to the kind of date that matters to you, such as close, awarding or field visit.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a rescheduled deadline must reach your calendar or your team before anyone works to the old date.
Watch out
without narrowing by Date Type, every rescheduled date starts the Zap.
3

New Opportunity Document

Instant trigger

In Zapier“Triggers when a new document is attached to an opportunity you follow, after the initial publication.”

Kicks off when a new document is attached to a tender you follow, once the tender has been published. Documents present from the first publication do not start it; only later additions do.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when whoever prepares the bid must know straight away that a new document landed on the file.
Watch out
the documents of the original publication never fire it.
4

Opportunity Followed

Instant trigger

In Zapier“Triggers when you send an opportunity (licitación) to tracking in your LicitaLAB account.”

Runs as soon as you send a tender to tracking in your LicitaLab account. In practice, it marks the moment a tender enters your pipeline, which makes it the natural starting point for everything else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when following a tender should open a line in your tracking sheet or alert a colleague.
Watch out
tenders followed before the Zap was published are not sent over.
5

New Question in Reverse Forum

Instant trigger

In Zapier“Triggers when a new question is posted in the reverse forum of an opportunity you follow.”

Goes off when someone posts a new question in the reverse forum of a tender you follow. Questions there can change how a bid is read, so this one is easy to miss by hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your bid team should see every new question without checking each forum.
Watch out
it covers followed tenders only, not every forum on the platform.
6

Opportunity Offers Opened

Instant trigger

In Zapier“Triggers when the offers of an opportunity you follow are opened (acto de apertura).”

Reacts when the offers on a tender you follow are opened, the step LicitaLab labels acto de apertura. It tells you the competition phase has moved on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your team wants to know the moment offers are opened, to prepare for what comes next on that tender.
Watch out
this trigger says the offers were opened; the outcome comes later, through Opportunity Result Published.
7

Opportunity Result Published

Instant trigger

In Zapier“Triggers when the result of an opportunity you follow is published. Use the Result field to tell won from lost.”

Fires when the result of a tender you follow is published. The Result field it brings tells a won tender from a lost one, which is what most follow-up steps need.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when won and lost tenders should go to different places, for example two separate tabs of the same sheet.
Watch out
splitting won from lost needs a filter on Result, and a filter means a paid plan.
8

Opportunity Status Changed

Instant trigger

In Zapier“Triggers when the status of an opportunity you follow changes — for example when it closes or is awarded.”

Triggers whenever the status of a tender you follow changes, for example when it closes or is awarded. It is the broadest of the tender triggers, catching every move of status in one place.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when you want a single running log of how each followed tender moves along.
Watch out
because every status change fires it, a busy tender can use several tasks downstream.
When it breaks

When a LicitaLab Zap breaks

Zapier links no help article to LicitaLab, so the known failure modes are the general ones every Zap shares.

  • Past tender history is not sent

    A Zap reacts only to what happens after it is switched on. Results, documents or orders from before stay in LicitaLab; moving that backlog is a separate job.

  • A loop drains your tasks

    If a Zap writes into the very place its own trigger watches, it sets itself off again and again. Keep the action of one Zap away from the trigger of another.

  • A sudden burst is held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back before the actions run.

  • Unfollowed tenders stay silent

    Seven of the eight triggers only watch tenders you follow. A tender you have not sent to tracking will never start a Zap, however much it changes.
Need help

Need help automating LicitaLab with Zapier?

A person reads every message.

FAQ

LicitaLab Zapier integration: questions

01Is the LicitaLab Zapier integration free?
Yes, within the free plan limits. LicitaLab is not a premium app, and its eight triggers cost nothing when they fire. On the free plan you get 100 tasks a month and Zaps of two steps: one LicitaLab trigger, then one action in another tool. If you add a filter, for example to keep only won tenders, or a second action, the Zap becomes multi-step and needs a paid plan. Unlimited Zaps are allowed, so one small Zap per trigger stays free.
02How many tasks does a LicitaLab Zap use?
None for LicitaLab itself, one for each successful action after it. A trigger firing is never billed, so a status change that starts the Zap costs nothing on its own. The spreadsheet row or the email your Zap then creates is one task each time it succeeds; a failed action is not counted. With two actions, both count. A broad trigger like Opportunity Status Changed can fire several times per tender, so watch the 100-task monthly ceiling on Free.
03Is the LicitaLab integration real time?
Yes. All eight LicitaLab triggers are instant: the app tells Zapier the moment something happens, and the Zap starts straight away. The polling grid that sets the pace for other apps, 15 minutes on Free down to one minute on Team and Enterprise, does not apply here. That makes the free plan as fast as any paid one for LicitaLab. In the editor, a Zap built on these triggers shows a lightning bolt, which is how you can confirm it.
04What does it take to connect LicitaLab to Zapier?
A LicitaLab account, ideally the one that actually follows your tenders, since seven of the eight triggers watch only followed tenders. The connection is made once from the Apps page of Zapier with + Add connection, then a sign-in in a new tab where you grant Zapier access. Every later Zap reuses it. For New Purchase Order Received, the account also needs the tax number your orders are tied to, because only those orders are picked up.
05Why does a LicitaLab trigger never fire for some tenders?
Because those tenders are not followed. Opportunity Date Changed, New Opportunity Document, New Question in Reverse Forum, Opportunity Offers Opened, Opportunity Result Published and Opportunity Status Changed all watch tenders you have sent to tracking, and Opportunity Followed fires only at that moment. Send the tender to tracking in LicitaLab and the next event on it will start the Zap. Events that happened earlier are not sent after the fact.
06What if the LicitaLab operation you need does not exist?
Then Zapier cannot do it for LicitaLab today. The integration is trigger-only: eight instant triggers, no action and no search. Writing into LicitaLab, such as following a tender automatically, or looking up a tender from another app is out of reach through this connector. The workable route is to treat LicitaLab as a source of signals and do the writing in other tools. Zapier's app page for LicitaLab lists every available operation.
07Zapier, Make or n8n for LicitaLab?
Compare on criteria rather than picking a winner. Zapier suits LicitaLab well if you want to react to tender events: all eight triggers are instant, even on the free plan. The thing to check elsewhere is whether another platform offers what Zapier lacks here, a way to write into LicitaLab. Also weigh how many events your followed tenders generate each month, who will maintain the flows, and whether filters push you to a paid plan anyway.
Same platform

Other docs you might need on this stack.

Browse all integrations