Tag in FUB Triggers MaverickRE Appointment/Opportunity Routing
🟨 Step 1: FUB Trigger
Trigger: Tag added to contact
Tag Name: send-to-maverick
Zapier App: Follow Up Boss
Trigger Event: “Tag Added to Contact”
🔍 Step 2: Get Lead Info
Use “Find Person by ID” in FUB (Zapier)
Extract:
Lead name
Phone number
Email
Price
Source
Tags
Zip code (if available)
Stage
⚙️ Step 3: Webhook to MaverickRE (Let Maverick Round Robin It)
Zapier Action: Webhooks by Zapier → POST
URL: MaverickRE API endpoint (e.g. https://api.maverickre.io/leads/new)
Headers:pgsqlCopyEditContent-Type: application/json
Authorization: Bearer YOUR_MAVERICK_API_KEY
JSON Payload Example:jsonCopyEdit{
"name": "John Smith",
"phone": "1234567890",
"email": "john@example.com",
"zip_code": "33301",
"price": 450000,
"source": "Zillow",
"tags": ["send-to-maverick"],
"action": "round_robin"
🎯 Key Point: You're not assigning an agent via Zap, you're simply telling Maverick: "Here's a lead — use your own routing logic to assign it to best agent.
Comments: 2
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
25 Jun, '25
Brian Buckley MergedUpdated Setup: Tag in FUB Triggers Round Robin in MaverickRE
🟨 Step 1: FUB Trigger
Trigger: Tag added to contact
Tag Name: send-to-maverick
Zapier App: Follow Up Boss
Trigger Event: “Tag Added to Contact”
🔍 Step 2: Get Lead Info
Use “Find Person by ID” in FUB (Zapier)
Extract:
Lead name
Phone number
Email
Price
Source
Tags
Zip code (if available)
Stage
⚙️ Step 3: Webhook to MaverickRE (Let Maverick Round Robin It)
Zapier Action: Webhooks by Zapier → POST
URL: MaverickRE API endpoint (e.g. https://api.maverickre.io/leads/new)
Headers:pgsqlCopyEditContent-Type: application/json
Authorization: Bearer YOUR_MAVERICK_API_KEY
JSON Payload Example:jsonCopyEdit{
"name": "John Smith",
"phone": "1234567890",
"email": "john@example.com",
"zip_code": "33301",
"price": 450000,
"source": "Zillow",
"tags": ["send-to-maverick"],
"action": "round_robin" -
30 Jun, '25
Rachel Montoya System"Tag in Fub webhook to Maverick Round Robin" (suggested by <Hidden> on 2025-06-25), including upvotes (1) and comments (0), was merged into this suggestion.