Skip to main content
Features/Zapier Integration
WebGrowly OS

Every Lead Source. One Organized Pipeline.

Bring leads from portals, ad forms, spreadsheets, and any Zapier-compatible source into the same CRM. Exact email matching updates an existing person instead of creating a duplicate, while the original source and status remain protected.

Book a 60-Minute DemoAll Features

9

Lead fields

name · email · phone · source · budget · notes · type · location · bedrooms

2

API endpoints

create lead · test authentication

1

Secure API key

x-api-key · allowed domains · rate limits

3.1

OpenAPI standard

public documentation · live explorer · curl examples

A Facebook Lead, Already Organized in Your CRM

The connected Zap on the left; the complete lead record and original source on the right.

Diagram showing portals, ad forms, and spreadsheets sending up to nine mapped fields through Zapier to WebGrowly CRM, where exact email matching creates a new lead or updates the existing record without changing its original source and status.

What Lands in Your CRM

Sofia K.

Facebook Lead Ads

sofia.k@mail.com

$450K·Condo·Brickell

Marco T.

Google Forms

marco.t@mail.com

$2.8K/mo·Rental·Edgewater

Julia B.

Typeform

julia.b@mail.com

$650K·House·Coral Gables

How It Works

STEP 01

Copy the API key from your dashboard

Every account receives its own key. Zapier sends it in the x-api-key header, and WebGrowly also checks the account’s allowed domains and request limits. The connection test confirms the account ID, name, company, and plan.

STEP 02

Choose any Zapier-compatible lead source

Use your portal, ad form, spreadsheet, or another connected app as the trigger and WebGrowly OS as the action. Then map up to nine fields: name, email, phone, source, budget, notes, property type, preferred location, and bedrooms. Name is required.

STEP 03

Prevent duplicates and preserve the original source

WebGrowly looks for an exact email match without regard to capitalization. If that person already exists, only their contact details and stated criteria are updated. Status and source are set when the lead is first created, so a repeat delivery cannot move the person backward in the pipeline or replace the original acquisition channel.

STEP 04

Count only genuinely new leads

A new email creates a lead with status “new” and the source supplied by your Zap, or “Zapier Integration” by default. It counts toward the monthly lead allowance and triggers the new-lead notification. A repeat delivery updates quietly and does neither. The API log records the endpoint, method, result, and response time for every call.

Why Agents Use It

Automatic Deduplication

If the same person arrives from an ad form and your website, exact email matching updates the existing record instead of filling the pipeline with duplicates. Simultaneous deliveries are safely rechecked and updated rather than failing.

Nine Fields Built for Reliable Delivery

Name, email, phone, source, budget, notes, property type, preferred location, and bedrooms are validated and safely capped. A long note is trimmed within documented limits instead of breaking a working Zap.

Complete API Documentation

Public documentation includes the OpenAPI 3.1 specification, an interactive explorer, and ready-to-use curl examples for both endpoints. You retain control of field mapping and authentication in your own Zap.

Continue the tour

Website AI Assistant

The assistant appears across the website, searches live MLS data, and answers with actual property cards; when the visitor shares contact details, the CRM record includes the conversation transcript. Theme, accent color, greeting, avatar, voice input and output, and the number of useful exchanges before the contact request are configured in WebGrowly OS rather than in code.

Learn more →

Contact & Inquiry Forms

Every website form submits through one server-controlled endpoint with nine defined source contracts: general contact, property inquiry, exit callback, three guides, neighborhood quiz, home valuation, and saved properties. Each branch fixes its own attribution and rejects unexpected fields, preventing the browser from inventing a source or attaching arbitrary property metadata.

Learn more →

Exit-Intent Callback

A dismissible callback panel becomes eligible only after five seconds, then appears when the pointer leaves through the top edge or after three upward scroll reversals. It can fire only once per session and remains disabled whenever another overlay is open, so it does not interrupt a visitor already completing a task.

Learn more →

Bring Every Lead Source into One CRM

See a live Zapier intake during a 60-minute WebGrowly demo.

Book a Demo