A webhook or a product-drop workflow?

A webhook is a useful building block.

Discord incoming webhooks provide a way to post messages into a channel using a generated endpoint. They are a reasonable option for a simple custom announcement or an integration you are prepared to maintain. Protect the webhook URL as a credential: anyone who can use it may be able to post through it.

A Shopify webhook is a separate concept: it notifies an application about an event in a store. Connecting the two still requires a service that authenticates and processes the Shopify event, decides what to say, and calls the Discord endpoint.

Compare the whole workflow.

Selection and event triggers are different.

A store can update a product many times before a launch. Automatically posting on each edit may not match the moment you want to tell customers. Decide whether the workflow should react to an event or wait for a merchant-created release.

MemberPort is centred on selected products or collections announced now or on a schedule. It is not advertised as an automatic alert for every order, refund, inventory change, or product edit.

Ask what you will maintain.

For a custom workflow, plan authentication, secret rotation, retries, duplicate handling, and a way to observe failed delivery. Shopify notes that webhook delivery can be duplicated; processing needs to account for repeated events.

For any ready-made product, inspect its documented behaviour instead of assuming those details. MemberPort’s current early-access setup gives you a focused product-drop workflow to evaluate with your own test channel.