Resources · Zapier integration

Logytext Zapier integrationAutomate Logytext with Zapier.

The Logytext Zapier integration gives you 8 triggers, 1 action and 2 searches. All eight triggers are instant, so a driver message, a shared location, a rate or a quote request reaches your other tools as it happens, and Zapier can send messages back through Logytext.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Logytext Zapier integration does for dispatch

Logytext is a single place to talk to your drivers by SMS, with channels and departments, plus rate tools for drayage and OTR loads. The Zapier integration plugs it into the rest of your tools. A message, a location, a rate or a quote request in Logytext can start an automation, and another app can send a message through Logytext without anyone opening it.

Three results come up most. First, a written trail of every driver conversation: Incoming Message fires when a driver writes in a channel, and a row lands in a spreadsheet the office can search later. Second, quote requests that nobody misses: Quote Requested starts the Zap the moment a request comes in, and a note reaches whoever prices loads. Third, messages sent from another tool: when a job changes in your planning sheet, Send Message texts the driver through the right channel and department.

The rest follows the same idea. Incoming Location passes on a position a driver shares, the four rate triggers report a drayage or OTR rate as soon as it is calculated, and the two searches fetch a rate mid-Zap.

What Zapier does not do for Logytext: there is a single action, so it sends messages and nothing else. It cannot create a channel, a driver or a quote. If you need more than that, read n8n vs Zapier and Make vs Zapier before you build.

Vocabulary

Zapier words, in plain English

Eight words carry this page. Read them once, the rest follows.

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. Once the Zap is switched on, Zapier waits for that event and nothing else.
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. One task is one action your Zap completes successfully, and your plan counts those.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists, such as a rate, so the steps after it can use what it found.
Connection
Your Logytext account linked to Zapier once, then reused by every step of every Zap that works with Logytext.
Cost

What a Logytext Zap really costs

Logytext is not a premium app, so it runs on the free Zapier plan. Waiting for a driver message or a rate costs nothing: only an action that succeeds is billed as a task.

  • Premium appNo, the free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Instant triggers8 out of 8

The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter, a second action or a search step such as Find OTR Rate makes the Zap multi-step, and that needs a paid plan. A failed action is not counted. The interval grid below is for polling triggers; it does not apply to the eight Logytext triggers, which are all instant. A Zap that logs one driver message per run therefore costs one task per message, and nothing while the channel is quiet.

Connect

Connect your Logytext account in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Logytext account first, with access to the channels and departments the Zap will use.

  2. 02

    Pick Logytext

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

  3. 03

    Sign in and allow access

    Sign in to Logytext in that tab and grant Zapier access to the account. The connection then shows on your Apps page, ready for every Zap that uses Logytext.

First Zap

Your first Zap: every driver message in a log

GoalEach message a driver sends in Logytext adds a row to your spreadsheet, but only when it passes the filter you set.

  1. 01

    Create the Zap

    Start a new Zap in Zapier. Choose Logytext as the trigger app and Incoming Message as the event, then pick your Logytext connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so you map the next steps on a real driver message rather than empty fields.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then fill in the field, the rule and the value. A filter makes this a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the spreadsheet row

    Add your spreadsheet step and map the details of the driver message into its columns. Test the step, then open the sheet and check the row it wrote.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only messages received from now on will be logged; older conversations stay in Logytext.

Triggers

Logytext triggers

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

1

Drayage Rate Calculation in Logytext

Instant trigger

In Zapier“Triggers when a drayage rate is calculated in Logytext.”

Starts the Zap each time someone calculates a drayage rate inside Logytext. The rate and its details move on to the next step, so a price worked out in Logytext does not have to be copied by hand into another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a running sheet of every drayage rate your team has priced.
Watch out
rates calculated in Truckrates use a separate trigger, so pick the one that matches where the work is done.
2

Drayage Rate Calculation in Truckrates

Instant trigger

In Zapier“Triggers when a drayage rate is calculated in Truckrates.”

