Resources · Zapier integration

LASSO Zapier integrationAutomate LASSO with Zapier.

LASSO Zapier integration: 11 triggers (7 instant, 4 polling), 35 actions and 34 searches for an event company's quotes, invoices, crew, events and subrentals. Here is what each step does, what it costs in tasks and where it tends to break.

See the 80 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LASSO Zapier integration does for an event company

The LASSO Zapier integration connects LASSO, the platform event companies use to run crew, inventory, finance and projects, to the rest of your tools without code. A quote, an invoice or a payment moves in LASSO, and Zapier carries the news elsewhere. Or another tool changes, and Zapier writes it into LASSO.

Three results come up most. First, a staffed show the minute it is sold: Quote Accepted starts the Zap, Find Event picks up the event, and Assign Event Role names the project manager. Second, finance in step with accounting: a payment logged in your accounting tool becomes Create Invoice Payment in LASSO, and New Payment Recorded. can feed the other direction. Third, a crew roster that builds itself: a new hire in your HR tool becomes Create Crew, then Assign Crew to Event Position puts them on a show.

What it does not do. There is no dedicated delete action, and the one step that removes anything, the bulk order update, deletes order lines by side effect. New and updated events reach Zapier by polling, not instantly. Draft quotes stay invisible until they are saved. And anything outside the ready-made steps goes through API Request (Beta), which is meant for someone technical.

Comparing platforms for the same job? See our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier words in one minute

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

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event to occur.
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 task is one action your Zap completes successfully; your plan counts those and nothing else.
Instant vs polling
An instant trigger is pushed by the app when the event happens. A polling trigger is checked by Zapier on a timer set by your plan.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up a record already in an app, like an event or a crew member, so later steps can use what it found.
Cost

What a LASSO Zap really costs

LASSO is not a premium app, so it runs on the Free plan. Zapier bills tasks, and only actions that succeed count.

  • Free plan100 tasks per month, unlimited Zaps
  • Zap size on FreeTwo steps: one trigger, one action
  • LASSO triggers7 instant, 4 polling
  • Premium appNo

Triggers never cost a task, however often Zapier checks for new events. Each successful action counts on its own, so a three-action Zap uses three times what a one-action Zap does, and failed actions are free. The Free plan stops at two-step Zaps: add a filter, a search or a second action and you need a paid plan. Most LASSO flows need a search to find an event or a crew ID, so plan for that. The interval grid applies to the 4 polling triggers only.

Connect

Connect your LASSO account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your LASSO account linked to Zapier once, then reused by every step that touches LASSO.

  2. 02

    Pick LASSO in the dialog

    Type LASSO in the dialog's search box, select it and click Add connection. A new tab opens on the LASSO sign-in screen. Use an account that can see the events, crew and invoices you plan to automate.

  3. 03

    Sign in and grant access

    Log in to LASSO in that tab and allow Zapier to reach the account. Beyond your own records, the Zap can only read or change what this account already has read or write access to.

First Zap

Your first Zap: staff a show as soon as the quote is accepted

GoalWhen a client accepts a quote, the matching LASSO event gets its project manager without anyone opening the event.

  1. 01

    Create the Zap

    Start a new Zap. It reads top to bottom: the app and event that start it, then the steps that follow, with fields mapped from one step to the next.

  2. 02

    Set the trigger

    Pick LASSO, then Quote Accepted. Test it: Zapier brings back the three most recent items of your account, so you work on a real accepted quote.

  3. 03

    Find the event

    Add Find Event. Choose the field that identifies the event and map the event from the quote. This search step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Assign the role

    Add Assign Event Role, map the event found above, pick Project Manager as the role and identify the crew member by email or employee code.

  5. 05

    Test and publish

    Run each step once and check the event in LASSO. When the role shows up, click Publish to switch the Zap on for every accepted quote.

Triggers

LASSO triggers: what starts a Zap

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

1

List Client Addresses

Polling trigger

In Zapier“Triggers when a new client address is added or updated.”

Starts the Zap when a client address is added in LASSO, and also when an existing one is edited. The address then flows to your CRM, your shipping tool or a mailing list.

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
keeping delivery and billing addresses identical in LASSO and in the tool your logistics team uses.
Watch out
edits fire it too, so a Zap that creates records downstream should search before it creates, or you will get duplicates.
2

List Client Contacts

Polling trigger

In Zapier“Triggers when a new client contact is added or updated.”

