Peak Automations / Real estate
There is an inquiry for the flat.It lands with the right agent, not in a shared mailbox.
In real estate teams inquiries arrive quickly and in numbers. Peak Automations creates a contact from every submitted Peak Forms form without duplicating it, creates the viewing task and, after a signature in Peak Sign, adds the hand-over appointment to Google Calendar.
Put the goal into words. Add perspectives and timing right below.
Two sample flows · emails to prospects only with approval.
One inquiry / one signature
Inquiry, viewing, hand-over.
- Trigger
- Peak Forms inquiry submitted or agreement signed in Peak Sign.
- Steps
- Contact, task, Google Calendar event, note.
- Control
- Test run with a sample inquiry.
Your first automation
How does an inquiry run for you?
Set the inquiry route, the owner and the first step. The preview shows the rule and stores nothing.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three answers. No lost inquiry.
Draft · not yet put together
- Trigger
- Still open
- Sahip
- Still open
- First step
- Still open
Two real estate moments
Where does an inquiry get lost?
Pick the moment. The example shows contact, task and appointment.
Inquiry form for a property
An inquiry form in Peak Forms is submitted.
- The action
- Peak finds or creates the prospect as a contact, notes the property and creates the task “propose a viewing” for the agent.
- The intent
- Every inquiry has an owner and a next step.
Example: inquiry → viewing
- When
- Inquiry submitted (example)
- Then
- Contact + note “property”
- And
- Task “propose a viewing”
The example shows the structure. In Peak Automations you describe an inquiry's path for you.
To the next stepIs this for you?
What works today. What doesn't yet.
A real estate team that
wants to answer every inquiry.
This is where the example helps.
- Inquiries come in through forms in Peak Forms.
- Contracts are signed in Peak Sign.
- Appointments live in Google Calendar.
Nothing runs
What Peak Automations doesn't do today.
- Property portals are not connected today.
- Peak does not chase anyone on its own; every email to third parties waits for an approval.
- Triggers on inactivity or thresholds are planned, not available today.
From the example to a real automation
Build your inquiry path.
Connect Google Calendar in your workspace's integrations, describe an inquiry's path and test it with a sample inquiry.
Start with Peak AutomationsPeak Automations / Your next step
No inquiry goes unanswered.
Start with the property that gets the most inquiries right now.
See real estate examplesFor real estate teams with many inquiries.
Test run with a sample inquiry.
Frequently asked questions
Are these real customer cases?
No. They are examples built from triggers and actions that exist today. We only show customer cases with evidence.
Does an automation start running right away?
No. You test it with an example first and then activate it yourself. Nothing runs before that.
Does the appointment land in my calendar?
Yes, if your workspace has set up its own Google Calendar connection. Otherwise it stays a task in Peak.