Fires when a drayage rate is calculated in Truckrates rather than in Logytext itself. Same kind of result, different place of origin, which matters if part of your team prices loads from there.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
collect Truckrates drayage results in the same place as those from Logytext.
Watch out
one Zap listens to one trigger, so covering both sources means building two Zaps.
3

Incoming Location

Instant trigger

In Zapier“Triggers when a location sent by a driver is received in a channel.”

Reacts when a driver shares a location that arrives in a channel. The position becomes data another tool can store or display, instead of a pin buried in a conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
record each shared position next to the job it belongs to in your planning sheet.
Watch out
it only fires when a driver actually sends a location; it does not track drivers on its own.
4

Incoming Message

Instant trigger

In Zapier“Triggers when a message sent by a driver is received in a channel.”

Every reply a driver sends lands here: the trigger goes off when a driver's message reaches a channel in Logytext. Whatever comes back from the road passes through it, so it is the natural start for a log or an alert.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
write each driver message into a searchable log, as in the first Zap above.
Watch out
busy channels mean many runs; a filter keeps only the messages you care about, but needs a paid plan.
5

OTR Rate Calculation in Logytext

Instant trigger

In Zapier“Triggers when an OTR rate is calculated in Logytext.”

An OTR rate calculated inside Logytext is what sets this one off. It hands the result to the next step, so the figure lands where your quotes or reports are prepared.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post each new OTR rate to the team chat as soon as it exists.
Watch out
this one only covers rates calculated in Logytext; Truck Rates has its own OTR trigger.
6

OTR Rate Calculation in Truck Rates

Instant trigger

In Zapier“Triggers when an OTR rate is calculated in Truck Rates.”

Fires when an OTR rate is calculated in Truck Rates. It is the twin of the Logytext version, for teams that work out part of their prices in that tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
feed Truck Rates OTR results into the same rate sheet as the rest.
Watch out
mixing results from both sources in one sheet works best with a column that says where each rate came from.
7

Outgoing Message

Instant trigger

In Zapier“Triggers when a message by a user is send in a channel.”

Runs the Zap when a user sends a message in a channel, the reverse of Incoming Message. It captures what your side told the driver, which completes the record of a conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a copy of instructions sent to drivers alongside their replies.
Watch out
a Zap built on this trigger that also uses Send Message will set itself off again with every message it sends.
8

Quote Requested

Instant trigger

In Zapier“Triggers when a quote is requested.”

Fires the moment a quote is requested in Logytext. A request that sits unseen loses value, so this trigger is about getting it in front of the right person straight away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alert the person who prices loads, in the tool they already watch.
Watch out
the Zap only sees requests made after you publish it; older ones stay in Logytext.
Actions

Logytext action

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

1

Send Message

Action

In Zapier“Sends a message in a channel.”

Sends a message through a Logytext channel, from the department you choose, to the recipient you map. It lets another tool talk to a driver without anyone opening Logytext.

When to use it
text a driver when their job changes in your planning sheet.
Watch out
Channel Type, Department and To are required, while Is message signed? is optional.
Searches

Logytext searches

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

A search step looks up a rate that Logytext can already work out, so the steps after it can use the figure. Searches sit at the bottom of the action list, under SEARCH. Any Zap with a search is multi-step and needs a paid plan.

1

Find Drayage Rate

Search

In Zapier“Finds a drayage rate based on pickup and delivery locations.”

Looks up a drayage rate from a pickup and a delivery location, and hands it to the next step. The Zap gets a price it did not carry when it started.

When to use it
attach a drayage rate to a request before a message goes out.
Watch out
Container size is required; without it the search cannot run.
2

Find OTR Rate

Search

In Zapier“Finds an OTR rate based on origin and destination markets.”

Finds an OTR rate between an origin market and a destination market. It brings a road rate into the middle of a Zap, where the next step can use it.

