Arlanix Notifications for Magento 2 and Adobe Commerce: Problems reach the people who fix them

See it in the admin

How it goes

1. 01

   Your developer installs it

   With Composer, in about twenty minutes. It ends with a test message you can see arrive.

   Installation →
2. 02

   You make a topic, a subscription and a rule

   In the admin, in about ten minutes, without code: what is worth a message, and who gets it.

   Your first rule →
3. 03

   The right people hear about it

   Within a minute or so, by email, Telegram, Slack or Discord. Several messages at once arrive as one digest.

   How a notification is delivered →

What it does

• Email, Telegram, Slack or Discord

  Subscribe an address, a chat or a channel to a topic: everything, warnings and errors, or errors only.

• Rules for what happens in the store

  An order over $100, a refund, a review to moderate: choose the event, its conditions and the topic.

• Hear when the store breaks

  Cron stopped, a job or an indexer failed, an error in the log, orders that stop coming.

• A burst arrives as one digest

  Thirty failed feeds make two emails, not thirty; the same message repeated shows once, with its count.

• A delivery that fails is tried again

  After 1, 5, 15, 60 and 240 minutes, or at once with Retry now. One address that fails holds up no other.

• Every message in the Message Log

  What became of each message, the rule that sent it, and why a delivery failed.

• Your words, the event's fields

  Name the fields in braces, such as {order.increment_id}; Preview shows the message before anything is sent.

• Know who signs in to the admin

  A failed admin sign-in, as whom and why, and a sign-in from an address or a device not used before.

• From your own module too

  A module publishes to a topic the store chooses in its settings; who gets it is up to the subscriptions.