Create multiple Apaleo units from one Zendesk ticket
Handle room and unit expansions without repeating the same setup task.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Create multiple units
Use this call to create multiple units, following a naming rule.<br>you must have at least one of these scopes: 'units.create, setup.manage'.
Why this helps
Creating units one at a time creates tedious work and increases naming errors.
- Speeds up inventory expansion
- Applies the requested naming rule consistently
- Produces one completion summary
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Apaleo in the Notis portal.
- 2Create an automation for batch unit setup.
- 3Tell Notis to read the quantity, naming rule, and property from the ticket, then create the units.
- 4Pick the Zendesk New Zendesk Ticket trigger.
- 5Choose a report channel and test with a real expansion request.
Questions about this workflow
What does the ticket need to include?
It should provide the target property, quantity, and naming rule required by the Apaleo action.
What if the naming rule is ambiguous?
Notis reports the ambiguity and asks for clarification through the configured report channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Apaleo. A trigger fires from one place; an action lands in another.
Zendesk 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)
New User Created
Triggered when a new user is created in Zendesk.
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'.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
Zendesk 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.