Resources · Zapier integration

Locate2u Zapier integrationAutomate Locate2u with Zapier.

Locate2u Zapier integration: 1 trigger, 6 actions and 4 searches to move stops, orders and shipments between Locate2u and the rest of your tools. Here is what each one does, what it costs on each plan and where it tends to break.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Locate2u Zapier integration actually does

Locate2u is a booking and routing tool for service and delivery businesses. Plugged into Zapier, it can start an automation when a stop changes status, and it can receive work from other tools: new orders, shipments and stops, edits to existing ones, and lookups of what is already in your account.

Three things people typically get out of it. First, a running log: every time a stop changes status, Stop Status Change pushes the event out, and a spreadsheet or a reporting tool gets a new line without anyone copying it. Second, no double entry: an order taken somewhere else becomes a Locate2u order through Create Order, with its purchase order number, shipping address and date already filled in. Third, a record that stays current: when a shipment's drop-off moves, Update Shipment rewrites it in Locate2u instead of leaving two versions of the truth.

Now the limits, because the list of operations is short and precise. Only one event can start a Zap from Locate2u, the stop status change. A new order or a new shipment created inside Locate2u starts nothing on its own. There is no delete action either: stops, orders and shipments can be created, updated and looked up, never removed. And nothing in this integration touches route optimization or live location sharing, even though Locate2u itself is built around them.

If you are still weighing platforms, the n8n vs Zapier and Make vs Zapier comparisons sit next to this page.

Vocabulary

Zapier vocabulary, in one minute

Eight words come back on every line of this page. Here they are in plain terms, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that event happens.
Trigger
The event that starts a Zap. Locate2u has exactly one: a stop whose status changes. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes or updates something for you, such as a new stop in Locate2u.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
Polling: Zapier asks the app for news on a timer. Instant: the app calls Zapier as soon as the event happens. Locate2u's trigger is instant.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something that already exists, like an order's details, so the later steps can use what it found.
Connection
Your Locate2u account linked to Zapier once, then reused by every step of every Zap that touches Locate2u.
Cost

What it really costs

Short version: the Locate2u trigger costs nothing, and each action that succeeds costs one task. Locate2u is not a premium app, so it works from the free plan.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

An action that fails is not counted. Looking for data is free as well. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search step or a second action and it becomes a multi-step Zap, which needs a paid plan. The grid below is how often Zapier checks a polling trigger on each plan; it does not apply here, since the only Locate2u trigger is instant.

Connect

Connect your Locate2u account in 3 steps

  1. 01

    Add Locate2u from the Apps page

    In your Zapier account, open the Apps page and click + Add connection. Type Locate2u in the dialog, pick it from the list, then confirm with Add connection.

  2. 02

    Sign in to Locate2u

    A new tab opens on Locate2u. Sign in with the account whose stops, orders and shipments the Zaps will handle. If some of those records belong to a colleague, you need read or write access to them first.

  3. 03

    Grant Zapier access

    Approve the access Zapier asks for. The connection then appears on the Apps page, and every Zap step that uses Locate2u offers it in a dropdown, so the account is linked once for all your Zaps.

First Zap

Your first Zap: log the stop status changes that matter

GoalEach time a stop changes status in Locate2u, a filter keeps only the changes that meet your condition, and a new row lands in your spreadsheet.

  1. 01

    Create the Zap

    From your Zapier dashboard, create a new Zap. The editor opens with an empty trigger card at the top: a Zap always starts with its trigger, never with an action.

  2. 02

    Set the Locate2u trigger

    Pick Locate2u as the app and Stop Status Change as the event, then choose your Locate2u connection. Because this trigger is instant, the editor marks it with a lightning bolt.

  3. 03

    Test it on a real stop

    Run the test. Zapier brings back the three most recent items from your account. Pick one of them, so every field you map later is shown with real data instead of a blank.

  4. 04

    Add the filter

    Click the plus icon, add a Filter step and fill its three boxes: the field to look at, the rule, the value. Use a text rule on text and a number rule on numbers, or it never passes.

  5. 05

    Add the spreadsheet action

    Add your spreadsheet tool as the last step and map the Locate2u fields you want into its columns. Test this step too and read what came back before going any further.

  6. 06

    Publish

    Click Publish to switch the Zap on. The filter makes it a multi-step Zap, so it needs a paid plan. Drop the filter and the same Zap fits the free plan.

