Added send slack message
This commit is contained in:
@@ -74,8 +74,8 @@ Process in this exact order to ensure data is fresh for downstream decisions:
|
|||||||
* The Postermen
|
* The Postermen
|
||||||
* Intervlag
|
* Intervlag
|
||||||
* Vila Etiketten
|
* Vila Etiketten
|
||||||
* VG Print BV
|
* VG Print B.V.
|
||||||
* Zalsman BV
|
* Zalsman B.V.
|
||||||
* Oakdene Services
|
* Oakdene Services
|
||||||
* I print 1925
|
* I print 1925
|
||||||
* Digiforce
|
* Digiforce
|
||||||
@@ -88,12 +88,50 @@ Process in this exact order to ensure data is fresh for downstream decisions:
|
|||||||
* Drukkerij Van As
|
* Drukkerij Van As
|
||||||
* Oakdene Services
|
* Oakdene Services
|
||||||
|
|
||||||
**Action**: If you want to snooze an order call n8n-mcp snooze-order workflow.
|
**Action**: If you want to snooze an order call traffic-mcp snooze-order workflow.
|
||||||
with a body like this:
|
with a body like this:
|
||||||
{
|
{
|
||||||
orderDetailId: %id_orderdetail%
|
orderDetailId: %id_orderdetail%
|
||||||
}
|
}
|
||||||
|
|
||||||
|
**Action**: Sent information to traffic-mcp with call slack-feed-traffic-delay-list. Use the format below.
|
||||||
|
## Slack Message Format for Snoozed Orders
|
||||||
|
|
||||||
|
When posting snoozed order results to Slack, always use this exact format:
|
||||||
|
|
||||||
|
### 1. Header
|
||||||
|
A single line with the total count:
|
||||||
|
```
|
||||||
|
Here are all {count} snoozed orders:
|
||||||
|
```
|
||||||
|
|
||||||
|
### 2. Table
|
||||||
|
A plain-text table with exactly these four columns, in this order:
|
||||||
|
```
|
||||||
|
Order Detail ID Supplier Carrier Product
|
||||||
|
5768484 De Groot Drukkerij B.V. DPDINT-STANDARD foldedleafletsv2
|
||||||
|
5785996 Probo UPS-UPS_STANDARD smallstickersownsize
|
||||||
|
```
|
||||||
|
|
||||||
|
- Include every order — never truncate or summarize with "and X more"
|
||||||
|
- Keep columns aligned with consistent spacing
|
||||||
|
- Column order is fixed: Order Detail ID → Supplier → Carrier → Product
|
||||||
|
|
||||||
|
### 3. Summary footer
|
||||||
|
After the table, always add a summary line:
|
||||||
|
```
|
||||||
|
All had state "{state}", target dispatch date of {date}, and valid tracking links.
|
||||||
|
```
|
||||||
|
|
||||||
|
If orders have different states or dispatch dates, group them:
|
||||||
|
```
|
||||||
|
- {count} orders with state "{state_a}" and target dispatch date of {date_a}
|
||||||
|
- {count} orders with state "{state_b}" and target dispatch date of {date_b}
|
||||||
|
All had valid tracking links.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Posting
|
||||||
|
Send the formatted message via `mcp__traffic-mcp__Call_slack-feed-traffic-delay-list_`.
|
||||||
|
|
||||||
**Confidence:** If ALL criteria match exactly → auto-execute (99%+ confidence). If any field is ambiguous or missing → MANUAL\_REVIEW.
|
**Confidence:** If ALL criteria match exactly → auto-execute (99%+ confidence). If any field is ambiguous or missing → MANUAL\_REVIEW.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user