Watches the contacts attached to your clients and fires on each new contact as well as on each update to an existing one.

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
pushing every producer or venue manager your sales team adds in LASSO into your email marketing list.
Watch out
every edit to a contact can start a new run; a filter or a search in your other app keeps the list clean.
3

New Event

Polling trigger

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

Fires once for every event created in LASSO, which makes it the natural start for anything that should exist as soon as a show is on the books.

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
opening a project channel, a shared folder or a task list in another tool for each new event.
Watch out
events created before the Zap was published are never picked up afterwards.
4

Updated Event

Polling trigger

In Zapier“Triggers when an event is created or updated.”

Catches an event when it is created and every time it changes afterwards: dates, venue, status or any other edit.

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
keeping a calendar or a planning sheet outside LASSO in step with date changes.
Watch out
if your Zap uses Update Event on the same event, it changes what this trigger watches and can set itself off again.
5

New LASSO Invoice

Instant trigger

In Zapier“Triggers when a new invoice is sent.”

Reacts when an invoice is sent from LASSO, not when it is drafted, so what reaches your other tools is a bill the client already has.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
copying each sent invoice into your accounting software, or alerting the finance channel in your team chat.
Watch out
invoices sent before you switched the Zap on stay where they are; moving that backlog is a separate job.
6

New Payment Recorded.

Instant trigger

In Zapier“Triggers when a new payment record is created.”

Goes off each time a payment record is created in LASSO, whoever entered it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
marking the invoice paid in your accounting tool, or thanking the client by email the minute the money is logged.
Watch out
if another Zap writes payments into LASSO with Create Invoice Payment, those payments fire this trigger too, so make sure the two Zaps do not answer each other in a loop.
7

Quote Accepted

Instant trigger

In Zapier“Triggers when a quote status changes to Accepted, whether the customer accepted it or it was set manually. Delivers the quote summary (number, status, totals, event, customer) plus the accepted timestamp. Use the Find Quote action for the full quote detail.”

Fires when a quote's status turns to Accepted, whether the client clicked accept or someone on your team changed it by hand. It brings the quote summary, the event and customer, and the time of acceptance.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
starting staffing, deposits or contracts the moment a deal is won.
Watch out
you get a summary only; add Find Quote when a later step needs the full line detail.
8

New Quote

Instant trigger

In Zapier“Triggers when a quote is saved. Draft quotes do not fire until they are saved. Delivers the quote summary (number, status, totals, event, customer). Use the Find Quote action for the full quote detail.”

Kicks off when a quote is saved in LASSO, and hands over its number, status, totals, event and customer.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
logging each new quote in your CRM pipeline so sales can follow up.
Watch out
a draft does nothing until it is saved, so a quote someone is still building will not appear yet. For line-level detail, chain Find Quote after this trigger.
9

Quote Sent

Instant trigger

In Zapier“Triggers when a quote status changes to Sent, whether it was emailed to the customer or set manually. Delivers the quote summary (number, status, totals, event, customer). Use the Find Quote action for the full quote detail.”

Reacts as soon as a quote moves to Sent, either because LASSO emailed it to the client or because a teammate set the status manually.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
creating a follow-up task for the account manager in your task tool once the quote is out.
Watch out
a manual status change counts as sent, even if nothing left your outbox, so word your follow-ups with that in mind.
10

New Subrental (Purchase Order) Created

Instant trigger

In Zapier“Triggers when a new subrental (purchase order) is created. Includes full PO details (number, status, vendor, dates, totals, GL code breakdown) in the webhook payload. A subrental is also referred to as a purchase order (PO).”

Reacts to every new subrental, the gear you rent from another vendor, also called a purchase order. It carries the full purchase order: number, status, vendor, dates, totals and the breakdown by accounting code.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
creating the matching bill or purchase order in your accounting software.
Watch out
subrentals created before the Zap went live are not sent; only new ones count.
11

Subrental (Purchase Order) Updated

Instant trigger

In Zapier“Triggers when a subrental (purchase order) is updated. Includes full PO details (number, status, vendor, dates, totals, GL code breakdown) in the webhook payload. A subrental is also referred to as a purchase order (PO).”

Fires whenever an existing subrental changes, and sends the complete purchase order again with its vendor, dates, totals and accounting codes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping the copy of a purchase order in your accounting tool aligned when dates or amounts move.
Watch out
each edit is a run, so a purchase order adjusted many times in one afternoon spends a task per change on every action.
Actions

LASSO actions: what the Zap writes

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

1

Create Account Event Status

Action

In Zapier“Creates a new account event status.”

Adds a new status to the list your account uses to track where an event stands.

