Resources · Zapier integration

Logisav Zapier integrationAutomate Logisav with Zapier.

The Logisav Zapier integration gives you 7 triggers, 5 actions and 3 searches. All seven triggers are checked on a timer, and Logisav is not a premium app, so it runs on the free plan. Here is what each piece does, what it bills and where it breaks.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Logisav Zapier integration does for your customer records

The Logisav Zapier integration connects your Logisav records to your other tools through Zaps: small automations that start on one event, then run one or more steps on their own. Logisav is a business tool built around contacts, addresses, contracts and tickets; Zapier carries those records in and out.

Three results come up most. Contacts that arrive on their own: someone fills in a form elsewhere and Create Contact adds them to Logisav. Opportunities nobody misses: New Opportunity picks one up and your team chat hears about it. Requests turned into tickets: a request collected in another tool becomes a Logisav ticket with Create Ticket, already set to the right status.

What Zapier does not do here: there is no update and no delete, so a Zap can add records but never change or remove one. The searches cover addresses, contacts and owners only, not contracts or opportunities. And all seven triggers are polling ones: on the free plan, Zapier checks every 15 minutes, never at once.

One trap is worth knowing up front. A Zap that writes where its own trigger watches restarts itself: New Contact followed by Create Contact is a loop.

Still comparing tools? See our Zapier review and our n8n vs Zapier comparison. Hack'celeration has no Logisav page for Make or n8n yet.

Vocabulary

Zapier vocabulary, explained plainly

Seven words carry this page. Here they are, in plain English.

Zap
An automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is 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 in an app for you.
Task
The unit Zapier bills. One action that completes successfully counts as one task on your plan.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Cost

What Logisav costs you in Zapier tasks

The trigger is free, and so is every check Zapier runs to look for new records. You pay one task for each action that succeeds. An action that fails is not counted.

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

The free plan gives 100 tasks a month and Zaps of two steps: one trigger, one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. Find Address before Create Event, for example, already makes three steps. A few apps bill more than one task per action; nothing in the catalog says Logisav does. The grid below sets how often the seven Logisav triggers are checked.

Connect

Connect Logisav to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Logisav account linked once, then reused by every step that talks to Logisav.

  2. 02

    Pick Logisav

    Search for Logisav in the dialog, select it and click Add connection. A new tab opens: sign in to Logisav with the account your Zaps should act on behalf of.

  3. 03

    Grant access

    Allow Zapier to use that account. Check its rights before building: it needs read or write access on every record type you do not own and want a Zap to watch or create.

First Zap

Your first Zap: tell your team about new Logisav opportunities

GoalEach time an opportunity is created in Logisav, keep only the ones that meet your condition and post a message in your team chat.

  1. 01

    Build: set the trigger

    Create a Zap, pick Logisav and the New Opportunity event, then select your connection. This trigger has no required field to fill.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent opportunities of the account, so you set the next steps on a real one rather than on blanks.

  3. 03

    Add a filter

    Add a Filter step and fill its three boxes: the field to look at, the rule, the value. A text rule only works on text, a number rule only on numbers.

  4. 04

    Add the message

    Add your team chat as the action and build the message from the opportunity's values. With the filter, this Zap is multi-step and needs a paid plan.

  5. 05

    Test, then publish

    Test each step and read the message that arrives. Then click Publish: the Zap switches on and reports opportunities created from now on.

Triggers

Logisav triggers in Zapier

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

1

New Address

Polling trigger

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

Starts the Zap whenever an address record is created in Logisav, and passes its details to the next steps.

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
a spreadsheet of sites or customer addresses kept outside Logisav should follow every addition.
Watch out
a Zap that answers this trigger with Create Address writes where it watches, and the next check starts it again, in a loop that eats your tasks.
2

New Contact

Polling trigger

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

Picks up each contact added to Logisav, whoever created it, and hands it to the Zap.

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
your mailing tool should receive every new Logisav contact without anyone exporting a list.
Watch out
contacts created before the Zap was published are never picked up; moving them is a separate job.
3

