Now, when you’re using Cyclr, you might want to create your own connectors as opposed to using something in a library where you might feel that you don’t need us to build it out.
In this instance, you’ll be using something called a custom connector.
So the first thing we’re going to look at is how we get started with using custom connectors. So we’re going to do on the left hand side, click on connectors, go down to custom connectors, not all of you will have this enabled as price plan dependent.
And what I want to do is create a new connector.
What I’m going to show you for the sake of this video is how you can import swagger documentation to be able to generate a connector relatively easily without much hassle.
So what I want to click is generated from OpenAPI specification.
Now I have an OpenAPI URL option, and the option to upload an icon or I have the specification here. So if I have the JSON or the YAML, I can base that entire contract into here. And Cyclr will generate it, providing that it’s OpenAPI 2.0 or 3.0 compliant.
So what I’m going to do is take
this open API spec, I’m just doing the Pet Store for this example.
Not going to upload any images for this,
I’m just going to click Generate.
Now what you’ll see is Cyclr takes you through what’s been created, if there are any issues with the generation in this case, it’s the authentication.
Also produces let you know what’s going on what’s to be expected when you click inside the release.
So I’m going to click Continue. I’ve got eight methods now in the connector.
And now I can start customising it.
So if I wanted to change the authentication, but wanted to look at the methods here, I wanted to add scripts, etc, this is where I would do it, I’m just gonna add a quick note. So I know that this is the initial release of this connector.
And then I’m gonna save it.
Once I’ve done all my customizations, or my changes, what I’m going to do is publish the draft. And what you’ll see now is I have a live version of the Pet Store connector.