When to use it
rolling out a new stage of your sales process, say a status for holds, across the account from a central sheet.
Watch out
both the status name and its event status code are required.
2

Create Account Event Type

Action

In Zapier“Creates a new account event type.”

Registers a new kind of event, such as a conference or a festival, in your account settings.

When to use it
a new line of business needs its own type before events of that kind can be created.
Watch out
the name is the only required field and must stay between 1 and 255 characters.
3

API Request (Beta)

Action

In Zapier“Makes a raw HTTP request to the LASSO API, including authentication. Useful for endpoints this integration does not have a dedicated action for yet. Requires knowledge of the LASSO API.”

Sends a raw request to LASSO, with your connection's sign-in already attached, for anything the other steps do not cover.

When to use it
a developer on your team needs one specific LASSO function that has no ready-made step yet.
Watch out
it is in beta and you choose the method and path yourself, so it is not a beginner's step.
4

Assign Crew to Event Position

Action

In Zapier“Rosters a crew member onto a position on an event, resolving the crew member's position qualification automatically.”

Rosters a crew member onto a slot of an event, and LASSO works out their qualification for that position on its own.

When to use it
a crew member confirms availability in a form and lands on the show.
Watch out
pick the event first, because the position list depends on it, and create the slot beforehand with Create Event Position if it is missing.
5

Assign Event Role

Action

In Zapier“Assigns a crew member to an event as Project Manager, Supervisor, Account Manager, Crew Chief, or Timekeeper.”

Names someone as Project Manager, Supervisor, Account Manager, Crew Chief or Timekeeper on an event.

When to use it
the account manager who closed the deal should be set on the event automatically.
Watch out
you identify the person by a field you choose, such as email or employee code; email matching ignores capital letters and stray spaces.
6

Assign Labor Coordinator to Event

Action

In Zapier“Assigns a labor coordinator to an event in LASSO.”

Attaches a labor coordinator, a LASSO user rather than a crew member, to an event.

When to use it
each new event in a region should get that region's coordinator without a manual step.
Watch out
only coordinators with an email on their LASSO user profile can be picked, since the email is how they are identified.
7

Update Order (Bulk Action - Restricted Access)

Action

In Zapier“Only use on orders that do not have associated products, or components. Process a CSV file with product codes and quantities to update an order. Example CSV layout (Header must be exact): product_code,quantity,1234,5,5678,10. If the order line item already exists, the quantity will be updated, if different. If the order line item does not exist on the CSV file, it will be deleted from the order in LASSO.”

Rewrites the lines of an order from a CSV file of product codes and quantities, changing quantities where they differ.

When to use it
a packing list prepared in a spreadsheet should replace the order quantities in one go.
Watch out
any line missing from the CSV is deleted from the order, and the step is meant for orders without linked products or components.
8

Create Category

Action

In Zapier“Creates a new category.”

Sets up one more category in your LASSO account, ready to file records under.

When to use it
your catalogue lives in a spreadsheet or a product tool, and new categories created there should exist in LASSO too.
Watch out
run Find Category first, or its find-or-create variant, to avoid creating the same category twice.
9

Create Client Address

Action

In Zapier“Creates a new client address.”

Saves a new address on a client record in LASSO.

When to use it
a client fills an onboarding form with a billing or delivery address, and it should land in LASSO without retyping.
Watch out
the client ID and an airport are required, so a Find Client and a Find Airport step often come before it.
10

Create Client Contact

Action

In Zapier“Creates a new client contact with input from previous steps.”

Adds a person to a client's contact list, with details mapped from earlier steps.

When to use it
a new lead in your CRM becomes a contact on the right client in LASSO.
Watch out
type, client ID, first name and last name are all required, so a contact with only an email will not go through.
11

Create Client Note

Action

In Zapier“Creates a new client note.”

Writes a note on a client's record, kept with the rest of that client's file.

When to use it
logging a summary of each sales call or support ticket from another tool next to the client.
Watch out
the client ID is mandatory, so the step usually follows a Find Client search by name.
12

Create Client

Action

In Zapier“Creates a new client.”

Opens a new client record in LASSO from data gathered elsewhere.

When to use it
a deal marked won in your CRM should give the operations team a client file straight away.
Watch out
only the name is required, which makes duplicates easy; Find Client with its find-or-create option avoids them.
13

Create Event Note

Action

In Zapier“Creates a new event note using the event ID from a previous step.”

Pins a note with a subject, a body and a status on an event, using the event ID from an earlier step.

