Yes that’s correct, the orders/paidwebhook is probably what you’re looking for.
You’ll need to set up some kind of filter to only send notifications if it’s a special invoice for this circumstance.
If it’s a draft order, you might be able to use the draft_order/update topic instead, if that webhook is emitted when the draft order changes status to paid.
There’s a lot of data in the webhook response and no clear way to distinguish orders which are of interest from normal orders. There probably is, but I don’t have the time to read through a tonne of dox or do some experiments right now.
My pro-tem solution was to tell my colleagues in customer services to tag orders with ‘alert_ken’, ‘alert_sean’, ‘alert_chris’ etc etc if they want to be kept updated about them. Then in the webhook handler I look for that tag. If it’s there, then send a slack + email etc to the appropriate member of staff who’s tagged that order.
Do not forget to warn your colleagues against tagging their mates on dozens of orders just to watch them deal with the huge influx of emails for shits and giggles. I really should’ve seen that one coming.
There’s also using flow to have conditions then use the send-request action to basically proxy the events.
And or also use flow for reconciliation so it just runs on a schedule.
In this scenario, I suggest you periodically poll to check the payment status of your order invoices, and then proceed with the next step of operation accordingly.This approach will not affect the original business logic either.