NetSuite and Slack: Goods Receipt Confirmation Template

When your warehouse posts a receiving event, this Spojit template records the item fulfillment against the matching NetSuite purchase order and confirms receipt in Slack.

What It Builds

A Webhook trigger fires the moment your warehouse or scanning system posts a receiving event. A NetSuite Connector node looks up the referenced purchase order and records the item fulfillment against it, then a Slack Connector node posts a confirmation message to the receiving channel. The result is an audit trail in NetSuite and a real-time heads-up for the team, with no manual data entry.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on an incoming webhook when our warehouse posts a goods receipt event. Match the event to the referenced purchase order in NetSuite, record the received items as an item fulfillment against that PO, and then post a confirmation to the #receiving channel in Slack with the PO number, supplier name, and the list of items and quantities received.

Connectors Used

  • Webhook trigger - starts a run when the warehouse posts a receiving event.
  • NetSuite - matches the purchase order and records the item fulfillment.
  • Slack - posts the receipt confirmation to your chosen channel.

Customize It

Change #receiving to your team's channel, and adjust which fields appear in the Slack message (add location, received_by, or a link to the PO). You can also tell Miraxa to flag partial receipts or quantity mismatches against the ordered amounts.

Tips

  • Secure the webhook with HMAC verification so only your warehouse system can start a run.
  • Use a NetSuite Connector node in Direct mode for the exact PO lookup and fulfillment, keeping the run fast and AI-cost free.
  • Make sure your NetSuite role has permission to view purchase orders and create item fulfillments.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.