When to use it
recording on the event that the quote was accepted, with the totals, so the production team sees it.
Watch out
the event ID must be the numeric one; a trigger or Find Event provides it.
14

Create Invoice Payment

Action

In Zapier“Creates a new invoice payment.”

Records a payment against a LASSO invoice, with amount, payment type, date and the payment's ID in your accounting system.

When to use it
a payment cleared in your accounting software should mark the LASSO invoice as paid.
Watch out
run Find Invoice first; a voided payment needs a void reason, and a deleted one a deleted reason.
15

Create Crew

Action

In Zapier“Creates a new crew member.”

Adds a crew member to your LASSO roster.

When to use it
a technician signs up through your recruiting form and should be bookable right away.
Watch out
email, classification, US state of residence and postal code are required, so a form that skips any of them makes the step fail.
16

Create Department

Action

In Zapier“Creates a new department.”

Creates a department, one of the units LASSO uses to organize your teams and work.

When to use it
a new department set up in your HR or org-chart tool should appear in LASSO with the same name.
Watch out
check with Find Department first so a second Zap run does not create a twin.
17

Create Division

Action

In Zapier“Creates a new division.”

Creates a division in LASSO under the name you give it, the only field it requires.

When to use it
opening a new office tracked in your ERP should create the matching division.
Watch out
the division name is required; Find Division searches by name or external code if you need to check first.
18

Create Equipment Order

Action

In Zapier“Creates a new equipment order.”

Builds a new equipment order on an event, the list of gear going out for that show.

When to use it
rarely from scratch; mostly when another system already holds every detail of the order.
Watch out
it requires many fields, from warehouse and rate type to prep, leave, return and show dates plus discounts, so map them all before testing.
19

Create Event Group

Action

In Zapier“Creates a new event group.”

Adds a named group to an event, tied to a venue.

When to use it
a multi-room conference planned in a spreadsheet should get one group per room.
Watch out
the event ID, the group name and a venue ID are all required, so find the venue first.
20

Create Event Position

Action

In Zapier“Creates a new event position.”

Opens a position slot on an event, for example four stagehands needed in one group.

When to use it
the crewing needs of a show come from a planning tool and should become open slots in LASSO.
Watch out
it needs the event, group and position IDs, which Find Event, Find Event Group and Find Position provide, plus quantity and rate setting.
21

Create Event

Action

In Zapier“Creates a new event.”

Creates an event in LASSO with its name, venue and dates.

When to use it
a booking confirmed in your CRM or a client form should open the event for the operations team.
Watch out
begin and end dates must be text in the YYYY-MM-DD format; a date in any other shape is rejected, so format it first.
22

Create Event Role

Action

In Zapier“Creates a new event role.”

Assigns a role on an event to a crew member identified by their numeric crew ID.

When to use it
you already hold the crew ID from an earlier step and simply want the role set.
Watch out
unlike Assign Event Role, it does not look the person up by email or code, so the ID must be right.
23

Create Order Group

Action

In Zapier“Creates a new order group.”

Adds an order group, a section that keeps related lines of an order together.

When to use it
splitting an order into audio, lighting and video sections built from another planning tool.
Watch out
Find Order Group and its find-or-create variant help you avoid a duplicate group when the Zap runs again.
24

Create an Order Line Item

Action

In Zapier“Creates a new order line item.”

Adds a single line to an existing order.

When to use it
a client confirms one extra item through a form, and it should appear on the order without retyping.
Watch out
each run of this action adds one line and bills one task, so several lines mean several actions in the Zap.
25

Create Position

Action

In Zapier“Creates a new position.”

Defines a new job position, such as rigger or camera operator, in your LASSO account.

When to use it
your skills list is maintained in an HR tool and new roles should exist in LASSO too.
Watch out
the short name is an abbreviation that must be unique across all positions, so reuse fails.
26

Create Product

Action

In Zapier“Creates a new product.”

Adds a product to your LASSO inventory catalogue.

When to use it
new gear bought and logged in a purchasing tool should be available for orders.
Watch out
Find Product searches by ID only, so keep the product ID from this step if later Zaps need to find it.
27

Create Product Tag

Action

In Zapier“Creates a new product tag.”

Creates a tag that can label products, for grouping and filtering your inventory.

When to use it
a tag scheme decided in a spreadsheet should be rolled out to LASSO in one pass.
Watch out
Find Product Tag works from an ID, so it cannot tell you whether a tag with the same name already exists.
28

Create Schedule Entry

Action

In Zapier“Creates a new schedule entry.”

