The Parameters tab can be used to define numerous types of parameters.
I’m just going to type in the target name here.
So by default, the target type is set to a query string.
This will just add a query string to the end of the endpoint.
You can add also add extra HTTP headers to the request, you can set a merge field, if there are parts of the URL or endpoint that needs to be filled in, for example, an ID from the previous step. If you have a merge field setup for that ID, you set the mappings here and then it will show up in the connector step setup.
For example, here we have a merge field called pet ID. And if we go to the Settings page, we can see that there is a merge field at the end of the URL for the pet ID. So in this, I can now place a pet ID value.
And Cyclr will be able to automatically map that fill that in for the URL and will get the specific information for that pet.
Merge fields are always defined with curly braces.
And that way, when you define the URL Cyclr knows that it’s a place for a merge field to be filled. When you set them up as a parameter, you do not need the curly braces, you just need to match the text that is held inside.
You may wish to have a dynamic lookup on the field. In this example, pet IDs, a dynamic lookup anytime you feel is available in a request, I might want to make it easier to be able to look up an ID specifically.