Overview
The Revamp365 Zapier integration lets you connect your CRM, SMS, scheduling, and e-sign workflows to 6,000+ apps — without writing a single line of code. This article covers:
- How to connect your Revamp365 account to Zapier (OAuth)
- Available Triggers — events that start a Zap
- Available Actions — things a Zap does inside Revamp365
- Available Searches — lookups you can use mid-Zap
- Plan requirements and usage caps
- Troubleshooting common issues
1. Connect your Revamp365 account
- Go to Integrations & Apps → Zapier (or visit /integrations/app/zapier directly).
- Click Connect on Zapier. You will be taken to Zapier's website.
-
In the Zapier editor, when adding a Revamp365 step, click Sign in.
A popup will appear asking you to choose your environment:
- Production — use this for your live account on revamp365.ai
- Staging — use this only if your account is on staging.revamp365.ai
- Log in to Revamp365 in the popup and click Authorize.
- Zapier will show your connection labelled with your email address (e.g. [email protected] · pro). That confirms it is working.
Requirements: You must be on a Starter, Pro, Scale, or Dealmaker plan. Free accounts cannot connect to Zapier.
To disconnect at any time, go to Integrations → Zapier and click Disconnect. This revokes all active Zap webhooks immediately.
2. Triggers
Triggers are events inside Revamp365 that start a Zap. All triggers support instant delivery via webhooks (REST Hooks), with polling as an automatic fallback.
New Contact
Fires when a new contact is created in your CRM.
Key fields returned: id, email,
first_name, last_name, phone_e164,
tags, pipeline_stage, created_at
Available to: Starter, Pro, Scale, Dealmaker
Contact Updated
Fires when an existing contact is updated — including pipeline stage changes.
Key fields returned: Same as New Contact, plus
pipeline_stage_changed_at
Available to: Starter, Pro, Scale, Dealmaker
New SMS Received (Inbound)
Fires when an inbound SMS arrives on your Revamp365 number.
Key fields returned: id, from_number,
body, received_at, contact_id
Available to: Starter, Pro, Scale, Dealmaker (read access)
Note: outbound SMS you sent are not included in this trigger.
New Appointment Scheduled
Fires when a booking or calendar event is created.
Key fields returned: id, kind
(booking or event), attendee_email,
start_time, end_time, timezone,
event_type_name
Available to: Starter, Pro, Scale, Dealmaker
New Support Ticket
Fires when a new support ticket is created in your account.
Key fields returned: id, ticket_number,
title, priority, status, created_at
Available to: Starter, Pro, Scale, Dealmaker
New Wholesale Property
Fires when a new wholesale / off-market property is added.
Key fields returned: id, address,
city, state, asking_price, status
Available to: Scale, Dealmaker only
E-sign Document Completed
Fires when all parties have signed an e-sign packet.
Key fields returned: id, title,
completed_at, signer_count, download_url
Available to: Starter, Pro, Scale, Dealmaker (read access)
3. Actions
Actions are things a Zap does inside Revamp365 — triggered by events in any other app you connect.
Create or Update Contact
Creates a new contact or updates an existing one, matched by email or phone number.
Running the same Zap twice with the same email is safe — it updates the existing
record and returns is_new: false.
Input fields: email, first_name,
last_name, phone_e164, tags,
pipeline_stage, notes
Available to: Starter, Pro, Scale, Dealmaker
Send SMS
Sends an SMS to a contact from your Revamp365 phone number.
Input fields: to (E.164 phone number), body (message text)
Requirements:
- The recipient must already be a contact in your CRM.
- The recipient must not be opted out of SMS.
- Your account's Zapier SMS cap must not be exceeded (default: 200/day, 2,000/month).
Available to: Pro, Scale, Dealmaker (not Starter)
Create Appointment
Books an appointment for a contact using one of your event types.
Input fields: event_type_id (select from dropdown),
attendee_first_name, attendee_last_name,
attendee_email, attendee_phone,
start_time, end_time, timezone, notes
Available to: Starter, Pro, Scale, Dealmaker
Create Support Ticket
Opens a new support ticket in your account.
Input fields: title, description,
priority (low / medium / high / urgent),
categories
Available to: Starter, Pro, Scale, Dealmaker
4. Searches
Searches let you look up existing records mid-Zap. They are used in Zapier's Find or Create pattern: search first; if nothing is found, create it. Searches always return an array (never a 404) — an empty result just means no match.
Find Contact
Looks up a contact by email address or E.164 phone number.
Input fields: email or phone (at least one required)
Available to: Starter, Pro, Scale, Dealmaker
Find Wholesale Property
Looks up a wholesale property by street address or MLS/database ID.
Input fields: address (partial match) or mls_id
Available to: Scale, Dealmaker only
5. Plan requirements and usage caps
| Feature | Starter | Pro | Scale | Dealmaker |
|---|---|---|---|---|
| Connect to Zapier | ✓ | ✓ | ✓ | ✓ |
| Triggers (contacts, appointments, tickets, e-sign) | ✓ | ✓ | ✓ | ✓ |
| Triggers (wholesale properties) | — | — | ✓ | ✓ |
| Send SMS action | — | ✓ | ✓ | ✓ |
| Wholesale property search | — | — | ✓ | ✓ |
SMS caps: To prevent runaway Zaps from generating unexpected charges, Zapier-triggered SMS has a daily cap (default: 200 messages) and a monthly cap (default: 2,000 messages). These caps apply only to SMS sent through Zapier — not to SMS you send manually inside Revamp365. Admins can adjust your cap on request.
You can see your current usage at any time on the Integrations → Zapier page.
6. Sending data into Revamp365 from Zapier (Inbound webhooks)
The actions above let Zaps push data into Revamp365 via our native API. However, if you already have a Zap built around Webhooks by Zapier → POST and want to route inbound leads directly into your CRM with custom field mapping and HMAC signature verification, use the Inbound Lead Webhooks feature instead. Both approaches work; the native Zapier actions (above) are easier for new Zaps, while inbound webhooks give you more control over field mapping for existing automations.
7. Troubleshooting
"Zapier could not connect to your account"
This usually means the OAuth token exchange failed. Common causes:
- You picked "Production" in the environment dropdown but your account is on staging (or vice versa).
- Your account is on the Free plan — Zapier requires a paid plan.
- You declined the consent screen — click "Try again" and click Authorize on the consent page.
Trigger fires but Zap immediately errors
Check the Zapier task history for the error message. Common causes:
- 402 plan_not_eligible — the action or trigger requires a higher plan than your current one.
- 422 recipient_not_consented (Send SMS) — the contact is not in your CRM, or they are opted out.
- 429 zapier_daily_cap_exceeded (Send SMS) — your Zapier daily SMS cap was reached. The header includes a
Retry-Aftervalue. Contact support to raise your cap.
Zap ran but I see a loop
Revamp365 has built-in loop prevention: if a Zap creates a contact via the "Create or Update Contact" action, the system will NOT fire the "New Contact" trigger back to Zapier for that same record. This prevents infinite loops. If you believe loop prevention is incorrectly suppressing a webhook, contact support with the approximate time and your Zapier account email so we can check the server logs.
I disconnected my account and my Zaps stopped
Disconnecting removes all active webhook subscriptions and revokes your access tokens. To re-enable your Zaps, go to Integrations → Zapier and click Connect on Zapier, then re-authenticate in the Zapier editor.
Still stuck? Open a support ticket from the Integrations → Zapier page or email [email protected].