Places a shift on the schedule of an event position, with date, start and end.

When to use it
call times planned in a spreadsheet should become schedule entries in LASSO.
Watch out
start and end times use the HH:MM:SS format without the date, and an external code is also required.
29

Create Tag

Action

In Zapier“Creates a new tag.”

Registers a plain tag in your LASSO account, separate from the product tags above.

When to use it
a tag such as a client tier, set in your CRM, should also exist in LASSO.
Watch out
pair it with Find Tag or its find-or-create variant so repeated runs do not create duplicates.
30

Update Event

Action

In Zapier“Update an event in LASSO”

Changes an existing event, its dates and its display options such as hiding the client or the event name.

When to use it
dates moved in your booking tool should move in LASSO too.
Watch out
begin and end dates are required on every update, in YYYY-MM-DD, even if only another field changes.
31

Update Invoice Payment

Action

In Zapier“Update an Existing Invoice Payment.”

Edits a payment already recorded in LASSO, including marking it void or deleted.

When to use it
a refund or a cancelled transfer in your accounting tool should correct the LASSO payment.
Watch out
you need the payment ID, which Find Payment returns, and voiding or deleting needs a reason.
32

Update Position

Action

In Zapier“Update a position in LASSO”

Modifies a job position already defined in LASSO.

When to use it
a role renamed in your HR tool should be renamed in LASSO the same day.
Watch out
the position ID and the short name are required, and the short name must stay unique across all positions.
33

Update Schedule Entry

Action

In Zapier“Update an existing schedule entry in LASSO”

Edits a shift already on an event schedule.

When to use it
a call time pushed back in your planning sheet should update the matching entry.
Watch out
only the entry's ID is required, but you need it at hand; Find a Schedule Entry can fetch it before this step.
34

Create Venue

Action

In Zapier“Creates a new venue.”

Adds a venue to LASSO with its name, city, region, nearest airport and postal code.

When to use it
a new venue entered in your CRM should be selectable for events.
Watch out
all five of those fields are required, and the airport must be its code; Find Airport looks it up from a postal code.
35

Create Warehouse

Action

In Zapier“Creates a new warehouse.”

Sets up a new warehouse, a place where your gear is stored and shipped from.

When to use it
opening a storage site recorded in your ERP should create it in LASSO for equipment orders.
Watch out
check with Find Warehouse first, which needs a search field and a value, to avoid a duplicate site.
Searches

LASSO searches: finding the record a step needs

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

A search step looks up a LASSO record and hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH. Each one adds a step, so the Zap becomes multi-step and needs a paid plan. 24 of these searches also appear in the editor as a Find or Create line: that is the same search with the create box ticked, not an extra operation.

1

Find Account Event Status

SearchFind or create

In Zapier“Finds an account event status based on name.”

Looks up an event status of your account by its name and returns it for later steps.

When to use it
before setting a status on an event, to get the exact record LASSO expects.
Watch out
the editor also lists Find or Create account event status, which is this same search set to create the status when the name is unknown.
2

Find Account Event Type

SearchFind or create

In Zapier“Finds an account event type by ID or name.”

Finds an event type of your account, either by its ID or by its name, chosen in the Search By box.

When to use it
mapping a type name from a booking form to the LASSO type before creating the event.
Watch out
Find or Create Account Event Type is this search with the create option ticked, not a separate step.
3

Find Airport

Search

In Zapier“Finds an airport based on postal code.”

Returns the airport that matches a postal code, which LASSO uses on venues and client addresses.

When to use it
just before Create Venue or Create Client Address, which both require an airport.
Watch out
there is no find-or-create version, so an unknown postal code simply returns nothing.
4

Find Category

SearchFind or create

In Zapier“Finds a category.”

Checks whether a category already exists in your LASSO account and returns it.

When to use it
any Zap that files products under a category coming from another catalogue.
Watch out
its variant Find or Create Category creates the category when nothing matches; it is the same search, so it adds no operation to the count.
5

Find Client Addresses

SearchFind or create

In Zapier“Finds client addresses based on search criteria.”

Lists the addresses of a client that match your search criteria.

When to use it
checking whether a delivery address from an order form is already on file before adding it.
Watch out
Find or Create Client Address is the same search ticked to create the address when none matches, which avoids duplicates in one step.
6

Find Client Contacts

SearchFind or create

In Zapier“Finds client contacts based on search criteria.”

Searches the contacts of one client, identified by its client ID, which is required.

