Automating Workflows with Zapier: Technical Reference
This article provides a detailed technical breakdown of Sembley’s Zapier integration. It is designed for users who want to build advanced automations and need to understand the exact data structures and events available.
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.
Triggers (Data leaving Sembley)
Triggers allow you to send data from Sembley to other apps automatically when specific events occur. Sembley supports four primary triggers:
1. New Insured from Submitted Intake
Timing: This trigger fires the moment a client clicks "Submit for Review" on an intake form. This allows you to start downstream workflows (like CRM entry or quoting) before you have even reviewed the data yourself.
Available Data: This is the most data-rich trigger. It includes:
Core Identity: Insured Name, Sembley ID, FEIN (Tax ID), NAICS Code, and Total Employees.
Mailing Address: Full breakdown of Line 1, Line 2, City, State, and Zip.
Primary Contact: Full name, email, and primary phone number.
Submission Context: The ID and Name of the specific intake submission.
Dynamic Questions: A full map of every question title in the intake and the client's response.
Data Tables (Policy Schedules): Full arrays of data for complex tables like Vehicle Schedules, Drivers Lists, or Equipment Schedules.
2. New Insured Created
Timing: Fires whenever a new insured record is added to your Sembley account, whether created manually or via another integration.
Available Data: A streamlined payload including the Insured Name, Email, Primary/Cell Phone, and the name of the Sembley user who created the record.
3. Manual "Send to Zapier"
Timing: Fires only when a user clicks the lightning bolt icon or the "Send to Zapier" button on an insured’s row in the Insureds list.
Available Data: Includes the full core identity and contact info, plus all dynamic question responses from the most recent intake submission. Note: This trigger does not currently include the Data Tables object.
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
4. New Notification
Timing: Fires when key system events occur. You can filter your Zap to only react to specific notification types. Events are checked automatically by Zapier.
Notification Types:
Intake Submitted: When a client submits an intake for review.
Intake Started: When a client first begins working on a new intake.
Signature Packet Signed/Viewed: When a recipient interacts with a signature request.
Payment Received: When a payment is successfully processed through a signature packet.
Actions (Data entering Sembley)
Actions allow other apps to create information in your Sembley account.
Create New Insured
This action allows you to push leads or new clients from external sources (like a website form or a CRM) directly into Sembley.
Required Fields: Insured Name.
Mapping Custom Data: You can map data into any of your dynamic questions or table columns in Sembley. To do this, use either the Block Slug (e.g., insured_email) or the internal Block ID (e.g., block:12345) as the key in your Zapier configuration.
How Data is Structured in Zapier
For technical users mapping these fields, here is how complex data is delivered:
The "Questions" Object
Sembley flattens your dynamic intake forms into a simple list of key-value pairs. The Title of the question (as seen in the form builder) is the key, and the client's answer is the value. This makes it easy to find specific answers without knowing internal IDs.
The "Tables" Object (Policy Schedules)
Data-rich tables (like a Schedule of Values) are sent as arrays of objects. Each row in the table is an object, and the Column Header Name is the key for each value within that row. For example, a Vehicle Schedule might look like this:
[
{ "Year": "2022", "Make": "Ford", "VIN": "123..." },
{ "Year": "2021", "Make": "Tesla", "VIN": "456..." }
]