NetSuite and Slack: Overdue Supplier PO Follow-Up Template
A daily workflow that finds NetSuite purchase orders past their expected receipt date and posts an overdue follow-up list to your procurement Slack channel.
What It Builds
A Schedule trigger runs each morning and a NetSuite Connector node pulls purchase orders whose expected receipt date has passed and that are not yet fully received. A Transform step shapes them into a tidy list, then a Slack Connector node posts the summary to your procurement channel so the team can chase suppliers before delays hit the line. Spojit handles the schedule and the connections for you.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every weekday at 8am, finds NetSuite purchase orders whose expected receipt date is in the past and that have not been fully received, and posts an overdue follow-up list to the #procurement Slack channel showing the PO number, vendor name, expected date, and days overdue.Connectors Used
- Schedule trigger - runs the workflow on a daily cron in your time zone.
- NetSuite - queries open purchase orders and their expected receipt dates.
- Slack - posts the overdue summary to a channel.
Customize It
Change the run time or days in the prompt, swap #procurement for your own channel, or adjust the overdue threshold (for example, only POs more than three days late). You can also add fields like buyer name or total amount to the Slack message without a second prompt.
Tips
- Make sure your NetSuite connection has read access to purchase order and vendor records.
- Use the Slack Connector node in Direct mode to post the exact message with no AI cost.
- If your PO volume is high, have the Transform step sort by days overdue so the worst delays surface first.