Invelo Webhooks Integration

Send external data into Invelo automatically

Invelo now supports Webhook integrations, allowing you to send real-time data from external tools directly into Invelo. Whether you're collecting lead data through a form, syncing from another CRM, or processing property lists through automation platforms like Zapier, Make, or custom scripts—Webhooks make it seamless to keep Invelo up to date.

This feature is ideal for:

Real estate investors who want to automate lead intake
Teams syncing property/contact data from external platforms
Developers building custom integrations into Invelo

How webhooks work in Invelo

A webhook allows external services to send an HTTP POST request to Invelo’s webhook URL with structured data (JSON payload) to either create or update properties and contacts.

How to setup webhooks in Invelo

To set up a webhook:

Click your profile icon at the top right part of the platform. From the drop down list, choose Integrations.
In the integrations page, click on Webhooks. Once the Webhook modal appears, select Add Webhooks.
Once you're redirected to the Webhooks page, click on Create new webhook.
Add the following information:
- Name: The webhook name is for your reference only. A unique URL will be generated after setup.
- Model type: Select the type of record this webhook will handle—either property or contact.
  - Allow creating new properties or contacts: The webhook can create new properties or contacts in Invelo if those records don't already exist.
- Field mapping: Map fields from your webhook payload to the correct fields in Invelo. Use dot notation to access nested data—for example: property.address_1 or contact.first_name. This tells Invelo exactly where to look for the data in your incoming request.
  - Property record required fields: APN, Property Address Street, Property Address City, Property Address State, Property Address Zip, Lifecycle Stage
  - Contact record required fields: First name, Last name, Company name, Phone number, Email address, Mailing address street, Mailing address city, Mailing address state, Mailing address zup.
Optional: You can choose to enable the following options:
- Enable webhook security
- Property record updatable fields
- Enroll records into Workflows
Click Save.

You can then copy the webhook URL into your external system, such as:

A form platform (e.g., Typeform, Jotform)
Automation tools (e.g., Zapier, Make)
Your custom backend script or CRM

Configuration options

When configuring a webhook, the following toggles let you control how data is handled:

1. Allow Creating New Property or Contacts If They Do Not Exist

Default: On
If On: Invelo will create a new property or contact if it does not already exist.
If Off:
- Existing records will be updated if found.
- If a property exists but the contact doesn’t, the contact will be ignored.

2. Change Primary Contact If Contact Is Found or Created

Default: Off
Available only for: Property Records webhook
If enabled, the webhook can change the primary contact on a property record.
Note: If the property doesn’t have a primary contact, the incoming contact will become the primary regardless of this setting.

Property Record Field Support

Field	Required	Updates Allowed	Notes / Validation
APN	✅	❌	Must include City + State if used
Property Address 1	✅*	❌	Required if APN is missing
Property Address 2	❌	❌
City	✅*	❌	Required if APN is missing
State	✅*	❌	Required if APN is missing
ZIP Code	✅*	❌	Required if APN is missing
Lifecycle Stage	❌	❌	Used only on creation
Asking Price	❌	✅
Lead Temperature	❌	✅	Must match Invelo enum (e.g., “Cold”)
Sale Timeline	❌	✅	Must match enum (e.g., “1–3 months”)
Deal Type	❌	✅	Must match enum (e.g., “Wholesale”)
Profit	❌	✅	Numeric
Purchase Date	❌	✅	Valid date format (YYYY-MM-DD)
Purchase Price	❌	✅	Numeric
Custom Fields	❌	✅	Fully mappable to user-defined fields

Contact Field Support

Field	Required	Updates Allowed	Notes / Validation
First Name	✅	❌	Name check logic for existing matching
Last Name	✅	❌	Name check logic for existing matching
Company Name	✅	❌	Name check logic for existing matching
Title	❌	✅
Phone Number	✅	❌	Duplication check based on number
Email Address	✅	❌	Duplication check based on email
Mailing Address 1	✅	❌	Required for duplication logic
Mailing Address 2	❌	❌
City	✅	❌	Required for duplication logic
State	✅	❌	Required for duplication logic
ZIP Code	✅	❌	Required for duplication logic
Custom Fields	❌	✅	Can map to user-defined custom fields

Example use cases

Lead forms on your website: Connect a form to Invelo so any submitted property info creates a record automatically.
CRM-to-Invelo sync: Push data from other platforms like Salesforce into Invelo in real time.
Post-purchase updates: Send webhook data to update purchase details once deals close in another system.

Validation logic & safeguards

Required Field Logic: Missing required fields will cause the webhook to fail. Logs will reflect which field caused the issue.
Enum Matching: Fields like "Lead Temperature" or "Deal Type" must match Invelo’s internal values. Mismatches will be rejected.
Duplication Checks: Contact updates rely on email, phone, and address duplication logic to prevent overwriting or duplicating contacts improperly.

Need Help?

Our team is here to help you troubleshoot or map your data correctly.