Cannot assign notification channel to relay webhook

I'm trying to set up a notification on a webhook to report on transaction statuses. However when I go to the setup dialog on the relayer none of the notification channels I've set up appear.

Am I thinking about this wrong or is there a bug?

Is this the only official support channel for Defender?

I'm concerned about a production release given what I've experienced as a buggy UI and light, inconsistent documentation.

In the meantime this is blocking a high profile and time sensitive project. Hopefully someone has some insight soon.

Hi @lightcap

We are taking a look.

In the meantime, to facilitate easier debugging, could you please provide your account tenant ID and, if possible, the user ID used for this operation?

You can send additional info to us via defender-support @ openzeppelin . com or report this issue directly from Defender by using Feedback Form.

Best,
Zeljko

Hi @lightcap

Based on relayer id from attached image I was able to find account info.

Relayer webhook notifications feature at the moment supports only attaching webhook channel type.

In your account I see that there are only slack and email channels and that is main reason why you are seeing empty list.

If you create webhook notification channel you would be able to see it here and select it.

I am wondering about your use case, were you intending to use slack or email?

We can extend support to other channels based on prioritisation and user requests.

Best,
Zeljko

Thanks for having a look. Our tenant ID is 5448dbfa-8651-4796-b729-90633a6ed4ea.

I set the slack and email notification channels up as a test to see if they'd show up to select in the relayer webhook notification drop down I posted.

My use case is to send transaction lifecycle notifications in a few cases. First, if a transaction fails or has execution reversed to notify a support slack channel. Second, to send an alert to Sentry on those same failures. Finally, to send a notification to our backend when the transaction is confirmed.

I'll try setting up a webhook notification on the relayer webhook as you say. If that works it's a fine workaround for slack and sentry as I can just use their webhooks (which is basically what the dedicated notification channels are doing as far as I can tell).

In the meantime I'm using a address monitor for the relayer account. But it only supports success and failure but I'd prefer to have more granular transaction statuses, hence the above.

@zeljko any progress looking into this?