New Contract

Polling trigger

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

Fires when a contract is created in Logisav, so the people who act on it hear about it without opening the app.

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
each new contract should land as a row in a shared tracking sheet.
Watch out
there is no action to create or change a contract from Zapier; this trigger only reads what happens in Logisav.
4

New Event

Polling trigger

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

Reacts to each event created in Logisav, the kind linked to an address with a start and an end.

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
the events planned in Logisav should also appear in your calendar.
Watch out
pairing it with Create Event in the same Zap creates a loop, since every event the Zap adds is new to the trigger.
5

New Opportunity

Polling trigger

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

Runs when Zapier's next check finds an opportunity that did not exist before in Logisav.

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
a new sales lead should reach the person who follows it up, through your team chat.
Watch out
Logisav offers no search for opportunities, so later steps can only use what this trigger hands over.
6

New Owner

Polling trigger

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

Starts on each owner record added to Logisav and hands that record to the next steps.

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
another tool that bills or reports per owner needs the new entry too.
Watch out
do not answer it with Create Owner in the same Zap; the owner created would start the Zap again.
7

New Supplier

Polling trigger

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

Fires each time a supplier is created in Logisav, which makes it the only way into Zapier for supplier data.

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
your purchasing spreadsheet should list every new supplier without double entry.
Watch out
there is no action or search for suppliers, so Zapier can read new ones but never create or look one up.
Actions

Logisav actions in Zapier

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

1

Create Address

Action

In Zapier“Creates an address”

Creates an address record, named for example after a company, with street, postal code, city, phone and email.

When to use it
a new site recorded in another tool needs its Logisav address before any event can be linked to it.
Watch out
all six fields are required and the email must be valid, so check the source collects each one.
2

Create Contact

Action

In Zapier“Creates a contact”

Adds a contact to Logisav with a name, a phone number and an email.

When to use it
people who fill in your website form should become Logisav contacts without retyping.
Watch out
Name, Phone and Mail are all required, and Mail must be a valid email address, so make sure your form collects all three.
3

Create Event

Action

In Zapier“Creates an Event”

Creates an event linked to an address, with a start and an end date and time.

When to use it
a booking made in another tool should appear as a Logisav event at the right address.
Watch out
Address Id is required; it is the number at the end of the address page URL, or what Find Address returns.
4

Create Owner

Action

In Zapier“Creates an owner”

Creates an owner record with the same set of details as an address: name, street, postal code, city, phone and email.

When to use it
a new owner signed up elsewhere should exist in Logisav straight away.
Watch out
run Find Owner first, or the same owner can be created twice.
5

Create Ticket

Action

In Zapier“Creates a ticket”

Opens a ticket with a title and a status, ready for your team to handle in Logisav.

When to use it
a request sent through a form should become a ticket without anyone copying it.
Watch out
Status takes a number, 0 for standby, 1 for ongoing, 2 for event created, 3 for closed; send one of those four values, not a word.
Searches

Logisav searches in Zapier

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

A search step looks something up in Logisav and hands the result to the steps after it. In the editor, the three Logisav searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when a lookup goes sideways.

1

Find Address

Search

In Zapier“Finds an address”

Looks up an address that already exists in Logisav and passes it to the next steps, Address Id included.

When to use it
just before Create Event, so the event lands on the right address without anyone reading a URL.
Watch out
whether it wants an exact value or a close one is decided by Logisav, not by Zapier; test it with a real name.
2

Find Contact

Search

In Zapier“Finds a Contact”

Checks Logisav for a contact that is already there and returns what it found for the steps that follow.

When to use it
before Create Contact, to avoid adding the same person a second time.
Watch out
Logisav offers no find-or-create here, so a contact that is not found is not added for you; that takes a separate Create Contact step.
3

Find Owner

Search

In Zapier“Finds an owner”

Finds an owner record already stored in Logisav and makes its details available to the rest of the Zap.

When to use it
a message about a contract or an event should quote the owner's details.
Watch out
if several owners match, the default keeps the first one; check that setting when names look alike.