Triggers

The Locate2u trigger

1 event starts a Zap when something happens in Locate2u, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Stop Status Change

Instant trigger

In Zapier“Triggers when the status of a stop in Locate2u is changed.”

Starts your Zap whenever a stop in Locate2u moves to another status. Whatever comes next (a log line, an order update, a message to the office) reacts to the progress of the stop itself, with no one watching the screen.

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 the progress of a stop should show up somewhere other than Locate2u, for a customer, a manager or a report.
Watch out
it is the only trigger Locate2u offers on Zapier, so new orders or new shipments cannot start a Zap by themselves. A Zap that edits the stop it watches can also set itself off again.
Actions

The 6 Locate2u actions

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

1

Create Order

Action

In Zapier“Creates order. Can be assigned to a user or be unassigned”

Adds a new order to Locate2u, assigned to a team member or left unassigned. Three values are required: a purchase order number, a shipping address and an order date.

When to use it
orders are taken in another tool and should land in Locate2u without being typed twice.
Watch out
if the source has no date or no address to map, the step cannot run, since all three are mandatory.
2

Create Shipment

Action

In Zapier“Creates shipment. Can be assigned to a user or be unassigned”

Opens a shipment between two points, a pick-up address and a drop-off address, both mandatory. Like an order, it can go to a team member or stay unassigned.

When to use it
the job is a move from A to B rather than a single visit.
Watch out
a missing address on either end stops the action. A failed action is not billed, but nothing gets created either.
3

Create Stop

Action

In Zapier“Creates a stop. Can be assigned to a user or left unassigned.”

The lightest of the three create actions: a single address is all it asks for, and the stop can be assigned or left open.

When to use it
a one-off visit booked through a form or another tool should appear in Locate2u as its own stop.
Watch out
since the address is the only required field, check that the field you map really holds a full address and not just a name.
4

Update Order

Action

In Zapier“Update existing order”

Rewrites an order that already exists. It finds it by its Order ID, and asks again for the purchase order number, the shipping address and the order date.

When to use it
the details of an order change in your sales tool after it was sent to Locate2u.
Watch out
the Order ID has to come from an earlier step that carries it; without it there is nothing to update.
5

Update Shipment

Action

In Zapier“Update existing shipment”

Changes a shipment you already have. Four values are mandatory: the Shipment ID, the IDs of its pick-up and drop-off stops, and the drop-off address.

When to use it
the delivery end of a shipment moves and Locate2u should follow.
Watch out
the two stop fields expect identifiers, not addresses. Mapping text into them is the quickest way to a failed step.
6

Update Stop

Action

In Zapier“Update a Stop in Locate2u with Source and Source Reference Parameter”

Edits one stop you point at with its Stop Id. The address has to be sent every time, even when only the contact or the time window changes.

When to use it
a visit's address is corrected upstream and the stop must match.
Watch out
if the Zap starts from Stop Status Change, a Zap that writes into what its own trigger watches can loop and burn tasks.
Searches

The 4 Locate2u searches

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

A search step reads what is already in Locate2u and hands it to the steps that follow. In the editor, the searches sit at the bottom of the Action event list, under SEARCH. Locate2u offers no find-or-create variant, so a search here only ever finds. Three settings decide what happens when the result is not the one you expected.

1

Get Order Details

Search

In Zapier“Get existing order's details”

Pulls up an existing order from its Order ID and hands its details to the next steps.

When to use it
a later step, an email or a report line, needs the order's content and only its ID is at hand.
Watch out
the Order ID is required, so this search confirms and enriches an order you already know; it cannot hunt for one by address or date.
2

Get Shipment Details

Search

In Zapier“Get existing shipment's details”

Reads a shipment from its Shipment Id, so what Locate2u holds about it becomes available as fields further down the Zap.

When to use it
just before Update Shipment, to see what the shipment holds before rewriting it.
Watch out
one required value, the Shipment Id, and no other way in. Keep that ID somewhere when the shipment is created.
3

