Zapier lets you connect LMN to thousands of other apps so you can automate repetitive tasks without writing any code. This guide walks you through what the integration can do, how to connect your LMN account, and how to build your first Zaps using LMN triggers and actions.
In this article:
What is Zapier?
Zapier is a tool that lets you create automated workflows called Zaps. A Zap listens passively in the background for a specific event (a trigger) and then automatically performs one or more follow-up tasks (actions) in another app.
With the LMN integration, you can move information into and out of LMN automatically—for example, creating a to-do, logging communication history, or pushing estimate data to another system—so your team spends less time on manual data entry.
Before you begin
Make sure you have the following in place:
An active Zapier account.
An LMN plan that includes access to the integration.
Security Admin permission in LMN, which is required to view the Integrations settings where your credentials live.
Get your LMN Credentials
To connect LMN to Zapier, you'll need your API Key and API Username from your LMN account.
Open your LMN settings and go to the Integrations page.
Locate your API Key and API Username.
Copy these values—you'll paste them into Zapier when you connect your LMN account.
Available Triggers & Actions
The LMN integration supports several triggers and actions you can combine to build automations.
Actions (things LMN can do when a Zap runs):
Create a To-Do
Create a Request
Create Communication History
Find a Contact
Create or Update a Contact
Triggers (events in LMN that start a Zap):
An estimate is created or updated, which pushes estimate data out to your connected app
Important: When testing your Zap, Zapier looks for a recent record to use as sample data. Make sure the test contact, estimate, or other entity you use was created or updated within the last 24 hours, or Zapier may not find it.
Build a Zap with an LMN Trigger
Use these steps when you want an event in LMN to kick off an action in another app.
In Zapier, create a new Zap and choose LMN as the trigger app.
Select the LMN app version marked as the latest available.
Choose the LMN trigger event you want to use.
Connect your LMN account by entering your API Key and API Username.
Test the trigger to confirm Zapier can pull a sample record, then continue building the rest of your Zap.
Build a Zap with an LMN Action
Use these steps when you want another app to trigger an action inside LMN.
In Zapier, add an action step and choose LMN as the action app.
Select the LMN app version marked as the latest available.
Choose the LMN action you want to perform (for example, Create a To-Do or Create a Contact).
Connect your LMN account with your API Key and API Username if you haven't already.
Map the fields from your trigger data into the LMN action fields.
Test the action, then turn on your Zap.
Avoiding Duplicate Contacts
If your Zap creates contacts in LMN, you can prevent duplicates by checking for an existing record first.
Add a Find a Contact step before your Create or Update a Contact step.
Configure the Create or Update step to run only if no matching contact is found, or to update the existing one instead.
Troubleshooting
Connection or authentication error when connecting LMN
If you see a 500 error or a generic "An error has occurred" message when enabling or connecting your account:
Confirm you're signed in to the correct LMN account.
Hard refresh the page or try an incognito/private browser window.
Remove and re-add the LMN connection in Zapier.
If the error persists, contact Support so we can investigate a possible server-side issue.
"One or more validation errors occurred" on Create a To-Do
This usually means the Status or Progress field is empty. Even though it can appear optional, make sure you provide a value for that field in the action step.
401 or required-field errors
A 401 or required-field error often points to a mapping problem. Verify that each required field—such as Lead Name—is mapped to the correct source value, and avoid mapping unrelated data (for example, Lead Classification) into the Lead Name field.
Estimate updates aren't coming through
The estimate trigger fires based on the estimate's Last Updated timestamp. Both manual edits and portal status changes update that timestamp and will trigger the Zap, so confirm the estimate was actually changed if you expected the Zap to run.
Need more help? Contact our Support Team by email at lmn-support@granum.com, through Live Chat, or by phone at (888) 347-9864
Signup for our Live Webinars or learn more about attending our in-person Bootcamps HERE