MNS allows event notifications to be received through a MESH mailbox. On requesting a MESH mailbox to be created, one is required to provide a Workflow ID. Could you please guide whether there is a specific workflow ID to be used when requesting creation of a MESH mailbox for receiving MNS events. Additionally, if a workflow ID exists for this request is it a generic one, i.e. to be used with any event type or there ones linked to specific MNS events.
Hi Deepak,
When configuring a MESH mailbox to receive Multicast Notification Service (MNS) events, you do not need to use an existing workflow ID, nor do you need to register or request a new one from NHS England.
-
No Workflow ID Registration Required: MESH does not validate or restrict workflow IDs for general message routing unless a workflow is specifically restricted. You are free to invent your own workflow ID and MESH will successfully deliver messages using it without any prior setup or registration on the platform.
-
Mailbox Setup Form: When creating a destination mailbox for MNS, you do not need a pre-existing or registered workflow ID associated with the mailbox. If the request form prompts for workflow details, you can simply enter a placeholder name or state that the mailbox is intended for MNS event intake.
-
Setting Granularity in Your Subscription: You can choose whatever workflow ID best fits your internal architecture. You may use a single generic identifier or define distinct, arbitrary workflow IDs for specific event types if your local systems use the header for downstream filtering.
We’ll look to improve the documentation to make this clearer