Resources · Zapier integration

LocaliQ Zapier integrationAutomate LocaliQ with Zapier.

The LocaliQ Zapier integration gives you 2 triggers and no action. Both triggers are instant and LocaliQ works on the free plan. This page covers what each trigger hands you, what a Zap costs in tasks and the spots where it trips.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LocaliQ Zapier integration does for you

The integration links your LocaliQ account to Zapier, so new contacts and contact interactions in LocaliQ can set off work in your other tools. You build a Zap (one automation: an event that starts it, then the steps that follow) and Zapier runs it each time that event happens, with no copying by hand.

A contact list that stays in step. New Contacts is a trigger (the event that starts the Zap): it fires when a contact is created in LocaliQ. The next step, an action (the part that writes, sends or moves something for you), can add that person to your spreadsheet or your CRM.

An alert when a contact gets in touch. New Contact Interaction fires when LocaliQ records a new interaction with a contact. Route it to your team chat and the person who should follow up hears about it without watching a dashboard.

One place for both. Two Zaps, one per trigger, feeding the same spreadsheet give you a running log of new contacts and of what they did next.

What Zapier does not do here: LocaliQ has no action and no search in Zapier. A Zap can read from LocaliQ but never write into it, so creating or updating a contact there is out of reach. When the catalog is this one-sided, the n8n vs Zapier comparison is worth a look before you decide.

Vocabulary

The Zapier words used on this page

Seven terms, one line each. With these, nothing below needs a second read.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event to come in.
Action
What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan counts those.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself as soon as the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your LocaliQ account linked to Zapier once, then reused by every step of every Zap that works with LocaliQ.
Cost

What a LocaliQ Zap costs you in tasks

Zapier bills completed actions, not events. LocaliQ only offers triggers, and a trigger never costs a task.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo, works on the free plan

What you pay for is the action in the other app: each one that succeeds counts once, so a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. LocaliQ is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below is for polling triggers and does not apply here: both LocaliQ triggers are instant.

Connect

Connect your LocaliQ account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. You need a LocaliQ account first, plus access to any contacts you do not own but want the Zap to read.

  2. 02

    Find LocaliQ in the dialog

    Type LocaliQ in the search box of the dialog, select it and click Add connection. A new tab opens on the LocaliQ side so you can sign in with the account that holds your contacts.

  3. 03

    Allow access

    Sign in to LocaliQ in that tab and grant Zapier access to the account. The connection then shows up in your Apps list, and every Zap that uses LocaliQ picks it from there.

First Zap

Your first Zap: flag contact interactions to your team

GoalEach new contact interaction in LocaliQ that passes your filter is posted in your team chat, so follow-up starts without delay.

  1. 01

    Create the Zap and set the trigger

    Start a new Zap, choose LocaliQ and New Contact Interaction as the event, then pick your connection. It is an instant trigger, so the editor shows a lightning bolt on it.

  2. 02

    Test it on real data

    Run the test. Zapier brings back the three most recent items from your account. Pick one: it is the sample you will map fields from in the next steps.

  3. 03

    Add the filter

    Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule and the value. A text rule only works on text.

  4. 04

    Add the chat message and test

    Add the action of your team chat and map the contact details into the message. With a filter the Zap is multi-step, so it needs a paid plan. Test each step once.

  5. 05

    Publish

    Click Publish to switch it on. Only interactions recorded from then on go through. If the editor feels new, the Zapier training is a good next step.

Triggers

LocaliQ triggers in Zapier

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

1

New Contacts

Instant trigger

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

Starts your Zap whenever a contact is created in LocaliQ, and hands that contact's details to the steps that follow so they can file or share them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your CRM or your spreadsheet should hold every new LocaliQ contact without anyone exporting a list.
Watch out
contacts created before you publish the Zap are never picked up, so the existing base has to be moved separately.
2

New Contact Interaction

Instant trigger

In Zapier“Triggers when a new contact interaction is generated.”

