> ## Documentation Index
> Fetch the complete documentation index at: https://help.kivaro.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Shopify Flow: Tracking alert raised

> Start a Shopify Flow when Kivaro raises a tracking alert—notify your team, email the customer, or open a support ticket with order and tracking context.

## Overview

AusPost MyPost Business can start a **Shopify Flow** whenever Tracking Alerts creates a new alert that needs attention.

The trigger is called **Tracking alert raised**. Use it when you want something to happen **outside the Alerts dashboard**—for example Slack to ops, an email to the customer, or a tagged support ticket—using the same alert types you configure under **Alerts → Alert Settings**.

> [!TIP]
>
> **Alerts find the problem. Flow runs the response.** Keep monitoring and thresholds in AusPost MyPost Business. Use Flow for the next step (notify, escalate, document).

> [!WARNING]
>
> **Paid plans only:** Tracking Alerts and Shopify Flow triggers require a paid AusPost MyPost Business plan (not Starter). The trigger also only fires after you create and enable a workflow that uses **Tracking alert raised**.

> [card] Same alert types
>
> Fires for the alerts you enable in Alert Settings (no separate Flow threshold)

> [card] Order + customer context
>
> Flow receives the Shopify order and customer, so you can use any order or customer fields

> [card] Tracking details included
>
> Alert type, tracking number, status, reason, suggested action, and tracking URL

> [card] Works with email alerts
>
> Optional: keep daily email summaries and add real-time Flow actions for urgent types

## How it relates to Tracking Alerts

| In AusPost MyPost Business | In Shopify Flow |
| - | - |
| You enable alert types and thresholds under **Alerts → Alert Settings** | You choose **Tracking alert raised** as the workflow trigger |
| Alerts appear in the Alerts dashboard | Flow runs when a **new** alert is raised (and Flow is allowed for your plan) |
| Optional daily summary email | Optional real-time actions (Slack, email, tags, etc.) |

Configure **which** alerts matter in the app. Configure **what to do next** in Flow.