When to use it
finding the right producer on a client before sending them a message from another app.
Watch out
Find or Create Client Contact reuses this search and creates the contact when it is missing; you then supply the fields a new contact needs.
7

Find Client Note

SearchFind or create

In Zapier“Finds a client note by ID.”

Fetches one client note from its ID, which is the only way this search works.

When to use it
you kept a note ID from an earlier run and need its content again.
Watch out
the editor also shows Find or Create Client Note; it is this search set to create a note when the ID returns nothing.
8

Find Client

SearchFind or create

In Zapier“Finds a client based on name.”

Looks up a client by the field you choose in Search By, typically the name, and returns its ID.

When to use it
the step before almost any client action, since they need a client ID.
Watch out
Find or Create client is this search with creation switched on, the cleanest way to avoid duplicate clients from a CRM.
9

Find Crew

SearchFind or create

In Zapier“Finds a crew member based on ID, external code, or email.”

Finds a crew member from their ID, their external code or their email, picked in the Search By box.

When to use it
matching a technician from your HR or payroll tool to their LASSO record.
Watch out
Find or Create Crew is this same search set to create the crew member when no one matches.
10

Find Department

SearchFind or create

In Zapier“Finds a department.”

Retrieves a department from its department ID, which the search requires.

When to use it
confirming a department before linking crew or work to it.
Watch out
since it searches by ID, it cannot tell you whether a department of the same name exists; Find or Create Department is this search with creation ticked.
11

Find Division

SearchFind or create

In Zapier“Finds a division based on external code or name.”

Locates a division by its external code or its name, chosen in the Search By box.

When to use it
mapping a branch code from your ERP to the matching LASSO division.
Watch out
Find or Create Division is this search set to create the division when the code or name is unknown.
12

Find Equipment Order

SearchFind or create

In Zapier“Finds an equipment order based on the search criteria.”

Finds equipment orders from a field you pick in Search By.

When to use it
getting the order of an event before a bulk update or before adding line items.
Watch out
its variant Find or Create Equipment Order would create an order, and an order requires many fields, so only tick it if you can map them all.
13

Find Event Group

SearchFind or create

In Zapier“Finds an event group for a given event ID and group name.”

Returns the group of an event that matches an event ID and a group name.

When to use it
supplying the group ID that Create Event Position requires.
Watch out
Find or Create Event Group is this search ticked to create the group when it is missing.
14

Find Event Position

SearchFind or create

In Zapier“Finds an event position.”

Confirms whether a position slot already exists on an event.

When to use it
before rostering someone, to confirm the slot is there and get its ID for the schedule.
Watch out
Find or Create Event Position reuses this search and opens the slot when none matches.
15

Find Event

SearchFind or create

In Zapier“Finds an event based on the selected search field.”

Retrieves the event matching the field you choose, then returns the record that later steps can map.

When to use it
right after New Event or Updated Event: pick the LASSO event ID as the search field and map the ID the trigger delivered.
Watch out
Find or Create Event is this same search set to create the event when nothing matches, with the dates and venue that requires.
16

Find Updated Crew

Search

In Zapier“Finds crew updated after a specified date and time.”

Returns crew members whose record changed after a date and time you set.

When to use it
sending the crew records changed since a given date to your payroll tool.
Watch out
it can return several people, so the multiple-results setting decides whether you get the first one only or all of them.
17

Find Event Note

Search

In Zapier“Finds an event note using the ID.”

Retrieves an event note from its ID.

When to use it
reading back a note your Zap created earlier, to copy it to a client report.
Watch out
the note ID is required, and you may need to get it from the event record first.
18

Find Event Role (With Crew Details)

SearchFind or create

In Zapier“Finds who holds a role on an event — Account Manager, Project Manager, Supervisor, Crew Chief, Timekeeper, or Labor Coordinator — and returns their name and contact details. Labor coordinators are LASSO users rather than crew members, so those results carry an email but no Crew ID, name, or Employee Code; the Role Source field says which kind of record a result came from.”

Tells you who holds a role on an event, with their name and contact details, or everyone attached when you choose any role.

When to use it
emailing the crew chief of a show from another app.
Watch out
labor coordinators come back with an email but no crew ID. Its variant Find or Assign Event Role assigns a crew member when the role is empty.
19

Find Invoice

Search

In Zapier“Finds an invoice based on search criteria.”

Finds one or more invoices from the field you pick in Search By.

When to use it
the required step before Create Invoice Payment, which needs the invoice ID.
Watch out
since several invoices can match, set the multiple-results option on purpose rather than trusting the first result blindly.
20

Find Payment

Search

