Actions119
- Categories Actions
- Payments Actions
- Appointments Actions
- Bookings Actions
- Extras Actions
- Events Actions
- Locations Actions
- Services Actions
- Coupons Actions
- Timeslots Actions
- Custom Fields Actions
- Entities Actions
- Search Actions
- Users Actions
- Customers Actions
- Employees Actions
- Notification Actions
- Stats Actions
- Resources Actions
- Packages Actions
Notification → Add Notification
AI-generatedSummary
Creates an Amelia notification by sending the configured notification fields in the request body. Set the notification content, name, recipient, delivery type, and any applicable entity, timing, or WhatsApp template values; Entity Ids is parsed from JSON into a value before sending.
Inputs
- Content — Notification message body; defaults to an HTML template containing customer and company placeholders.
- Custom Name — Custom notification label; defaults to
Custom notification. - Entity — Entity associated with the notification; defaults to
appointment. - Entity Ids — JSON value parsed and sent as entity IDs; defaults to
[1]. - Name — Notification identifier; defaults to
customer_appointment_approved. - Send Only Me — Boolean flag sent with the request; defaults to
false. - Send To — Recipient selector; defaults to
customer. - Status — Notification status; defaults to
enabled. - Subject — Notification subject; defaults to
%service_name% Notification Subject. - Time — Optional time value; default is empty.
- Time After — Optional lower time bound; default is empty.
- Time Before — Optional upper time bound; default is empty.
- Type — Notification delivery type; defaults to
email. - Whats App Template — Optional WhatsApp template value; defaults to an empty string.
- Request Options — Optional HTTP request settings: batching (50 items per batch, 1000 ms interval by default), insecure SSL acceptance, proxy, and timeout (10000 ms by default).
Output shape
A response item from the Amelia API, passed through the node's main output.
The supplied source shows the OpenAPI properties builder and request defaults, but not the generated operation's response schema. The request uses the configured Amelia API key and admin AJAX URL.