When to use it
price a lane mid-Zap before the result is written somewhere else.
Watch out
Load type is required, so the trigger or a fixed value must provide it.

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 and skips the steps that relied on it. Switched on, the Zap carries on without the rate.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Logytext offers no find-or-create, so it does not apply to these two rate searches.
  3. If multiple search results are found?
    Three ways out when several results match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Logytext Zap breaks

Zapier links no help article to Logytext, and no app-specific limit is on record. The cases below come from how every Zap behaves.

Most failures are not bugs: the Zap does what it was told, at a moment nobody expected. For other cases, see our Zapier troubleshooting guide.

  • Old conversations never show up

    A Zap only reacts to what happens after you switch it on. Messages, locations and quotes from before stay in Logytext; moving them is a separate job.

  • The Zap keeps texting itself

    Outgoing Message plus Send Message in one Zap is a loop: each message sent counts as a new outgoing message and starts the Zap again, burning tasks.

  • A big burst goes quiet

    When a huge batch of events arrives at once, after an import or a migration, Zapier's flood protection can hold it back instead of running each one.

  • A rate search comes back empty

    If Find Drayage Rate or Find OTR Rate finds nothing, the Zap stops there by default and the steps that needed the rate are skipped.
Need help

Need help automating Logytext with Zapier?

A person reads every message.

FAQ

Logytext Zapier integration: questions people ask

01Is the Logytext Zapier integration free?
Yes, for simple Zaps. Logytext is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and two-step Zaps only: one trigger and one action. A driver message copied to a spreadsheet fits inside it. A filter, a second action or one of the two rate searches turns the Zap into a multi-step Zap, which needs a paid plan. Your Logytext account is separate from Zapier.
02How many Zapier tasks does a Logytext Zap use?
One task per action that succeeds, nothing for the trigger. A Zap that logs every driver message costs one task per message, so a busy channel adds up quickly against the 100 tasks of the free plan. Waiting for messages, locations or rates is free, and a failed action is not billed. If a single message also sends a reply through Send Message, that is two tasks for that message.
03Does Logytext trigger Zaps in real time?
Yes. All eight Logytext triggers are instant: Logytext tells Zapier the moment a message, a location, a rate or a quote request happens. The Zap starts right away on every plan, the free one included. The interval grid of Zapier plans only applies to polling triggers, and Logytext has none. In the editor, a Zap that starts on an instant trigger shows a lightning bolt. Nothing needs tuning on the Zapier side for that speed.
04What does it take to connect Logytext to Zapier?
A Logytext account and a Zapier account. On the Apps page of Zapier, click + Add connection, search for Logytext, click Add connection, then sign in to Logytext in the tab that opens and grant access. If the Zap must use channels or departments you do not own, your Logytext user needs access to them. The connection is then reused by every Logytext Zap you build. You do it once, not once per Zap.
05Why does Send Message refuse to send?
Because one of its three required fields is empty: Channel Type, Department or To. Pick the channel type and the department once in the step so every message uses them, and map To from a field that always holds a recipient. When the step fails, no task is billed, but the driver gets nothing, so test with a real recipient before you publish. Is message signed? is the only optional field, and leaving it blank never blocks the send.
06What if the Logytext operation you need is not in Zapier?
Then this integration does not offer it. Zapier lists eight triggers, one action and two searches for Logytext: it reads messages, locations, rates and quote requests, and it sends messages. Nothing creates a driver, a channel or a quote. Check first whether a search covers the need, since Find Drayage Rate and Find OTR Rate bring a rate into any Zap. If the gap is central, another automation tool may reach Logytext differently.
07Zapier, Make or n8n for Logytext?
It depends on the criterion that matters most. On setup, Zapier is short: three steps to connect, and all eight Logytext triggers are instant even on the free plan. On coverage, Zapier offers one action and two searches, so check what Make or n8n expose for Logytext before choosing. On cost, any Zapier Zap with a filter, a search or a second action needs a paid plan. Weigh those points rather than a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations