Move an Approved Apaleo Property to Live
When your team sends a clear go-live instruction, let Notis make the Apaleo status change and report the result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Move property to live
Use this endpoint to move an existing test property to live this operation changes the property status to 'live'<br>you must have at least one of these scopes: 'properties.manage, setup.manage'.
Why this helps
Go-live requests in chat can be missed or left waiting while someone tracks down the right Apaleo screen.
- Keep an explicit go-live request actionable.
- Reduce delay between approval and status change.
- Receive a report after the action runs.
Setup
Build it in a few focused steps.
- 1Connect 2chat and Apaleo once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for approved property launches.
- 3Describe the outcome in one instruction: move the specified test property to live only when the request explicitly says it is approved.
- 4Choose the Notis webhook trigger and configure 2chat to send approved go-live requests to it.
- 5Choose a report channel and test with one real approved test property request.
Questions about this workflow
What does this action change?
It moves an existing test property to live by changing its status to live.
What access is required?
The connected Apaleo account needs properties.manage or setup.manage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Apaleo. A trigger fires from one place; an action lands in another.
2chat triggers
Apaleo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a property
Use this endpoint to archive an existing live property this operation set the isarchived flag to true<br>you must have at least one of these scopes: 'properties.manage, setup.manage'.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check if a property exists
Check if a property exists by id.<br>you need to be authorized (no particular scope required)
Check if a unit attribute exists
Check if a unit attribute exists<br>you must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
Check if a unit exists
Check if a unit exists by id.<br>you must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
Check if a unit group exists
Check if a unit group exists by id.<br>you must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
Clones a property
Use this call to clone a specific property. this operation creates a new property with inventory and rate plans from the specified property.<br>you must have at least one of these scopes: 'properties.create, setup.manage'.
Create a unit
Use this call to create a new unit.<br>you must have at least one of these scopes: 'units.create, setup.manage'.
Create a unit attribute
Use this call to create a new unit attribute.<br>you must have at least one of these scopes: 'unitattributes.create, setup.manage'.
Connect any two apps with Notis in the middle.
2chat and Apaleo, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Apaleo.