Turn a completed project handover into Apaleo units
When a site is ready for inventory setup, pass the confirmed unit count and naming rule to Notis so Apaleo can create the units in one go.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create multiple units
Create multiple units following a naming rule.
Why this helps
Manually creating units after a project handover adds repetitive work and makes it easy to lose track of which inventory is ready.
- Create multiple units in one action.
- Use the naming rule supplied with the handover.
- Keep the request anchored to a specific Apaleo property.
Setup
Build it in a few focused steps.
- 1Connect Acculynx and Apaleo once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to create units for the supplied Apaleo property using the confirmed count and naming rule; ask it to report missing details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Send one real handover request and review the created units.
Questions about this workflow
What should the handover request contain?
Include the Apaleo property identifier, confirmed unit count, and naming rule needed by the action. Notis should report missing information rather than inventing it.
Does this workflow create a property too?
No. This workflow creates multiple units for the property identified in the request.
Can I start this from an Acculynx event directly?
There are no Acculynx trigger events listed here. An external tool or custom backend must send the webhook request to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Acculynx to Apaleo. A trigger fires from one place; an action lands in another.
Acculynx triggers
Apaleo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a property
Archive an active property.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check if a property exists
Check whether a property exists.
Check if a unit attribute exists
Check whether a unit attribute exists.
Check if a unit exists
Check whether a unit exists.
Check if a unit group exists
Check whether a unit group exists.
Clones a property
Clone a property, including its inventory and rate plans.
Create a unit
Create a new unit.
Create a unit attribute
Create a new unit attribute.
Connect any two apps with Notis in the middle.
Acculynx 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.