For alert types and thresholds, see the [Tracking Alerts guide](https://help.kivaro.io/tracking-alerts.md). For buying labels with Flow, see [Shopify Flow Automation](https://help.kivaro.io/shopify-flow.md) (that guide covers the **Generate Shipping Label** *action*, not this *trigger*).

## When the trigger fires

The trigger runs after AusPost MyPost Business successfully creates a tracking alert, when all of the following are true:

1. Your shop is on a **paid** plan that includes Flow
2. You have at least one **enabled** Shopify Flow that uses **Tracking alert raised**
3. The shipment has a Shopify **order** and **customer** AusPost MyPost Business can attach (required by Flow)
4. The alert type is one you enabled in Alert Settings and the alert was newly raised

It does **not** fire again for the same alert just because tracking updates later. Re-opens or new alerts can start Flow again according to how alerts are created in the app.

### Alert types you can filter on

These match the labels in Alert Settings and the Flow field **Alert type**:

| Alert type (Flow field value) | Typical use |
| - | - |
| No Update for X Days | Ops / carrier investigation |
| Awaiting Collection for X Days | Remind customer to collect from the parcel locker / post office |
| Returned to Sender | CS follow-up and refund / reship decisions |
| Label Not Lodged for X Days | Confirm the label was lodged or reprint |
| Possible Delay | Proactive customer message |
| Article Damaged | Claims / replacement workflow |
| Cannot Be Delivered | Fix address or contact the customer |

## What Flow receives

Search for the app trigger **Tracking alert raised** (from AusPost MyPost Business). It appears in the Flow trigger list like this:

![Tracking alert raised trigger in the Shopify Flow trigger list, from Kivaro](https://mintcdn.com/kivaro/ZgpYuV5ANB4FXAsf/images/flow-trigger-tracking-alert-raised.png?fit=max\&auto=format\&n=ZgpYuV5ANB4FXAsf\&q=85\&s=3dafb73032d32fcfc19eb47a23f9d72a)

### References (use any order / customer fields)

| Field | Meaning |
| - | - |
| **Order** | Shopify order for the shipment — use order name, tags, note, shipping address, etc. |
| **Customer** | Customer on that order — use email, phone, tags, marketing consent, etc. |

### Trigger payload fields

| Field | Meaning |
| - | - |
| **Alert type** | Which alert fired (see table above) |
| **Tracking number** | Consignment / tracking id |
| **Current status** | Latest tracking status text when the alert was raised |
| **Trigger reason** | Why the alert was created |
| **Suggested action** | Short guidance from AusPost MyPost Business |
| **Carrier** | Display name (e.g. Australia Post) |
| **Order name** | Shopify order name (e.g. `#1044`) |
| **Tracking URL** | Link to the carrier tracking page |

## End-to-end flow

```mermaid theme={null}
flowchart TD
  Ship[Label purchased and shipment tracked]
  Monitor[Kivaro Tracking Alerts monitors tracking]
  Cond{Alert rule enabled and threshold met?}
  NoAlert[No alert - keep monitoring]
  CreateAlert[Create alert in Alerts dashboard]
  PlanOk{Paid plan with Flow?}
  SkipPlan[Skip Flow - alert still visible in app]
  FlowEnabled{Enabled Flow using Tracking alert raised?}
  SkipFlow[Skip Flow - enable a workflow to automate]
  Fire[Start Shopify Flow: Tracking alert raised]
  CondFilter{Your Flow condition: Alert type matches?}
  SkipType[Skip this workflow branch]
  Act[Run actions: Slack email tag ticket]
  Done[Team or customer notified]

  Ship --> Monitor --> Cond
  Cond -->|No| NoAlert
  Cond -->|Yes| CreateAlert
  CreateAlert --> PlanOk
  PlanOk -->|No| SkipPlan
  PlanOk -->|Yes| FlowEnabled
  FlowEnabled -->|No| SkipFlow
  FlowEnabled -->|Yes| Fire
  Fire --> CondFilter
  CondFilter -->|No| SkipType
  CondFilter -->|Yes| Act --> Done
```

## Example workflow: awaiting collection reminder

**Goal:** When a parcel sits **awaiting collection** too long, notify your ops Slack channel and email the customer with the tracking link—without checking the Alerts list every morning.

### What you set up in AusPost MyPost Business

1. Open **Alerts → Alert Settings**
2. Enable **Awaiting Collection for X Days**
3. Set the business-day threshold (for example **3**)
4. Save

### What you set up in Shopify Flow

1. **Settings → Apps and sales channels → Shopify Flow → Create workflow**
2. **Trigger:** search **Tracking alert raised** (AusPost MyPost Business)
3. **Condition:** **Alert type** is equal to `Awaiting Collection for X Days`
4. **Action A — Send Slack message** (or Microsoft Teams / email to ops):

```text theme={null}
Awaiting collection — {{ order.name }}
Customer: {{ customer.displayName }} / {{ customer.email }}
Tracking: {{ Tracking number }}
Status: {{ Current status }}
Why: {{ Trigger reason }}
Suggested: {{ Suggested action }}
Track: {{ Tracking URL }}
```

5. **Action B — Send internal email** or **Send marketing email** / transactional email to the customer (only if your Flow email step and consent rules allow it). Keep the body short:

```text theme={null}
Hi {{ customer.firstName }},

Your order {{ order.name }} is waiting for collection.
Tracking: {{ Tracking URL }}

Please collect it soon so it is not returned to us.
```

6. Turn the workflow **On**

### What happens for one shipment

```mermaid theme={null}
flowchart TD
  DeliveredToPoint[Carrier marks item awaiting collection]
  DaysPass[Business days pass with no collection]
  AlertRaised[Kivaro raises Awaiting Collection for X Days]
  FlowStarts[Flow: Tracking alert raised]
  TypeCheck{Alert type equals Awaiting Collection for X Days?}
  OtherAlert[Other workflows or no match]
  Slack[Post to ops Slack]
  EmailCust[Email customer with Tracking URL]
  Outcome[Ops aware + customer reminded]

  DeliveredToPoint --> DaysPass --> AlertRaised --> FlowStarts --> TypeCheck
  TypeCheck -->|No| OtherAlert
  TypeCheck -->|Yes| Slack --> EmailCust --> Outcome
```

### Why this example works

* Thresholds stay in Alert Settings (one place to tune “how many days”)
* Flow only handles communication
* **Alert type** condition stops every alert type from spamming the same Slack channel
* **Tracking URL** and **Order** / **Customer** references avoid copying numbers by hand

## Other useful patterns

| Pattern | Condition | Actions |
| - | - | - |
| Damaged parcel escalation | Alert type = `Article Damaged` | Slack `#claims` + tag order `damaged-shipment` |
| Delivery failure | Alert type = `Cannot Be Delivered` | Email CS queue + add order comment with trigger reason |
| Possible delay (VIP only) | Alert type = `Possible Delay` **and** customer tag = `VIP` | Personal email from support |
| Quiet hours for non-urgent | Alert type = `No Update for X Days` | Add to a “review tomorrow” spreadsheet or digest email only |

> [!TIP]
>
> Start with **one** alert type and **one** channel (Slack or email). Add more types after you confirm the wording and volume feel right.

## Set up checklist

**1. Enable alerts in the app**

In AusPost MyPost Business, open **Alerts → Alert Settings**, enable the types you care about, and set thresholds where required.

**2. Create the Flow**

In Shopify Flow, create a workflow with trigger **Tracking alert raised** from AusPost MyPost Business.

**3. Filter by Alert type**

Add a condition on **Alert type** so each workflow handles one situation (or a small set).

**4. Add actions**

Use Order / Customer fields plus Tracking URL, Trigger reason, and Suggested action in Slack, email, or tags.

**5. Enable the workflow**

Turn the workflow on. AusPost MyPost Business only sends the trigger when an enabled Flow exists for this shop.

## Troubleshooting

> [accordion] Alert appears in the app but Flow never runs
>
> * Confirm you are on a **paid** plan
> * Confirm the workflow is **enabled** and uses **Tracking alert raised**
> * Confirm the alert was **newly raised** after the workflow was turned on
> * Open the Flow run history for errors on later steps (Slack auth, email, etc.)

> [accordion] Flow runs for every alert type
>
> Add a condition on **Alert type** (exact label from the table above). Without it, one workflow handles all enabled alert types.

> [accordion] Missing customer or order in Flow
>
> The trigger needs a Shopify order and customer on the shipment. Adhoc or incomplete tracking records may create an in-app alert but skip Flow. Check the order still exists and has a customer.

> [accordion] Wrong or empty tracking link
>
> Use the **Tracking URL** field from the trigger. If it looks wrong, open the same consignment on the [Tracking Page](https://help.kivaro.io/getting-started.md#tracking-page) and compare the carrier tracking number.

## Related help

> [card] [Tracking Alerts](https://help.kivaro.io/tracking-alerts.md)
>
> Enable alert types, thresholds, and daily email summaries.

> [card] [Shopify Flow Automation](https://help.kivaro.io/shopify-flow.md)
>
> Buy Australia Post labels automatically with Generate Shipping Label.

> [card] [Tracking Page](https://help.kivaro.io/getting-started.md#tracking-page)
>
> Investigate full tracking history after an alert.

> [card] [Getting started](https://help.kivaro.io/getting-started.md)
>
> App setup and paid-plan feature overview.

> [!NOTE]
>
> Need help designing a workflow? [Email support](mailto:support@kivaro.io) or [book a free consultation](https://calendly.com/kivaro-support/30min).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.