The three settings every search exposes

  1. Successful if no search results are found?
    On its default, a search that finds nothing stops the Zap and skips the steps that needed 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. Logisav offers no such variant, so none of its three searches shows it.
  3. If multiple search results are found?
    When several records match, you keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a Logisav Zap breaks

Zapier attaches no help article to Logisav, so the traps below are Zapier's general ones, read through this app.

On a polling trigger Zapier remembers what it has already seen, so the same contact does not start the Zap twice. Four other cases are worth planning for. If a Zap still misbehaves, see our Zapier troubleshooting page.

  • Old records are not picked up

    A Zap only reacts to what is created after you publish it. Contacts, contracts and addresses already in Logisav stay out; moving that backlog is a separate job.

  • A Zap that sets itself off

    New Contact followed by Create Contact, or New Event followed by Create Event, writes where the trigger watches: the Zap restarts and burns your tasks.

  • A bulk import held back

    After a migration or a mass import into Logisav, a sudden pile of new records can trip Zapier's flood protection, which holds the batch back instead of running it.

  • A search finds nothing

    If Find Address returns nothing, Create Event has no Address Id. On default settings the Zap stops at the search and the event is never created.
Need help

Need help automating Logisav with Zapier?

A person reads every message.

FAQ

Logisav Zapier integration: frequent questions

01Is the Logisav Zapier integration free?
On the Zapier side, yes. Logisav is not a premium app, so it works on the free plan, with 100 tasks a month and as many Zaps as you like. Each Zap must stay at one trigger and one action there. New Opportunity followed by one chat message fits. Put Find Owner in between, or a filter, and the Zap becomes multi-step, which needs a paid plan. Your Logisav subscription is a separate matter that Zapier does not cover.
02How many tasks does a Logisav Zap use?
One per action that succeeds, none for the trigger. A Zap where a web form feeds Create Contact uses one task per new contact. Add Find Contact in front to avoid duplicates and the Zap becomes multi-step, with each step counted on its own. Zapier's checks for new records cost nothing, however often they run, and a failed step is not billed. Size your plan on how many records actually go through.
03Does Logisav trigger Zaps in real time?
No. All seven Logisav triggers are polling triggers. Zapier checks for new records at an interval set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can change how often it checks and run a check by hand from the editor. The trigger type comes from Logisav itself and cannot be switched to instant from the editor, whatever your plan.
04What does it take to connect Logisav to Zapier?
A Logisav account, plus read or write access on every record type you do not own and want a Zap to watch or create. In Zapier, open the Apps page, click + Add connection, search for Logisav, click Add connection, sign in in the tab that opens and grant access. The connection is made once and reused by every Logisav step. Check that the account can open the addresses your events will be linked to.
05Where do you find the Address Id that Create Event needs?
In the address page of Logisav, or from a search. Address Id is required on Create Event, and it is the number shown at the end of the browser URL of the address, for example 111. Typing it by hand only works for one fixed address. For a Zap that handles many, add Find Address before Create Event and map the ID it returns. Test the chain once with a real address before publishing.
06What if the Logisav operation you need is not in Zapier?
Then the editor will not offer it: the catalog holds 15 visible operations, 7 triggers, 5 actions and 3 searches. There is no update, no delete, and nothing that creates a contract, an opportunity or a supplier. A chain of existing steps covers some needs, for example Find Contact then Create Contact to add a person only once. Anything else stays manual in Logisav or moves to another automation tool.
07Zapier, Make or n8n for Logisav?
Compare them on criteria, not on a ranking. Coverage first: Zapier offers 7 polling triggers, 5 actions and 3 searches for Logisav, so check that another tool exposes the operations your process depends on. Billing next: Zapier counts one task per successful action, which is easy to forecast when volume is steady. Then reaction time: every Logisav trigger here waits for the next check. Hack'celeration has no Logisav page for Make or n8n, so this page only covers Zapier.
Same platform

Other docs you might need on this stack.

Browse all integrations