What this helps you do
Your property-management system keeps the lease, the home, the balance and the work order; your access system keeps the gate and the fobs; your reservation process keeps the clubhouse calendar; your package process keeps the deliveries. The Hub keeps none of it. It holds only the residents who joined, the places and topics they follow, and what you sent, which is why a charge reminder is a message that points at the portal or the office where residents already pay. Whatever the system, the doors are the same four: a CSV export you upload on Residents, the inbound webhook that adds one person at a time, signed outbound events that tell your systems who connected, opted out or replied, and the Zapier app when both ends are apps rather than code.
When to use it
Use CSV from an opted-in resident or owner export, usually at the start or after a wave of move-ins. Use the inbound webhook when your own move-in form should add a resident the day they get the keys. Use outbound events when your own systems should know who connected or left. The code in the move-in packet covers most communities.
How to do it
- Export the opted-in residents or owners and upload the CSV on Residents. Email is the only required column; addresses are checked and previewed before any invitation goes out.
- Point your move-in form or your community website form at the inbound webhook on Integrations, so a new resident joins within minutes.
- Add your HTTPS endpoint under events out if your own systems should hear when someone connects, opts out or replies.
- Ask for the Zapier app if you would rather wire your systems and the Hub together without code.
- Create buildings, floors, phases and streets as audiences by name in the Hub, and place residents in them with Bulk assign. They are property data, and nothing imports or infers them for you.
Example
A management company exports its opted-in resident list for one community, uploads the CSV, and points the community website's move-in form at the inbound webhook. When the water goes off at eight, one Blast reaches Building B and the office answers in Conversations. The lease, the balance and the work order never left the property-management system.
Good to know
- There is no property-management, work-order, payment, lease, reservation, package or access-control connector, and no message can be triggered by a work order closing, a package arriving, a lease starting or ending, a balance changing, a gate failing or a move-in. Yardi, RealPage, AppFolio, Entrata and Buildium are named here only to say so.
- The Hub holds no unit, lease, balance, work-order, occupancy, renewal, violation or access data, and it does not learn where a resident lives until you or the resident place them in a place audience.
- The Hub takes no payments, carries no payment link, has no dues feature and holds no balance.
- It is not an emergency alert system, and it satisfies no entry, habitability, meeting or other lease-required, statutory or official notice obligation.
- Everyone arriving through a door still picks their own topics and can leave at any time.