Actions32
- Analytics Actions
- Batch Actions
- Customer Actions
- Order Actions
- Product Actions
- Purchase Actions
- Raw Request Actions
- System Actions
- Vendor Actions
- WhatsApp Actions
Batch → Get Batch Status
AI-generatedSummary
Fetches batch expiry status from the VitePOS Bridge (GET /wp-json/vtab/v1/batches/status), optionally filtered by product and outlet, and returns the API response with a readable summary line of expired, near-expiry, valid and no-expiry counts.
Inputs
- Product ID — Limit results to one product; sent as product_id only when filled.
- Outlet ID — Limit results to one outlet; sent as outlet_id only when filled.
- Available Only — Boolean, default true; sent as available_only=1/0.
- Include Global Outlet — Boolean, default true; sent as include_global=1/0.
- Include Archived — Boolean, default false; sent as include_archived=1/0.
- Limit — Maximum number of batch records to consider (default 200); sent as limit.
- Near Expiry Days — Window in days (default 30) used to classify a batch as near expiry; sent as near_days.
Output shape
One item per input item: the bridge's JSON response spread into the item, plus a response text field such as 'Batch status: X expired, Y near expiry, Z valid, W without expiry date.'
The summary sentence is built from data.summary counts (expired_records, near_expiry_records, valid_records, no_expiry_records); if no summary exists it reads 'Batch request completed.' If the API returns status/success false,
responseholds the API error message. With Continue On Fail, failed items output {error}. Uses the viteposBridgeApi credential. Read-only.
Examples
Example 1: Daily alert for products expiring within a week at one outlet
Outlet ID = 3, Near Expiry Days = 7, Available Only = true, Include Archived = false
Example 2: Check expiry health of a single product across all outlets
Product ID = 456, leave Outlet ID empty, Include Global Outlet = true, Near Expiry Days = 30