Resources · Zapier integration

Luminjo Zapier integrationAutomate Luminjo with Zapier.

The Luminjo Zapier integration gives you 3 triggers, 3 actions and 9 searches around the three things Luminjo stores: tickets, tags and typical responses. Here is what each one does, what it costs, and where it trips people up.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Luminjo Zapier integration actually does

Luminjo is a support desk: it holds tickets, the tags you sort them with, and typical responses, the ready-made answers your team reuses. Connecting it to Zapier lets those three objects travel to and from your other tools without anyone copying them by hand. Zapier watches Luminjo for new items, and it can also write tickets, tags and replies into it.

Three results come back again and again. First, a log of incoming requests: New Ticket feeds every fresh ticket into a sheet or a database, so the person who reports on support volume stops exporting lists. Second, tickets opened from outside the desk: Create Ticket turns a message caught elsewhere (a form, an inbox) into a proper Luminjo ticket with a subject, a sender and a body. Third, a shared answer library: New Typical Response tells the rest of the team each time someone writes a new canned reply, so nobody drafts the same answer twice.

Now the limits. Every trigger here is a polling one: Zapier asks Luminjo for news on a timer instead of being told, so nothing lands instantly. Luminjo exposes no delete operation in Zapier, and no trigger fires when an existing ticket changes. Updating a ticket, a tag or a reply is possible, but Zapier files those three operations under searches, which surprises almost everyone the first time.

If you are still weighing the platform itself, read our Zapier review, then the n8n vs Zapier comparison.

Vocabulary

Zapier words you will meet on this page

Eight words carry the whole page. Each one is used again later without a reminder.

Zap
The automation you build in Zapier: one trigger first, then one or several actions that run each time that trigger goes off.
Trigger
The event in an app that starts the Zap, such as a new Luminjo ticket. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills you for: one action your Zap finished successfully. Your plan counts these and nothing else.
Polling vs instant
A polling trigger is checked on a timer, and Zapier keeps only what it has not seen. An instant trigger is pushed by the app the moment it happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can use what it found.
Connection
Your Luminjo account linked to Zapier once, then reused by every step of every Zap that touches Luminjo.
Cost

What Luminjo with Zapier really costs

Luminjo is not a premium app, so it works on the free plan. What you pay for is tasks, and only some steps produce them.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger costNone, checks are free
  • Failed actionNot counted

The trigger never costs a task, and neither does Zapier checking Luminjo for new tickets, however often it looks. Each action that succeeds counts as one task; an action that fails is not counted. A Zap with three actions eats three times what a one-action Zap does. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a second action or any of the nine Luminjo searches and the Zap becomes multi-step, which needs a paid plan. The interval below applies to all three Luminjo triggers, since all three are polling ones.

Connect

Connect your Luminjo account in three moves

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Luminjo account, plus access to any ticket or reply you do not own yourself but want the Zap to touch.

  2. 02

    Pick Luminjo

    Type Luminjo in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the Luminjo side for the sign-in.

  3. 03

    Sign in and allow access

    Log in to Luminjo in that tab and grant Zapier access to the account. The connection then shows on the Apps page, and every Zap you build can reuse it without asking again.

First Zap

Your first Zap: log every new Luminjo ticket

GoalEach new ticket that reaches Luminjo and passes your filter appears as a row in your spreadsheet, so support volume can be tracked without exports.

  1. 01

    Create the Zap

    From your Zapier dashboard, start a new Zap. With a filter in the middle it becomes a multi-step Zap, so it needs a paid plan; drop the filter and the two remaining steps fit the free plan.

  2. 02

    Set the trigger

    Choose Luminjo as the app and New Ticket as the event, then select the Luminjo connection you added earlier from the account list.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets of the account, so you map fields on a real ticket instead of guessing.

  4. 04

    Add the filter

    Click the plus icon under the trigger and pick Filter. Set the three boxes: the field to look at, the rule, and the value to compare with. Only the tickets that pass go on.

  5. 05

    Add the action

    Pick your spreadsheet app and its new-row event, then drag the ticket subject, sender and content into the matching columns.

  6. 06

    Test, then publish

    Test the action once and check that the row looks right. Then click Publish to switch the Zap on; only tickets created after that moment will flow.

Triggers

Luminjo triggers in Zapier

3 events start a Zap when something happens in Luminjo. Zapier checks for them at the interval your plan allows.

1

New Tag

Polling trigger

In Zapier“Triggers when a new tag is created.”

This one wakes up whenever someone adds a tag to Luminjo, and passes its name to the rest of the Zap. It is the quiet trigger of the three: tags appear rarely, so the Zap sleeps most of the time and costs nothing while it does.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a shared list of your support categories in sync, so whoever reports on tickets always works from the current set of tags.
Watch out
it reacts to a tag being created, not to a tag being attached to a ticket, which is a different event this app does not expose.
2

