Turn device provisioning requests into Apaleo units
When a connected project signals that a unit is ready for setup, send its request to Notis and create the corresponding unit in Apaleo.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a unit
Create a new unit.
Why this helps
Unit setup requests can be delayed when device rollout details have to be re-entered by hand in hotel operations software.
- Start unit creation from a request sent by an Adafruit IO connected project.
- Use the request details as context for the Apaleo action.
- Send the run outcome to a chosen report channel.
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and Apaleo once in the Notis portal.
- 2Create an automation in Automations, then choose New Automation.
- 3Tell Notis to create an Apaleo unit from each incoming provisioning request, using only the supplied unit details.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real provisioning request to test the workflow.
Questions about this workflow
Does this workflow create units directly from an Adafruit IO event?
Adafruit IO has no native Notis trigger event in this package. A connected project or other sender must send the provisioning request to the Notis webhook.
What information must the request provide?
Provide the unit details needed for creation in Apaleo. Notis cannot supply missing unit details from an unspecified feed or device history.
Can the workflow create a unit group too?
No. This workflow uses the Apaleo create a unit action only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Apaleo. A trigger fires from one place; an action lands in another.
Adafruit IO 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.
Adafruit IO 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.