Now, let’s say I want to add a utility connector to this. Utility it can act as an extra functionality that allows cycles to either collate data, transfer data across different templates, or closer systems that maybe don’t necessarily have an API.
In this example, I’m going to use a generic Webhook. I’m going to take the webhook. Now this will involve me doing something off screen, but that’s fine.
When I connect this Webhook, you’ll notice that the Run option in the settings have disappeared. Now, all I can do is run the cycle. Look in the settings, there is no time constraint within Cyclr. If a template or a cycle starts with a webhook, it will run as frequently as it is triggered. So whenever that webhook is hit, it will run through the cycle.
So here, I have the generic Webhook URL, I can copy that. If I go into Postman, which I’m doing off screen
I had a new URL here, I could run this cycle. You’ll see that I didn’t have the run once option, so this cycle now just listen to whenever that Webhook is hit.
Now that the cycle is running, I will send it over in Postman, I get a little notification saying the Webhook has been accepted. What should expect to see here is the template begin.
So have some set data here from a few seconds ago. We can see that I’ve successfully made a call to lists users. The Decision Step has once again filtered out all of those objects that do not match with my statement. And I’ve thrown into Google Sheets, the “automated process” user.