If you’re looking to connect Sembley with other apps you use daily, you’re in the right place. Sembley integrates with Zapier, a tool that helps you automate tasks by connecting Sembley with thousands of other apps, like EZLynx, AgencyZoom, and more.
This article explains how to connect your Sembley account with Zapier so you can automate tasks across multiple applications. You will learn about Sembley’s Triggers (the events that start a Zap) and Actions (the tasks a Zap performs).
Prerequisites
• You need an active Sembley account.
• You need a Zapier account.
Connecting Sembley to Zapier
Log into Zapier. Go to your Zapier dashboard and click Create Zap.
Select Sembley as your App. When creating a new Zap, search for “Sembley” in the app selection.
Allow Zapier to access Sembley. If this is your first time using Sembley on Zapier, you will be prompted to connect your Sembley account. Follow the instructions to provide your credentials or API key.
Once your account is connected, you can configure your triggers and actions.
Sembley Triggers
Send to Zapier
Triggers when a user clicks the "Send to Zapier" button for any Insured in Sembley. Here's how to to enable and use this powerful trigger.
First, navigate to https://app.sembley.com/settings/integrations-settings and click "Activate" on the Zapier card
Then, turn on the "Zapier Button Visibility" button.
Finally, head over to your Insureds tab and click on the More Actions ⋮ button next to any Insured to activate the trigger
New Insured
Triggers when a submission is created in Sembley that includes a new “Insured.”
Submitted for Review
Triggers when a submission or custom intake is submitted for review.
Sembley Actions
Create New Insured
Creates a new Insured in Sembley. Use this action if you want to add an Insured to Sembley from another source (e.g., from a form submission on a website, or from a record in your CRM).
Fields
When you use Sembley’s triggers, you will see a list of output fields that Zapier can pass to other apps in your Zap. Here are some of the key fields available to Zapier:
• insured_business_name (string)
• insured_mailing_address_line_1 (string)
• insured_mailing_address_line_2 (string)
• insured_mailing_address_city (string)
• insured_mailing_address_state (string)
• insured_mailing_address_zip (string)
• insured_contact_full_name (string)
• insured_contact_first_name (string)
• insured_contact_last_name (string)
• insured_fein (string)
• insured_naics_code (string)
• insured_total_employees (string)
• insured_email (string)
• insured_phone_number (string)
• insured_website (string)
• insured_fax_number (string)
• insured_created_by (string)
Choosing between Triggers
Jeremy, here 👋. We've received a few questions from folks wondering which triggers to use when setting up a Zapier integrations. There are pros and cons to each approach:
New Insured: This will automatically send the new insured to Zapier as soon as you create it. The benefit is that you don't have to send it manually. However, the downside is that when you create an insured they'll only have basic information (name, email and phone).
Submitted for Review: This will automatically send the new insured to Zapier when a prospect submits one of your custom intakes for review. Similar to the "New Insured" trigger, it's nice because you don't have to do anything. If you only want new insureds created when someone fills out a custom intakes to be sent to Zapier (versus insureds created by your team), this is a good option.
Send to Zapier: This is my favorite trigger because you have full control over when and which insureds go to Zapier. You can wait until you have enough information about the insured before sending it to Zapier and you can be picky about only sending qualified leads to the apps you have connected to Zapier. The downside is that you need to manually send the insured to Zapier, it doesn't happen automatically. However this may be a benefit instead of a downside if you prefer the extra control.
So it really depends on your preference and the workflow that you want to build. Again, my preference would always be the "Send to Zapier" trigger because I like the control it gives.