Custom Alerts
Summary
Custom Alerts are configurable emails tied to a workflow event, built with data placeholders and an optional custom sender, that only fire when added as an action in a matching workflow rule.
Custom Alerts are configurable emails tied to a specific event (order import, pricing/quantity update, routing). You compose the subject and body with event data placeholders, optionally send from your own address via an email connection, and the alert fires when added as an action in the matching workflow rule.
- Tied to an event — order import, pricing/quantity update, routing completed, and more.
- Data placeholders — inject real-time values from the event into the email body.
- Choose the sender — send from your own address via an email connection, or the default sender.
- Fired by a workflow — the alert sends as an action inside a matching workflow rule.
| Field | Detail |
|---|---|
| Name | Internal name to identify the alert. |
| Event | The event it is tied to; determines the data available. |
| Email connection | Optional sender address; without one it sends from Flxpoint's default no-reply sender. |
| Subject | The email subject line. |
| Body | Text plus event data placeholders that inject real-time values. |
| Event | Data available in the alert |
|---|---|
| Order Import | Order metadata (order number, shipping address, etc.). |
| Fulfillment Request / Order | FR/FO metadata. |
| Pricing / Quantity update, Routing completed | Data specific to that event. |
The custom alert is not sending. Creating the alert alone does not send it. Add it as an action in a workflow rule for the same event — an order-import alert must live in an order-import workflow rule, with the rule's conditions met.
Recipients cannot reply, or replies bounce. The default no-reply sender is not monitored. Configure an email connection so the alert sends from a real, monitored address.
A placeholder shows up blank or as literal text. Placeholders are per-event. Make sure the placeholder you used belongs to the alert's selected event — a placeholder from a different event will not resolve.
What is a custom alert? A configurable email tied to an event (such as an order import) that sends a unique, data-rich message when that event's workflow rule fires.
How do I create one? Go to Settings, Custom Alerts: enter a name, choose the event, pick the email connection, set a subject, compose the body with placeholders, then Create.
Why isn't my alert sending? It must be added as an action inside a workflow rule for the matching event; the alert on its own does not trigger.
Can I change the address alerts come from? Yes — configure an email connection to send from your own address. Otherwise alerts come from Flxpoint's default no-reply sender.
Why is my alert only available in one workflow? Events and workflows are tied together, so an alert built for one event can only be applied within that event's workflow.