When you’re testing outside clone when you’re using new Cycles, etc, or running actions inside, but as I spoke about before, there’s a utility connector that you can use to create your own error reporting. So if I just go into my settings here, like rental general settings, the first thing that I want to do is enable the transaction there. So this transact Action error webhook is essentially what I’m pointing to whenever there’s an error happening.
This is where the information is being fed to. And as you can see here, I have the option to include warnings as well. So it might be the case, I only want to use only want to listen to actual errors or warnings where the system sends something back and says, look, listen, we’ve accepted this, but it’s not going to work until x, y Zed is fulfilled. So if you want to listen to those warnings, as well, you need to turn on this option in the General Settings, then we go back into the template library, let’s create a new template.
And then what I want to do is drag on this error webhook key. So have this little cycle still there a webhook.
Actually we want to copy this into general settings, so you can only have one error webhook set up per partner. But this will listen out for everything within the account.
And then let’s say I want to send that information to Slack, I can just let’s just post a message here. I can try these two steps together. Post a method. So let’s say watch whatever channel I want, let’s see in general. And then if I want the text, what I want to pull down is the information from the web hook itself. So I’m going to use the account ID, the transaction as well as the message about the error. And maybe I’ll also add in the detail too.
So I could format this however I want. And what Cyclr will do is concatenate these fields into one sort of text blob that can then be sent off based on these merge fields that will then be sent off into the general Slack channel.
Now, if I wanted to add some more information, I could format it or I could post some rich text message if I knew how specifically I wanted it formatted. And again, it doesn’t have to be tied specifically to Slack, this could be sent out as Gmail, this can build up a monthly report using our internal storage that then gets sent out to all users or the affected users. It can be tied to specific accounts on so forth.
But the idea is that whenever you want to listen to errors, or see if something goes wrong on the transaction, and you need to action immediately, that error webhook will be the quickest way to notify yourself, especially if you’re not sat on the platform 24/7.