In Zapier“Finds a payment based on name.”

Tracks down a payment through the field you choose in Search By.

When to use it
fetching the payment ID before Update Invoice Payment voids or corrects it.
Watch out
no find-or-create here, so a payment that cannot be found stops the Zap unless you allow empty results.
21

Find Product Image

Search

In Zapier“Finds a product image by image ID.”

Returns a product image from its image ID.

When to use it
attaching the picture of a product to a catalogue page or a client proposal built in another tool.
Watch out
it only searches by image ID, so you need that ID from an earlier step.
22

Find Subrental (Purchase Order)

Search

In Zapier“Finds a subrental (purchase order) by ID or lists subrentals with optional filters. Use the ID from the subrental webhook to fetch full details. A subrental is also referred to as a Purchase Order (PO).”

Fetches one subrental by its ID, or lists several with optional filters.

When to use it
after a subrental trigger, to pull its full details into the next steps.
Watch out
used as a list, it can return many purchase orders, so decide how the multiple-results setting should handle them.
23

Find Quote

Search

In Zapier“Finds quotes for an account with optional filters (event code, quote numbers, status, or date range). Returns a list of matching quotes.”

Lists the quotes of your account, with optional filters by event code, quote numbers, status or date range.

When to use it
after any quote trigger, when a step needs more than the summary it sends.
Watch out
drafts are hidden by default; tick Include Draft if you want them in the results.
24

Find Market

Search

In Zapier“Finds a market by ID. Markets are geographical areas used to determine crew "local" status for events.”

Returns a market from its ID. Markets are the areas LASSO uses to decide whether crew are local to an event.

When to use it
checking the market of an event before applying travel rules elsewhere.
Watch out
the market ID is required; there is no search by name.
25

Find Order Group

SearchFind or create

In Zapier“Finds an order group by search criteria.”

Finds an order group that matches your criteria.

When to use it
getting the group needed by Update Order (Bulk Action - Restricted Access), which requires one.
Watch out
Find or Create Order Group is this search ticked to create the group when it is missing, not a separate operation.
26

Find an Order Line Item

SearchFind or create

In Zapier“Finds an order line item by ID.”

Retrieves a single order line from its ID.

When to use it
reading back a line your Zap created, for example to confirm the quantity to the client.
Watch out
Find or Create Order Line Item reuses this search and adds the line when the ID returns nothing.
27

Find Position

SearchFind or create

In Zapier“Finds a position that matches the search criteria.”

Finds a job position from a search field and a value, both required.

When to use it
supplying the position ID that Create Event Position needs.
Watch out
Find or Create Position is this search with creation ticked; remember the new position will need a unique short name.
28

Find Product

SearchFind or create

In Zapier“Finds a product by ID.”

Pulls a product of your inventory from its ID.

When to use it
pulling product details into a proposal or a stock alert built in another app.
Watch out
it searches by ID only. Find or Create Product is the same search set to create the product when that ID matches nothing.
29

Find Product Tag

SearchFind or create

In Zapier“Finds a product tag by ID.”

Fetches a product tag from its ID.

When to use it
confirming that a tag stored in another system still exists before applying it.
Watch out
Find or Create Product Tag is this search ticked to create the tag, but a search by ID cannot detect a tag already named the same way.
30

Find a Schedule Entry

SearchFind or create

In Zapier“Finds a schedule entry.”

Locates an entry on an event schedule.

When to use it
fetching the entry ID right before Update Schedule Entry changes a call time.
Watch out
Find or Create Schedule Entry is the same search set to create the shift when nothing matches; it then asks for every required schedule field.
31

Search Updated Events

Search

In Zapier“Finds events updated within the specified date range. If no range is provided, returns events updated in the past 24 hours.”

Returns the events updated within a date range you set.

When to use it
gathering the events changed over a period, to send the list to the team in one message.
Watch out
leave the range empty and it returns only the events updated in the past 24 hours.
32

Find Tag

SearchFind or create

In Zapier“Finds a tag.”

Checks for a tag already defined in your account and returns it.

When to use it
any Zap that tags records from labels coming out of your CRM.
Watch out
its variant Find or Create Tag creates the tag when none matches; it is the same search, so it does not count as an extra operation.
33

Find Venue

SearchFind or create

In Zapier“Finds a venue based on search criteria.”

Finds a venue from the field you choose in Search By.

When to use it
supplying the venue ID required by Create Event Group, or checking a venue before creating an event.
Watch out
Find or Create Venue is this search set to create the venue, which then requires name, city, region, airport and postal code.
34

