The LASSO Zapier integration connects your LASSO account to Zapier, opening the door to automation across event management, invoicing, payments, crew data, products, and more — with over 6,000 applications on the other side.
Full Set Up Walkthrough
Video Time Stamps:
What's included: 9 Triggers (including Invoice v2 and Subrental PO v2 webhooks), 32 Find Actions, 24 Create Actions, and 6 Update Actions.
Authentication
To connect your LASSO account to Zapier:
Sign in with LASSO credentials. Enter your LASSO username and password. Your user must have admin permissions in LASSO to connect.
Provide your subdomain. Enter your LASSO subdomain (e.g., yourcompany).
Select your environment. Choose Production or Sandbox.
💡 Pro Tip: Credentials are exchanged securely for API access — no manual API key entry is required. If connection fails, verify that your user has admin permissions and contact LASSO Support if needed.
Capabilities at a Glance
Use this table to quickly see what you can do with each object type.
Object | Triggers | Search/Find | Create | Update |
Client | — | Find Client | ✓ | — |
Event | — | Search Modified, Find Event | ✓ | ✓ |
Invoice | ✓ | Find Invoice | — | — |
Payment | ✓ | Find Payment | ✓ | ✓ |
Product | — | Find Product, Find Product Image | ✓ | — |
Purchase Order | ✓ (2) | Find Subrental (PO) — rarely needed in v4.1.0+ (full PO details now in trigger payload) | — | — |
Crew | — | Find Updated Crew | ✓ | — |
Venue | — | Find Venue | ✓ | — |
Position | — | Find Position | ✓ | ✓ |
Schedule Entry | — | Find Schedule Entry | ✓ | ✓ |
Triggers
Triggers are events that happen in LASSO that start a Zap. When these events occur, LASSO sends specific data to Zapier to use in subsequent steps.
New LASSO Invoice
This trigger fires whenever a new invoice is sent from LASSO. It uses webhooks for real-time notifications, so your Zap runs immediately when an invoice is created.
Data provided:
Event information (Event Code, Event Name, Event External Code)
Customer details (Customer Name, Email)
Invoice details (Invoice Number, Invoice Date, Due Date, Terms)
Address information (Billing and Shipping addresses)
Financial information (Total Tax, Deposit Amount, Line-Item Total, Balance Due)
Line items with GL codes, product/service names, descriptions, amounts
New in v2 (existing v1 mappings continue to work unchanged on v2 payloads):
Deposit Line Items collection — deposit credits applied to a reconcile invoice are now exposed as their own line items (with GL code, amount, source deposit invoice reference). v1 hid these and only showed their net effect on revenue lines.
Invoice Total (v2) — single field for amount due that works on both deposit and reconcile invoices. Eliminates the need to branch on Invoice Type.
Invoice Total Before Deposit (v2) — gross before any deposit credits were applied.
Total of Previous Deposits (v2), Has Deposit Credits (v2) — summary fields for deposit reconciliation.
Deposit Invoice IDs (v2), Deposit Invoice Numbers (v2) — which deposit invoice(s) this reconcile is clearing.
Webhook Version — 1 or 2. Lets Zaps branch in mixed environments.
💡 Pro Tip: Existing v1 Zaps continue running unchanged on v2 payloads — every v1 field is still populated. See the v2 Upgrade Summary and v1→v2 Migration Guide for the full field reference and remap guidance.
New Payment Recorded
This trigger fires whenever a new payment record is created in LASSO, manually or through the automated payment processor. It uses webhooks for real-time notifications.
Data provided:
Payment Record ID
💡 Pro Tip: Use the "Find Payment" search action in the next step to retrieve complete payment details using the Payment Record ID.
New Subrental (Purchase Order) Created
This trigger fires when a new subrental (purchase order) is created in LASSO. It uses webhooks for real-time notifications.
Data provided:
Identifiers — Subrental (PO) ID, PO Number, PO Name
Workflow state — Status (Draft, Submitted to Vendor, Quote Received, Approved, Confirmed, Paid, Rejected) and Gear Status (No Gear Required, Not Started, Received, Returned, Shipping to Venue)
Vendor details — Vendor Name, Vendor Code, Vendor External Code
Event details — Event Name, Event Code, Event External Code (blank when the PO isn't tied to an event)
Financial and logistics — Total Cost, Delivery Date, Return Date, Warehouse, Ship Option, Shipping Address
Cost breakdown — GL Code Sums collection, with per-GL-code values: GL Code, GL Code Name, GL Code Description, GL Code Sum
Event envelope — Action (create), Timestamp, Webhook Version (2.0)
Subrental (Purchase Order) Updated
This trigger fires when a subrental (purchase order) is updated in LASSO. It uses webhooks for real-time notifications.
Data provided:
Identifiers — Subrental (PO) ID, PO Number, PO Name
Workflow state — Status (Draft, Submitted to Vendor, Quote Received, Approved, Confirmed, Paid, Rejected) and Gear Status (No Gear Required, Not Started, Received, Returned, Shipping to Venue)
Vendor details — Vendor Name, Vendor Code, Vendor External Code
Event details — Event Name, Event Code, Event External Code (blank when the PO isn't tied to an event)
Financial and logistics — Total Cost, Delivery Date, Return Date, Warehouse, Ship Option, Shipping Address
Cost breakdown — GL Code Sums collection, with per-GL-code values: GL Code, GL Code Name, GL Code Description, GL Code Sum
Event envelope — Action (update), Timestamp, Webhook Version (2.0)
Actions
Actions are operations Zapier performs in LASSO after a trigger from another app occurs. Actions include finds (to look up existing data), creates (to add new data), and updates (to modify existing data).
Event Actions
Find Event
Finds an event based on search criteria.
User inputs:
Search By (Required): code (LASSO assigned) or external_code (your system ID)
Search Value (Required): The value to search for
💡 Pro Tip: Use the Event Code or External Code to find events. The External Code is what you see as the Event ID in the LASSO UI.
Create Event
Creates a new event in LASSO with associated client and venue information.
Required inputs:
Event Name, Begin Date, End Date (YYYY-MM-DD format)
Venue Name, Venue Postal Code
Optional inputs:
Event Code, Event Status, Account Manager details
Client Name, Client Code, Venue Code
💡 Pro Tip: If the client or venue doesn't exist, LASSO will create them automatically. Use External Codes to maintain consistency between your system and LASSO.
Update Event
Updates an existing event in LASSO with new information.
Required inputs:
Event ID: The system-generated ID for the event to be updated
Begin Date, End Date (YYYY-MM-DD format)
💡 Pro Tip: Only provide the fields you want to update. Fields left empty will not be changed in LASSO.
Client Actions
Find Client
Finds a client based on search criteria: code, external_code, name (exact match), or id.
Create Client
Creates a new client in LASSO with name, external code, phone, and URL.
💡 Pro Tip: Use External Code to maintain consistency between your system and LASSO. This helps prevent duplicate clients.
Crew Actions
Find Crew
Finds a crew member based on LASSO ID, your system ID (external_code), or email.
Create Crew
Creates a new crew member in LASSO.
Required inputs:
Email: The email address of the crew member
Classification: fulltime, parttime, contractor, intern, volunteer, vendor, exempt
Postal Code: Used to determine nearest airport
💡 Pro Tip: The Postal Code is required and is used to automatically determine the nearest airport. This helps determine if crew is "local" to events.
Payment Actions
Create Invoice Payment
Creates a new payment record for an invoice in LASSO.
Required inputs:
Invoice ID: Use "Find Invoice" search step to locate the invoice
Payment Amount: The amount of the payment
Invoice Payment Type Code: CHK, CASH, WIRE, ACH, or CC
External Accounting Code: Unique ID from your accounting system
Payment Date: The date when payment was received
💡 Pro Tip: Always use the External Accounting Code to prevent duplicate payments. This should match the payment ID from your accounting system.
Update Invoice Payment
Updates an existing invoice payment in LASSO. Use this action to correct payment information, void payments, or update payment details from external systems.
Best Practices
1. Use Searches Before Updates
Before updating a record, use a Search action to find the record first. This ensures you have the correct ID and can verify the record exists.
2. Use External Codes
When creating or updating records that sync with external systems, always use External Accounting Codes or External Codes. This prevents duplicate records and helps maintain data integrity.
3. Test Your Zaps
Always test your Zaps with sample data before enabling them. Use the Test buttons in the Zap editor to verify each step works correctly.
4. Use Filters Strategically
Use Zapier's built-in "Filter by Zapier" step to only run your Zap for specific conditions. For example, only process invoices over a certain amount or only update events in a specific status.
5. Skip Lookups When the Trigger Has the Data
v2 triggers (invoice 4.0.0+, subrental 4.1.0+) include full payload details inline. You no longer need a Find Subrental (PO) step after the subrental trigger or a follow-up invoice lookup — map directly from the trigger.
Common Workflows
Invoice Processing Workflow
Trigger: New LASSO Invoice
Action: Create record in accounting system (e.g., QuickBooks) — use Invoice Total (v2) for amount due (works for both deposit and reconcile invoices)
Action: Send email notification to customer
Action: Update CRM with invoice information
Payment Recording Workflow
Trigger: New Payment Recorded
Search: Find Payment (get full payment details)
Action: Update accounting system with payment
Action: Send payment confirmation email
Purchase Order Sync Workflow
Trigger: New Subrental (PO) Created (or Updated)
Filter: Status = Approved or Confirmed
Action: Create PO in accounting system using inline trigger fields (vendor, totals, dates, ship option)
Loop: Iterate GL Code Sums to create one accounting line per GL code
Getting Help
Zapier Support
For authentication issues, LASSO data questions, and restricted feature requests:
Contact LASSO Support
Troubleshooting Tips
Authentication Issues: Verify your LASSO username and password are correct and that your user has admin permissions.
Missing Data: Use Search actions to verify data exists before using it.
Field Mapping: Check that field types match (e.g., dates are in the correct format).
Rate Limits: If you hit rate limits, consider adding delays between steps or reducing Zap frequency.
Reference Documents
Companion documents with deeper field-level detail and migration guidance for the v2 webhook updates:
LASSO Zapier v2 Upgrade Summary — invoice v2 capabilities at a glance
LASSO Zapier v1 to v2 Migration Guide — step-by-step invoice Zap remap
LASSO Zapier Subrental PO v1 to v2 — subrental webhook v2 field reference and remap guide