Fires when LocaliQ generates a new interaction for a contact, which makes it the trigger to use when what matters is a contact doing something rather than simply appearing.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
someone on your team must react quickly when a known contact gets back in touch.
Watch out
a busy account can send a flood of interactions at once, which Zapier may hold back.
When it breaks

When a LocaliQ Zap breaks

Zapier links no help article to LocaliQ and documents no limit of its own for the app. What goes wrong comes from how Zapier itself works.

These are the cases to know before you publish. For an error that is not listed here, the Zapier troubleshooting page is the place to start.

  • The existing base is not replayed

    A Zap only reacts to what happens after you switch it on. Contacts and interactions from before are ignored, and moving them is a separate job.

  • A burst held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the Zap back instead of running it.

  • A filter that never passes

    Filter rules are typed: a number rule applied to text never matches, so the message after the filter never goes out.

  • A free Zap one step too long

    On the free plan a Zap holds one trigger and one action. Adding a filter or a second app after a LocaliQ trigger needs a paid plan.
Need help

Need help automating LocaliQ with Zapier?

A person reads every message.

FAQ

LocaliQ Zapier integration: common questions

01Is the LocaliQ Zapier integration free?
Yes, as long as each Zap stays at two steps. LocaliQ is not a premium app, so it works on the free plan, with 100 tasks a month and unlimited Zaps. The limit is the shape: one trigger and one action. Adding each new LocaliQ contact to a spreadsheet fits. Add a filter or a second action and the Zap becomes multi-step, which only paid plans run, so plan your scenario around that before you start building it.
02How many tasks does a LocaliQ Zap use?
Only the actions in your other apps count, one task each when they succeed. The LocaliQ triggers themselves cost nothing. A Zap that adds each new contact to your spreadsheet costs one task per contact. If it also posts in your team chat, it costs two per contact, because every successful action counts on its own. An action that fails is not billed, and a quiet account costs you nothing at all.
03Do LocaliQ triggers fire in real time?
Yes. Both LocaliQ triggers are instant: the app tells Zapier as soon as a contact is created or an interaction is recorded, and the Zap starts right away whatever your plan. The intervals in Zapier's plan grid only concern triggers that Zapier checks on a timer, and LocaliQ has none of those. In the editor, the lightning bolt on the trigger card tells you it is instant, so there is nothing to tune.
04What does it take to connect LocaliQ to Zapier?
A LocaliQ account, plus access to any contacts you do not own but want the Zap to read. You connect from the Apps page of your Zapier account: add a connection, pick LocaliQ, sign in in the tab that opens and allow access. After that, every Zap that uses LocaliQ reuses the same connection, so you only link the account once. If some contacts belong to an account you do not own, get read access to it before you build.
05Can a Zap create or update contacts in LocaliQ?
No. LocaliQ offers two triggers in Zapier and no action, so a Zap can react to what happens in LocaliQ but cannot write anything back into it. Contacts created in your CRM or your forms will not reach LocaliQ through Zapier. Plan your flows in one direction: LocaliQ as the starting point, your other tools as the destination. If you need the reverse, it has to happen outside Zapier, so settle that before you design anything that depends on it.
06What if the LocaliQ operation you need is not in Zapier?
Then a Zap cannot do it today. Zapier offers two triggers for LocaliQ, nothing else shows up in the editor, and there is neither an action nor a search step. Writing to LocaliQ from a Zap is not on the list. The usual way around it is to rethink the flow with what exists, or to look at another automation tool that can call the app directly when the missing step is essential to you.
07Zapier, Make or n8n for LocaliQ?
It depends on your criteria, not on a ranking. Zapier is quick to set up here: two instant triggers and a guided connection. Its limits are a read-only catalog, with no way to write into LocaliQ, and the paid plan any filter calls for. Make and n8n have their own connectors, so check what each offers for LocaliQ. Weigh the direction your data must flow and who will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations