The Sisu and reZEN integration allows you to seamlessly push your listings and transactions to reZEN from Sisu, reducing manual entry and keeping your data accurate and consistent. This guide walks you through what to expect from the integration, how it works, and how data fields are mapped between Sisu and reZEN.
Topics in this article:
🔄 Integration Overview
When you set up the integration, two forms will automatically appear in Sisu. These forms include the required fields that allow data to sync from Sisu to reZEN:
reZEN Listing Builder – Used for seller-side listings
reZEN Transaction Builder – Used for buyer-side transactions
The information entered into these forms will sync to reZEN once a transaction meets the trigger you’ve configured. Triggers can be customized to fit your workflow, for example:
When a transaction status changes to Pending
When a stage changes to Preparing signing docs
When a specific tag (like reZEN) is applied
⚠️ Important notes:
This is a one-way integration. Updates flow from Sisu to reZEN only.
Document sharing between Sisu and reZEN is not currently supported, though it’s under review for future updates.
✅ Integration Requirements
To ensure the integration works smoothly, a few things need to be in place:
Agent Matching: The agent assigned to the property in Sisu must also exist in reZEN. Agents are matched by first name, last name, and email address, so be sure these details are identical in both systems.
State Licensing: The Sisu agent must have an active license in the same state as the property.
Participants in reZEN: reZEN automatically creates Buyers, Sellers, Agent-Owners, and Commission Payers as “Participants.” These Participants cannot be edited from Sisu, however, you can still update details like commission info, transaction amount, and property addresses in Sisu. Commission Payers will be created in reZEN using the Escrow Vendor information from Sisu.
🏡 Listings (Seller Side)
Please note the following when syncing Seller transactions from Sisu to reZEN:
The Transaction Type within the Sisu transaction must be selected as Seller.
A seller profile is created in reZEN using the first name, last name, email, and phone number that was entered into the reZEN Listing Builder form in Sisu.
The reZEN listing’s Owner is determined by the agent selected in the Sisu transaction.
Field Mapping: Required fields are indicated with an *.
Sisu Field → | reZEN Field |
City | City |
State | State |
Postal Code | Zip |
Address Line 1 | Street Address |
MLS ID | MLS Number |
Year Built | Year Built |
Signed Date* | Listing Start Date |
Listing Expiration Date | Listing Expiration Date |
Transaction Amount* | Sale Price |
LAC%* | Listing Commission |
BAC% | Sale Commission |
🛒 Transactions (Buyer Side)
Please note the following when syncing Seller transactions from Sisu to reZEN:
The Transaction Type within the Sisu transaction must be selected as Buyer.
A buyer profile is created in reZEN using the first name, last name, email, and phone number that was entered into the reZEN Transaction Builder form in Sisu.
If no Seller Name is provided, reZEN will default the field to “NA” (you can edit it in reZEN later).
The reZEN transaction's Owner is determined by the agent selected in the Sisu transaction.
Commission Payer info will sync from the Escrow Vendor field in Sisu. If no Escrow Vendor is provided, a team participant will be created as the Commission Payer info is required in reZEN.
Field Mapping: Required fields are indicated with an *.
Sisu Field → | reZEN Field |
Acceptance Date | Acceptance Date* |
Forecasted Closed Date or Closed (Settlement Date) | Closing Date (estimated)* |
Closed (Settlement Date) | Closing Date (Actual) |
Transaction Amount | Sale Price* |
GCI | Commission* |
| Buyer Info |
Seller Names | Seller Name |
Escrow Vendor
| Commission Payer |
🧠 Troubleshooting
With the Sisu > reZEN integration, key listing and transaction information flows directly between systems, saving time and reducing errors. If you experience any issues, please double check the following:
Agents are correctly matched and licensed
All required fields in Sisu are completed
Trigger stages, statuses, and tags are correctly configured
Need help optimizing your setup or have questions? Our support team is here for you! Just drop us a message in the chat bubble in Sisu! 💬