What level of integration support does LASSO provide?
Your integration module includes access to the LASSO API and Zapier connectors, allowing your team to connect LASSO with other tools in your tech stack and automate key workflows. Here’s how support breaks down:
Included with your integration module: API access, Zapier invitation, setup documentation, and basic troubleshooting via LASSO Support.
For custom or white-glove integrations: Our partner Flow Digital handles custom integration builds and advanced configuration via a Statement of Work (SOW).
Requirements:
The user must already exist in LASSO with an active account manager or supervisor designation in their crew profile. If the user’s crew profile doesn’t have this designation enabled, the API won’t return them in the account_user_role results. Your LASSO admin can enable this under the user’s crew profile settings.
Please note:
Custom integrations must be developed and maintained by your team. A Zapier account must be maintained by your team if Zapier is used. If additional technical support or custom integration work is required beyond basic setup, a separate SOW can be scoped upon request.
Getting Started With Zapier
What do I need before I can connect LASSO to Zapier?
Before you get started, make sure you have the following three things in place:
A contracted integration module on your LASSO account (either the general Integration module or the Accounting Integration module for QuickBooks).
A LASSO Admin user account with a password—not SMS login codes, and not SSO. More on that below.
A Zapier account (you’ll need to maintain your own Zapier subscription).
Once these are in place, contact LASSO Support at [email protected] to request your Zapier invitation.
How does the Zapier connection process work?
Here’s the step-by-step flow:
LASSO Support sends you a Zapier invitation via email.
You accept the invitation, which adds LASSO to your available Zapier apps.
In Zapier, create a new Zap and select LASSO as one of the apps.
Zapier prompts you to log in with your LASSO username, password, subdomain, and environment.
Behind the scenes, the system verifies you’re a LASSO Admin and securely connects your account.
Once authenticated, you’re connected and can start building Zaps.
Good to know:
You don’t need a separately generated API key for Zapier. The system handles authentication automatically when you log in through the Zapier connection flow. If you’ve been told you need an API key for Zapier, that’s an older process—just request the Zapier invitation and the rest takes care of itself.
What’s my subdomain, and how do I enter it correctly?
This is the single most common issue we see during setup. Your subdomain is just the first part of your LASSO URL—nothing more.
For example, if your LASSO URL is yourcompany.lasso.io, your subdomain is simply yourcompany. Do not enter the full URL. Entering "yourcompany.lasso.io" or "https://yourcompany.lasso.io" in the subdomain field will cause an authentication error.
Quick check:
When Zapier asks for your subdomain, enter ONLY the part before .lasso.io. No dots, no slashes, no "https://".
Which environment should I select—Production or Sandbox?
Select Production for your live data. This is the right choice for most customers.
If you’re testing an integration before going live, select Sandbox. You’ll need to be an Admin on the sandbox environment as well. Note: there’s only one version of the LASSO Zapier app—the environment selection simply determines which LASSO data your Zaps connect to.
Does the Zapier invitation expire? Can I share it with teammates?
The Zapier invitation allows anyone on your team to find and use the LASSO app in Zapier. It doesn’t matter how many people access it—LASSO charges for access to the integration module, not per Zapier seat. However, each person who connects to LASSO through Zapier must log in with their own LASSO Admin credentials.
Authentication & Login Troubleshooting
I’m getting an authentication error when connecting LASSO in Zapier. What should I check?
There are four common causes of authentication failures during Zapier setup. Work through them in order:
Wrong subdomain format. Enter only the prefix (e.g., "yourcompany"), not the full URL. This is the most frequent cause of failed logins.
SMS login codes (2FA) are enabled. The Zapier authentication flow can’t handle the SMS verification step. You’ll need to temporarily disable SMS codes for the connecting user, complete the Zapier connection, and then re-enable them. See the next question for details.
The user isn’t a LASSO Admin. Only Admin-level users can authenticate with Zapier. If you’re a standard user, ask your account administrator to upgrade your role, or have an Admin complete the connection.
Your account uses SSO (Single Sign-On). SSO credentials don’t work with the Zapier login flow. You’ll need to create a separate LASSO Admin account with a standard username and password specifically for the Zapier connection. See the SSO question below.
If none of these resolve the issue, try clearing your browser cache and cookies, then retry. If it persists, contact LASSO Support with a screenshot of the error message.
How do I temporarily disable SMS login codes to connect Zapier?
Here’s the process:
Go to Administration → User Directory in your LASSO account.
Find the user who will be connecting Zapier.
Turn off SMS codes (login codes) for that user.
Go to Zapier and complete the LASSO connection using that user’s credentials.
Once Zapier confirms the connection is active, go back to LASSO and re-enable SMS codes.
Why this works:
When you connect LASSO in Zapier, your credentials are sent through an authentication layer that can’t send an SMS verification code back to you. Once the connection is established, Zapier securely stores your credentials and never needs to do the login again—so SMS codes can safely be turned back on.
My company uses SSO. Can I still connect to Zapier?
Yes, but with a workaround. SSO credentials can’t authenticate through Zapier’s connection flow. You’ll need to create a separate LASSO Admin account that uses a standard username and password (not SSO) specifically for the Zapier connection.
This account is solely for establishing the Zapier link—it doesn’t need to be used for day-to-day LASSO access. Once the connection is made, Zapier stores the credentials securely and the account simply stays active in the background.
Your LASSO account administrator or LASSO Support can help create this account if needed.
I’m getting a “Please ensure login codes are disabled” error, but I already turned them off. What’s happening?
This error message covers multiple potential issues, not just SMS codes. If you’ve confirmed SMS codes are off, double-check these two things:
Your subdomain is entered correctly (just the prefix, not the full URL).
You’re using the correct username and password for this specific LASSO environment (Production vs. Sandbox).
The error message says login codes "might" be the issue—it’s a catch-all message for authentication failures. In many cases, the real culprit is a subdomain typo.
Setting Up Your QuickBooks Integration
How do I connect LASSO to QuickBooks through Zapier?
Once you’ve successfully connected LASSO in Zapier (see the Getting Started section above), the QuickBooks setup follows these steps:
In Zapier, create a new Zap with LASSO as the trigger app.
Choose the trigger event (e.g., a new invoice or timesheet).
Add QuickBooks Online as the action app.
Authenticate your QuickBooks account in Zapier.
Map the fields between LASSO and QuickBooks.
Test the Zap to confirm data flows correctly, then turn it on.
The field mapping step is where most of the work happens. Make sure you have your QuickBooks chart of accounts and any relevant GL codes handy before starting.
Can I connect LASSO to accounting software other than QuickBooks?
Yes. As long as the accounting system has its own APIs or a Zapier app, you can integrate it with LASSO. Customers have successfully connected QuickBooks Online (the most common), Sage, and Xero. If your accounting software is available in Zapier’s app directory, it should work—the process is fundamentally about mapping the right fields between the two systems.
Are there pre-made Zap templates I can use?
Not at this time. Because the LASSO Zapier app is currently a private app (invite-only), we’re unable to publish templates or pre-built Zaps to external users. We’re actively evaluating the requirements to make the Zapier app public, which would unlock template sharing in the future.
In the meantime, LASSO Support and our Professional Services team can guide you through building Zaps for common workflows like invoice syncing, timesheet exports, and event creation.
Do I need a Zapier subscription? What plan do I need?
Yes, you’ll need to maintain your own Zapier account. LASSO does not provide or manage Zapier subscriptions. The Zapier plan you need depends on how many Zaps you run and how frequently they trigger—Zapier’s free tier works for basic setups, but more complex integrations (or higher-volume data syncing) may require a paid plan.
Do I need to set up GL codes before sending invoices to QuickBooks?
Yes—this is critical. If you create invoices in LASSO before assigning GL codes, those invoices will come over to QuickBooks with “unknown” GL codes, and you’ll have to recreate them.
Here’s the correct order:
Set up your GL codes in LASSO under Administration → Company Inventory Settings → Financial.
Map those GL codes to your QuickBooks chart of accounts.
Assign GL codes to your LASSO asset categories and billing types.
Then create and send invoices to accounting.
Important:
Invoices in LASSO can’t be edited once created. If an invoice was generated before GL codes were set up, you’ll need to go back to the original quote, verify the GL codes are correct, and create a new invoice from that quote.
For more info on setting up GL Codes, check our GL Code FAQ and GL Code Configuration articles.
My service fees are coming over to QuickBooks without the right GL code. How do I fix this?
If your team uses service fees to bill for labor or other non-gear charges, those line items need a miscellaneous charge type assigned in LASSO to map correctly to a GL code. Without one, they’ll come over as generic “service fees” with no GL code attached.
To fix this:
Go to Administration → Company Inventory Settings → Quotes & Invoices.
Add a new miscellaneous charge type (e.g., “Labor”) and assign it the appropriate GL code.
When creating service fees on invoices, select this charge type from the dropdown.
Recreate any invoices that were sent before the charge type was set up.
This ensures the Zapier integration sends each line item to the correct account in QuickBooks.
How do I set up deposit invoices to flow correctly to QuickBooks?
Deposit invoices require both a LASSO configuration and a specific Zapier field mapping. Here’s the full setup:
In LASSO:
Go to Administration → Company Inventory Settings → Financial.
Create a new ledger code (e.g., “Deposits”) and set the revenue type to “Other.”
Go to Quotes & Invoices and assign this ledger code under the Deposit Invoice section.
In QuickBooks, create a corresponding product/service item for deposits so the Zap has a matching target.
In your Zapier deposit invoice step:
Set the Product/Service type to your deposit product.
Map both the Rate and Amount fields to “Deposit Amount” from step 1 (the larger number). For regular invoices, you’d use the smaller per-line amount, but deposits use the total deposit value for both fields.
Set Quantity to 1.
Once configured, deposit invoices will carry the correct GL code when they flow through Zapier. Previous payments appear as a separate line on the QuickBooks invoice, and discounts are applied directly to line item amounts (you won’t see a separate discount line).
How do I map payment terms from LASSO to QuickBooks in my Zap?
Payment terms (like Net 30, Due on Receipt, etc.) need to be translated between LASSO and QuickBooks because each system uses different internal IDs for the same terms.
The recommended approach:
Use Zapier’s built-in Lookup Table feature (under Formatter by Zapier → Utilities → Lookup Table). This lets you map each LASSO term to its corresponding QuickBooks term ID directly in the Zapier UI—no code required.
If you’re following older setup documentation that references a Code step for term translation, note that this method has been replaced. The Lookup Table approach is simpler, more reliable, and doesn’t require any scripting knowledge.
Finding your QuickBooks term IDs:
Each QuickBooks account has its own set of term IDs. You can find them by querying the Terms endpoint in the QuickBooks API, or by checking your Zapier step’s field options. Make sure your lookup table maps every LASSO payment term to the correct QuickBooks ID for your specific account.
Troubleshooting Active Zaps
My Zap was working, but now it’s throwing errors. What should I check first?
Start with these steps:
Check your Zap version. Open your Zap in Zapier and check that each step is running on the latest version. LASSO periodically releases updates (e.g., v3.3.8 → v3.3.10), and Zaps on older versions can start failing. Update each step to the latest version.
Re-authenticate your LASSO connection. In Zapier, go to your connected accounts and try reconnecting LASSO. This refreshes the underlying authentication.
Check the Zap history. Zapier’s task history shows exactly which step failed and the error message. Share this with LASSO Support if you need help interpreting it.
Verify the LASSO user is still an active Admin. If the user who originally set up the Zapier connection has been deactivated, removed, or downgraded from Admin, the Zap will stop working.
My QuickBooks data isn’t mapping correctly. What should I look at?
Field mapping issues are typically caused by one of these scenarios:
GL codes in LASSO don’t match your QuickBooks chart of accounts. Double-check that the GL codes on your LASSO assets and billing categories correspond to valid accounts in QuickBooks.
Invoices were created before GL codes were assigned, causing line items to come over as “unknown.” You’ll need to recreate those invoices after setting up the correct codes.
Service fee line items aren’t assigned a miscellaneous charge type (e.g., “Labor”), so they come over without a GL code. Set up charge types under Quotes & Invoices in your Company Inventory Settings.
The Zap’s product ID mapping in the Find Products step is incorrect, causing all line items to map to the same product (e.g., everything showing as “Rental”). Edit the Zap and verify the product ID mapping matches each line item type.
A new field was added to LASSO or QuickBooks after the Zap was originally set up. Re-open the Zap and refresh the field list for both apps.
If you’re contracted for the Integration module, LASSO Support can review your field mapping with you. For more complex mapping work, our Professional Services team or our partner Flow Digital can help.
Tip from our integration team:
Use the Zap history (click the clock icon in Zapier) to compare the data coming out of LASSO with what landed in QuickBooks. This lets you pinpoint exactly which step is misconfigured. If you accidentally send an invoice to accounting twice, don’t worry—the Zap will recognize the duplicate and skip it.
Retainer payments or specific financial data aren’t coming through correctly. What’s going on?
Changes to how data flows between LASSO and QuickBooks can occasionally be affected by updates on either side. If you notice something like retainer payments not applying properly or amounts suddenly looking wrong, here’s what to do:
Check if LASSO recently updated the Zapier app version (your Zap steps may need updating).
Check if anything changed in your QuickBooks setup (new account types, modified payment terms, etc.).
Review your Zap’s task history for error details.
Contact LASSO Support with specifics—we’ll coordinate with our integration team to investigate.