Skip to content
English
  • There are no suggestions because the search field is empty.

Automatically add tags to an order

Build a trigger that adds tags to an order as it is created, tags only orders with certain products, removes a tag later, and what those tags then drive.

A trigger can add a tag to an order as the order is created, with no one typing it: listen for Order Status Changes To with the Ordered status, and choose the Add Tags action. The same trigger can be narrowed to orders that contain certain products, and a second trigger can take the tag off again later. Once the tag is on the order it does the rest of the work for you, in reports, in other triggers and in Zapier.

Applies to: every Allmoxy site and every order type. Building triggers needs the Add/edit site triggers permission. Tags themselves are explained in Tags in Allmoxy.

In this article

Tag every new order

  1. Go to Settings > Operations > Triggers and click Add Trigger.
  2. Name the trigger, for example "Ordered: add New and Check drawings".
  3. Choose who it applies to: you can have this trigger fire for all companies in your system, a group of companies (via tags) or a single company.
  4. Under Conditions, choose Order Status Changes To in Trigger when and tick the order status you want it to fire on, in this case the Ordered status.
  5. Under Action, set the Type to Add Tags and put in the tags you want added to the order, for example "New" and "Check drawings".
  6. Set Active to Yes and click Save.

This trigger fires when any company places an order (or moves a bid up to Ordered status), and it adds the two tags to the order. It also fires when an order jumps past Ordered in one save, for example a bid saved straight to Verified, because the order passes Ordered on the way: the tags are added once, at the Ordered step. A bid that is saved and stays a bid does not fire it, because Ordered was never reached.

Tag only orders with certain products

To tag only some orders, add an extra condition to the same trigger. Order Status Changes To is one of the four events that allow them. Click Add Condition and choose a type in the And if row:

  • Product, to match a specific product, for example "Drawer box" (is or is not).
  • Product Attribute, to match a value a customer chose, for example a finish or a species.
  • The product tags box, to match any order that has at least one product carrying one of the product tags you enter.

You can layer conditions, such as a product and a particular attribute value, and all of them must hold. So a trigger "Ordered, product tag Finished, add tag Finish shop" puts a Finish shop tag on every order that includes a finished product, and nothing on the rest. Several of these triggers side by side give you a different tag for each department that needs to see the order.

Remove a tag later

To take the tag off again, build a second trigger with the Remove Tags action: for example, Order Status Changes To with Shipped ticked, action Remove Tags, tag "New". The tag is removed from the order when it ships. A Remove Tags trigger logs Success even when the order didn't have the tag, so an empty result there is normal.

What the tags then drive

  • Reports and queues: filter orders by tag to build a department's list of what to look at. See Production reports.
  • Other triggers: the Order Tag extra condition lets a later trigger fire only for orders that have (or don't have) a tag, so "Check drawings" can hold back a customer email until someone removes it.
  • Later emails and attachments: a trigger on a later status can use the Order Tag condition to decide which orders get an email, and which output pages go with it. See Output pages.
  • Zapier: a tag added to an order is sent to the Allmoxy app in Zapier as a "tag added to order" event, so a Zap can create a card or a row for it. A tag removed by a trigger is not sent to Zapier. See Zapier triggers and the data each one sends.

Things to know

  • Each run writes one row to the Trigger Call Log, with the order it tagged, so you can confirm the tag went on at Reports > Managerial > Trigger Call Log.
  • The tags go on the order the event is about. To tag a company instead, listen for a company event such as New Company Created; the Add Tags action tags whichever record the event belongs to.
  • Extra conditions work on Order Status Changes To, Remake Status Changes To and the two process events only. On other events they are ignored.
  • Tags are added at the status step, not when the bid is saved. A trigger on Ordered fires when the order reaches Ordered, whether a customer placed it or your office moved a bid up.
  • A tag removed by a trigger sends nothing to Zapier, while a tag added does.

Related articles