New Ticket

Polling trigger

In Zapier“Triggers when a new ticket is created.”

The workhorse. Each ticket that lands in Luminjo starts the Zap, carrying its subject, its sender and its content into the following steps. Most Luminjo Zaps begin here, because the ticket is where every support request starts.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
copy every incoming request into a reporting sheet, or warn a channel when a ticket arrives so someone picks it up.
Watch out
Zapier remembers which tickets it has already seen, so a ticket edited later never starts the Zap a second time.
3

New Typical Response

Polling trigger

In Zapier“Triggers when a new typical response is created.”

Fires when someone saves a new typical response, the reusable answer agents paste into tickets. The title and the text of the reply travel with it, ready for the next step to store or announce.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
back up your answer library to a document, or tell the team a new reply exists so they stop drafting it from scratch.
Watch out
a reply rewritten later does not count as new, so edits to an existing answer never reach the Zap.
Actions

Luminjo actions in Zapier

Luminjo gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Tag

Action

In Zapier“Creates a tag in luminjo.”

Adds a tag to Luminjo with the name you give it. Only the name is required.

When to use it
your categories live in another tool and you want Luminjo to offer the same ones to agents.
Watch out
a Zap that creates tags while also watching New Tag will set itself off again, so keep those two in separate, unrelated Zaps.
2

Create Ticket

Action

In Zapier“Creates a ticket in luminjo.”

Opens a ticket in Luminjo from anything an earlier step caught. It wants three things filled in: a subject, a sender email address and the content.

When to use it
a form answer or an email received outside the desk should become a ticket your agents can work on.
Watch out
if the previous step can leave the sender empty, the action fails, so map a field that is always present.
3

Create Typical Response

Action

In Zapier“Creates a typical response in luminjo.”

Saves a new reusable answer in Luminjo. You give it a one-sentence title that sums the reply up, and the text agents will paste.

When to use it
answers are drafted and approved in a shared document, and the approved version should land in the desk without retyping.
Watch out
both the title and the content are required, so an empty cell upstream stops the step.
Searches

Luminjo searches in Zapier, including the updates

9 search steps look for data that already exists in Luminjo, so a later step can use it.

A search step finds something that already exists in Luminjo and hands it to the next steps. In the editor, the searches sit at the bottom of the Action event list under a SEARCH heading. Luminjo puts nine operations there, and three of them change data rather than just reading it. Every search makes the Zap multi-step, so all of them need a paid plan. Luminjo offers no find-or-create variant. Three settings decide what happens when a search does not get a clean single answer.

1

Find Tag

Search

In Zapier“Finds a tag resource.”

Looks up a single tag from its identifier number and returns its details to the steps after it.

When to use it
an earlier step gave you a tag number and you need its readable name in a message or a report.
Watch out
it searches by number only, not by name, so a tag name typed by a person will not find anything.
2

Find Ticket

Search

In Zapier“Finds a ticket resource.”

Pulls one ticket from Luminjo using its identifier number, so later steps can read its subject, sender and content.

When to use it
a message elsewhere mentions a ticket number and the Zap has to fetch the full ticket before replying or logging it.
Watch out
without the number the search has nothing to go on; plan where it comes from.
3

Find Typical Response

Search

In Zapier“Finds a typical response resource.”

Fetches one saved answer by its identifier number, with its title and text.

When to use it
you want a Zap to drop the exact wording of an approved reply into an email or a note in another tool.
Watch out
the number is required; the search cannot look a reply up by its title.
4

Retrieve All Tags

Search

In Zapier“Retrieves all tags resources.”

Brings back the full list of tags in the account, with no field to fill in.

When to use it
a Zap needs the whole set of categories at once, for example to copy them into a reference sheet.
Watch out
with several results, the default keeps only the first one; switch the multiple-results setting if you want them all.
5

Retrieve All Tickets

Search

In Zapier“Retrieves all tickets resources.”

Returns every ticket the connected account can see, again without any field to set.

When to use it
a one-off pass over your tickets, since a Zap never picks up tickets created before it was switched on.
Watch out
handing all results on at once to an action can burn many tasks in a single run.
6

Retrieve All Typical Responses

Search

In Zapier“Retrieves all typical responses resources.”

Lists the whole library of saved replies in one go.

When to use it
you want to rebuild a copy of the answer library somewhere else, all at once rather than reply by reply.
Watch out
the default still keeps a single result; change the multiple-results setting first or you will only get one reply.
7

Update Tag

Search

In Zapier“Updates the tag resource.”