Find Warehouse

SearchFind or create

In Zapier“Finds a warehouse.”

Searches for a warehouse using a search field and a value, both required.

When to use it
getting the warehouse that the bulk order update and equipment orders require.
Watch out
Find or Create Warehouse is the same search with creation ticked, not an additional step in the count.

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 depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into its find-or-create variant: the setting above disappears and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Several matches: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a LASSO Zap breaks

Zapier attaches no help article to LASSO and publishes no LASSO-specific rate limit. What breaks comes from two places: how a few LASSO steps behave, and how Zapier works in general.

Six cases explain most failed or surprising runs. If one of them still blocks you, see our Zapier troubleshooting guide.

  • The bulk update deleted order lines

    Update Order (Bulk Action) removes every line that is missing from the CSV. Send the full list each time, never just the changes.

  • A draft quote never fired

    New Quote waits until the quote is saved, and Find Quote hides drafts unless you tick Include Draft. A draft is simply invisible to the Zap.

  • The Zap keeps setting itself off

    A Zap that runs Update Event on events watched by Updated Event changes what its own trigger looks at, fires again and burns through tasks.

  • Old records were not picked up

    A Zap only reacts to what happens after it is switched on. Existing events, quotes and invoices are never replayed; moving them is a separate job.

  • A big import was held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the runs back.

  • An edit did not start a second run

    On polling triggers Zapier remembers what it has already seen, so the same item does not start the Zap twice from one check.
Need help

Need help automating LASSO with Zapier?

A person reads every message.

FAQ

LASSO and Zapier: common questions

01Is the LASSO Zapier integration free?
Yes, within the Free plan limits. LASSO is not a premium app, so it works on Free, which gives 100 tasks per month and unlimited Zaps. The limit that matters is size: on Free a Zap holds one trigger and one action. Most LASSO actions need an ID found by a search first, such as an event, a client or an invoice, and that search makes the Zap multi-step, which requires a paid plan. Simple two-step flows, like a quote trigger feeding another app, do run on Free.
02How many tasks does a LASSO Zap use?
One task per successful action, and nothing for the trigger. A Zap that records each new invoice in your accounting tool uses one task per invoice. Add a team chat alert and each invoice costs two. Failed actions are not billed. Watch the triggers that fire on every edit: Subrental (Purchase Order) Updated runs again each time a purchase order changes, and each run pays for all its actions, so a busy purchase order can eat a good share of the 100 monthly tasks on Free.
03Is LASSO to Zapier real time?
Partly. Seven triggers are instant: New LASSO Invoice, New Payment Recorded, Quote Accepted, New Quote, Quote Sent and the two subrental triggers. LASSO tells Zapier the moment they happen, whatever your plan. The other four, List Client Addresses, List Client Contacts, New Event and Updated Event, are polling: Zapier checks every 15 minutes on Free, every 2 on Professional and every minute on Team and Enterprise. If timing matters, build on the quote and invoice triggers.
04What does connecting LASSO to Zapier require?
A LASSO account, plus read or write access to the records you do not own but want the Zap to touch. The connection takes three moves: add it from the Apps page, sign in to LASSO in the tab that opens, and grant access. One prerequisite catches people later: Assign Labor Coordinator to Event only lists coordinators whose LASSO user profile has an email address, so check those profiles before you build that step.
05Why did the LASSO bulk order update delete lines?
Because that is how the step works. Update Order (Bulk Action - Restricted Access) reads a CSV of product codes and quantities, updates the lines whose quantity changed, and deletes from the order any line that is not in the CSV. A file that lists only the changes therefore wipes the rest of the order. Send the full order every time, and keep the step for orders without linked products or components, as LASSO advises.
06What if the LASSO operation you need is missing?
Use API Request (Beta). It sends a request to LASSO with your connection's sign-in already attached, for functions that have no dedicated step yet. It is in beta and meant for someone technical: you choose the method and the path yourself. For anything less technical, chain a search and an existing action, since 34 searches cover most records an action needs. Removing records is the main gap, as no dedicated delete action exists.
07Zapier, Make or n8n for LASSO?
It depends on criteria, not on a ranking. Coverage: Zapier offers 80 ready steps for LASSO, including instant quote, invoice and payment triggers. Cost model: Zapier bills every successful action, and LASSO flows often chain a search and several actions, so volume adds up. Control: if your team is comfortable writing raw requests, API Request (Beta) covers gaps in Zapier, and other tools may expose similar options. Compare those three points against your monthly volume before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations