You are helping me build the following AI agent workflow.

## Goal
Magento 2 Low Stock Alert via Slack And Gmail: Daily cron checks Magento 2 inventory per source and sends low-stock alerts via HTML email and Slack for configurable items.

## Specification
- What it does: You receive daily low-stock alerts for your configurable Magento 2 items before they run out of inventory. This workflow checks stock levels per source, filters non-physical products, and instantly notifies you via HTML email or Slack when SKUs drop below your customizable thresholds.
- Trigger: On a schedule (Scheduled · daily 08:50)
- Autonomy: Fully hands-off
- Expected setup effort: under an hour
- Tools/services involved:
  - HTTP Request: Fetch Magento 2 inventory data via REST API
  - Code: Process stock levels and filter products
  - Gmail: Send HTML formatted low stock reports
  - Slack: Post formatted text notifications

## Known pitfalls, handle each one explicitly in your implementation
1. Slack message length limits can truncate long product descriptions, so ensure the Code node truncates text safely before sending.
2. Incorrect SKU filtering might send false positives for virtual products, so explicitly exclude non-physical item types in your query parameters.

## Reference implementation
https://n8n.io/workflows/6471 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/magento-2-low-stock-alert-via-slack-and-gmail/ via usecasesforagents.com