Changes an existing tag, identified by its number. Zapier lists it under searches even though it writes to Luminjo.

When to use it
a category is renamed in your source tool and Luminjo should follow.
Watch out
people look for it among the actions and give up; scroll down to the SEARCH heading.
8

Update Ticket

Search

In Zapier“Updates the ticket resource.”

Edits an existing ticket from its identifier number. It also carries an optional agent status field, set to true when the change comes from an agent.

When to use it
something decided in another tool should be reflected on the ticket itself.
Watch out
it sits under SEARCH, so a free plan cannot use it, even in an otherwise simple Zap.
9

Update Typical Response

Search

In Zapier“Updates the typical response resource.”

Rewrites a saved answer that already exists, found through its identifier number.

When to use it
the master wording of a reply changed in your document and agents should paste the new version.
Watch out
keep the number of each reply next to its source text, or the Zap has nothing to target.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switched on, the Zap goes on with empty hands.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Luminjo does not offer it on any of its searches, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them along at once.
When it breaks

When the Luminjo Zap breaks

Zapier attaches no help article to Luminjo, and no app-specific limit is documented. What breaks is what breaks on any Zapier app.

Four cases cover almost every support request about a Luminjo Zap. None of them shows up as a red banner; they show up as missing rows or a task count that jumps. If you are stuck past these, head to Zapier troubleshooting.

  • Old tickets never arrive

    A Zap only reacts to what happens after you publish it. Tickets already in Luminjo stay where they are; moving that backlog is a separate job.

  • A Zap that feeds itself

    Create Tag inside a Zap triggered by New Tag starts the Zap again, then again. The loop burns through your monthly tasks fast.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of running them all.

  • No duplicate, even when expected

    Zapier tracks what it has already seen on a polling trigger. The same ticket never starts the Zap twice, even after an edit.
Need help

Need help automating Luminjo with Zapier?

A person reads every message.

FAQ

Luminjo Zapier integration: questions people ask

01Is the Luminjo Zapier integration free?
Yes, as long as your Zap stays at two steps. Luminjo is not a premium app, so it runs on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is that the free plan stops at one trigger and one action. Logging each new ticket into a spreadsheet fits inside that limit. A filter, a second action or any Luminjo search, Update Ticket included, turns the Zap multi-step and requires a paid plan.
02How many tasks does a Luminjo Zap use?
One per successful action, per run. The New Ticket trigger costs nothing, and the checks Zapier makes on Luminjo are free however frequent they are. If each ticket starts a Zap that adds a spreadsheet row and then posts a message, that run costs two tasks. An action that fails is not counted against the plan. Watch the searches set to pass all results along: they can feed many items to an action in a single run and empty the monthly count.
03Does Luminjo trigger Zaps in real time?
No. All three Luminjo triggers are polling ones: Zapier asks Luminjo for new items on a timer and keeps only what it has not seen yet. On the free plan that check happens every 15 minutes, on Professional every 2, on Team and Enterprise every minute. Paid plans can also run a check by hand from the editor when you are testing. The type is set by the app itself, so no setting in Zapier turns these into instant triggers.
04What does it take to connect Luminjo to Zapier?
A Luminjo account and access to whatever the Zap should touch. From the Apps page of Zapier, click + Add connection, pick Luminjo, sign in in the tab that opens and grant access to the account. If the Zap must read or change tickets or replies created by colleagues, the account you connect needs read or write rights on them. Once added, the same connection is reused by every Luminjo step in every Zap you build.
05Why is Update Ticket missing from the actions?
Because Zapier files it under searches. Luminjo exposes Update Tag, Update Ticket and Update Typical Response in the SEARCH section at the bottom of the action-event list. They do write to Luminjo, but they behave as search steps, which also means they make the Zap multi-step and need a paid plan. Each one asks for the identifier number of the item to change, so an earlier step has to supply that number.
06What if the Luminjo operation you need is not there?
Then the editor will not offer it, since the list for Luminjo is fixed at 3 triggers, 3 actions and 9 searches. Check the SEARCH section first, because the three update operations live there and are easy to miss. There is no delete operation and no trigger on a changed ticket. If the step is still missing, combine what exists, for example Retrieve All Tickets followed by a filter that keeps only the tickets matching your rule.
07Zapier, Make or n8n for Luminjo?
Decide on criteria, not on a ranking. On Zapier, Luminjo offers 15 ready operations, runs on the free plan for two-step Zaps, and checks for news on a timer set by your plan. Ask yourself how many steps your flows really need, since every search pushes you to a paid plan. Then look at where the tools around Luminjo already live, because rebuilding their connections on another platform has a cost of its own.
Same platform

Other docs you might need on this stack.

Browse all integrations