Get Stop Details

Search

In Zapier“Get Stop Details”

Fetches a single stop by its Stop Id and returns what Locate2u knows about it.

When to use it
a Zap holds a stop ID from an earlier step and needs the full stop to write a clear message or log entry.
Watch out
if nothing comes back and the first setting above is left on its default, the Zap stops at this step.
4

Get Team Member Details

Search

In Zapier“Get team member's details”

The only search that works from a name: give it a team member's name and it returns that person's record.

When to use it
another tool knows who should handle a job by name, and the next step needs the person as Locate2u knows them.
Watch out
whether the name must match exactly or roughly is decided by Locate2u, not Zapier, so test it with a real name first.

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 depend on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that offer it. Locate2u offers none, so you will not see it on these four searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Zapier attaches no help article of its own to Locate2u, so what breaks here are the limits every Zap shares.

None of them is specific to Locate2u. Each one has a symptom you can spot: a Zap that ran less than expected, or far more. If a Zap misbehaves in a way these cards do not explain, the Zapier troubleshooting page is the next stop.

  • Nothing from before the Zap was switched on

    A Zap only reacts to what happens after it is published. Stops that changed status yesterday are not picked up, and moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that starts on Stop Status Change and then writes to the stops it watches can trigger itself again and again, and the task count drops fast.

  • A sudden flood held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.
Need help

Need help automating Locate2u with Zapier?

A person reads every message.

FAQ

Locate2u Zapier integration: questions people ask

01Is the Locate2u Zapier integration free?
Yes, on the free plan, with one condition. Locate2u is not a premium app, so it works from the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan only builds two-step Zaps, one trigger and one action. A stop status change that creates one row somewhere fits. Add a filter, a search such as Get Order Details, or a second action, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Locate2u Zap use?
One task per action that succeeds, and nothing else. The Stop Status Change trigger never costs a task, and neither do the checks for new data. A Zap that only runs Create Stop uses one task each time it goes through. Put Get Order Details in front of Update Order and the Zap becomes multi-step, so it needs a paid plan. An action that fails is not counted against your plan, which also means the work it should have done simply did not happen.
03Is the Locate2u trigger real time?
Yes. Stop Status Change is an instant trigger: Locate2u calls Zapier as soon as a stop changes status, and the Zap starts right away, on every plan including the free one. The interval grid of the plans, from 15 minutes on Free down to 1 minute on Team and Enterprise, only concerns polling triggers, and Locate2u has none. The type is set by the app itself and cannot be changed from the editor, so there is nothing to tune here.
04What does it take to connect Locate2u to Zapier?
A Locate2u account and a Zapier account. The connection starts from the Apps page with + Add connection, then a sign-in on Locate2u in a new tab and an access approval. If the stops, orders or shipments the Zap will touch belong to someone else in the account, read or write access to them is needed first. After that, the same connection serves every step of every Zap that uses Locate2u, without signing in again for each one.
05Why does an Update Order step keep failing?
Most of the time, because a required value is missing. Update Order needs the Order ID plus the purchase order number, the shipping address and the order date, even if only one of them changes. If the step before it does not carry the Order ID, there is nothing to point at. The same logic applies to Update Shipment, which wants two stop identifiers on top of the Shipment ID. Failed attempts cost no task, but the order stays as it was.
06What if the Locate2u operation needed is not on Zapier?
Then it is not available, for now. Zapier offers exactly 11 Locate2u operations: 1 trigger, 6 actions and 4 searches. There is no delete action, no trigger on new orders or shipments, and nothing about routes or live location. Sometimes a search covers the gap: Get Stop Details or Get Shipment Details can fetch a value no earlier step carried. Before building, check that each step of your plan maps to one of these 11 operations.
07Zapier, Make or n8n for Locate2u?
It depends on a few criteria rather than on a winner. First, availability: this page only covers what Locate2u publishes on Zapier, so check whether the other platforms offer it at all. Second, the trigger: on Zapier the Locate2u trigger is instant on every plan, which matters if you are on the free tier. Third, the shape of your Zaps: anything beyond two steps needs a paid Zapier plan. Fourth, who maintains it, and which tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations