Send a Slack Alert When a Shopify Product Launches or Expires

The drop goes live at 10 am. By 10:04, someone in Slack asks if it went up. Someone else @-mentions the ops lead to double-check. A third person opens the admin to look. If you run product drops with a team, this scene is familiar: the automation handled the storefront, but the humans still had to catch up manually, in a channel that had no idea the date had just passed. A shopify product expiry slack notification, or any product-date Slack alert, doesn't exist natively. Shopify doesn't send one. Neither do most expiry apps. This guide shows how to route a product launch or expiry date straight into a Slack channel, so your team sees it the moment the date arrives.

The alert Shopify never sends

Shopify's Slack integration handles orders. A paid order fires a message. What it can't do is notify Slack when a product's expiry date passes, because Shopify has no concept of a date-triggered event for products. A metafield date you saved months ago doesn't "change" when the calendar catches up. It was always the 21st of June. June 21st just arrives, and Shopify notices nothing.

Most dedicated expiry apps reach for email when they need to alert someone: send a team notification 7 days before expiry, that's the common pattern. Email is good when you want a paper trail or need to reach someone outside your Slack workspace. But for teams who live in channels, email means lag: read it this morning, act this afternoon, find out at lunch the product was still live all day. For time-sensitive events, the alert needs to land where your team actually spends their time.

Shopify Flow does have a "Send Slack message" action, but that only helps if Flow can trigger the workflow in the first place. And Flow can't trigger from a product date metafield. That's a platform constraint, not a configuration problem, and it's covered in detail in the Flow date comparison guide. The short version: Flow is event-driven, and a date quietly arriving on a product isn't an event Flow detects.

How Slack incoming webhooks work

Slack's incoming webhooks are a free native feature. You create a channel-specific URL, and any POST request containing a text field appears as a Slack message. Setup takes five minutes, requires no app development experience, and there's no ongoing cost. The practical detail: Slack only processes the text field, so whatever you POST needs to include it, formatted for human reading.

That's the one thing to know before you wire DateCue to Slack. DateCue's webhook payload is a small JSON object describing the product and the date that triggered it. It doesn't have a text field, because DateCue is sending a structured event, not a pre-formatted message. So you need one step between DateCue and Slack to reshape the payload into something Slack will display. Zapier or Make handle that step in about two minutes.

How DateCue connects a product date to Slack

DateCue watches your product metafields and fires an HTTP POST to any URL you choose the moment a date condition is met. Route that POST through Zapier or Make, format the product details into a readable message, and forward it to your Slack channel URL. DateCue handles the trigger, Zapier or Make handles the formatting, and Slack shows the result in your chosen channel.

The payload DateCue sends contains six fields:

{
  "shopifyProductId": "gid://shopify/Product/7821934592010",
  "productTitle": "Cold Brew Concentrate 500ml",
  "productHandle": "cold-brew-concentrate-500ml",
  "metafieldValue": "2026-06-21",
  "executionId": "clx7y2a9b0001",
  "actionType": "WEBHOOK"
}

In Zapier or Make, those fields become variables you drop into a message template. "Cold Brew Concentrate 500ml has hit its expiry date (2026-06-21). Pull it from active now." That message, delivered to the right channel the moment the date passes, is the whole thing. The rest is just the plumbing that gets it there.

Setting it up with Zapier

Create a Zapier "Catch Hook" trigger to get a webhook URL, then add a Slack "Send Channel Message" action and format the message using the product fields DateCue sends. In DateCue, create a workflow with the Fire Webhook action pointed at that Zapier URL. The whole setup takes about five minutes and uses Zapier's free tier if you're not already a paid user.

Here's the full sequence:

Step 1: Create the Zapier trigger. In Zapier, create a new Zap. Choose "Webhooks by Zapier" as the trigger app and "Catch Hook" as the event. Zapier gives you a unique URL. Copy it and keep the Zap open in a browser tab.

Step 2: Add the Slack action. Add a second step: Slack, "Send Channel Message." Pick the channel where you want the alert (#ops, #drops, #merchandising, whatever makes sense for this product event). In the message body, use Zapier's field picker to insert productTitle and metafieldValue from the webhook payload. A simple format like "Product [productTitle] has reached its date ([metafieldValue]). Check the admin." is enough to be useful.

Step 3: Create the DateCue workflow. In DateCue, create a new workflow. Set the metafield to whichever date you want to monitor. Set the timing (on the date, or X days before or after). Set the action to "Fire webhook" and paste the Zapier URL from step 1.

Publish the Zap, save the DateCue workflow, and the setup is live. The next time any tracked product's expiry date arrives, the chain fires: DateCue posts to Zapier, Zapier formats the message, Slack shows it in the right channel.

Using the same setup for product launches

Swap the expiry_date metafield for launch_date and point the webhook at a #drops or #new-arrivals channel. The workflow is identical. DateCue pings Slack the moment the launch date arrives, confirming the automation ran and giving the team a heads-up in real time.

You can also set the timing before the date. A workflow that fires 60 minutes before launch gives your team a final check: confirm the product page is ready, make sure the images loaded, verify the collection is live. Then a second workflow fires on the launch date itself to confirm it happened. Stack both on the same launch_date metafield in DateCue, each with its own timing and its own Slack message. They run independently, share the same trigger date, and together give you a pre-launch brief and a go-live confirmation, automatically.

Slack or email: when to reach for which

Use email for recipients outside your Slack workspace, formal records, or cases where you need a paper trail. Use Slack for time-sensitive alerts your team needs to react to immediately, inline with the conversation where they'll act on it. DateCue has a built-in email action that covers the first group on every plan, including the free one.

The two aren't competing. For a perishables expiry, you might want both: an email to the buyer for the purchase record, and a Slack ping to the ops channel so someone pulls the batch from the pick list that same day. Stack two workflows on the same expiry_date metafield, one email action and one webhook, and both fire on the date. The email documents it; the Slack message creates the response. For the email side of this pattern, sending a pre-launch alert 7 days before a product goes live shows how the email action works in practice.

A note on the plan

Being straight about it: the webhook action is part of the Scale plan at $19 a month. DateCue's other actions, changing product status, adding a tag, removing a tag, and the built-in email alert, are available on every plan. If all you need is a team notification by email, you can do that from the free plan without touching a webhook.

Every paid plan includes a 14-day free trial. Build the whole Slack setup, fire a real webhook at a real Zapier URL, watch the message land in your channel, and decide it's worth it before any money changes hands. For the full technical detail on the webhook action itself, including the HMAC signature for verifying that requests are genuine, the DateCue webhook guide covers all of it.

Matt Burrell

Founder of Ripen Studio. I build DateCue, and I spend a lot of my week talking to merchants about the small date-automation gaps that Shopify leaves open. More about Matt.