Workato Connector - Developer API

[saraiva]

Hello community,

In an effort to enhance our CICD pipeline, I was investigating Workato's Developer API (documentation: https://docs.workato.com/en/workato-api.html).
Is there an already made connector to access this API?
I searched in the Community library, but no success. Do you know if it exists? Or do I need to build the connector myself?

Thanks in advance for your time.

[gary1]

A Workato connector for a Workato API? That would be too easy... 🙃

[mppowe]

Yea it's a bummer, you'd think there'd be an easier way to access them.  I had to do this a while back too, and it involved making a generic HTTP connector using https://www.workato.com/api/ as the base url and a Header auth with a token, but I think that's deprecated now.  See their doc: https://docs.workato.com/en/workato-api.html#base-url 

[saraiva]

Hello @mppowe !

I'm already building a "Workato Developer API" connector - I don't want to use the generic HTTP connector. I hope I'll release it to the community one day (the API is quite extensive, so it will take some time).

Thanks for your feedback!

[rajeshjanapati]

Hi @saraiva ,

As of now, I guess there is no pre-built connector specifically for accessing Workato's Developer API or for implementing CI/CD pipelines directly. However, you can definitely achieve this by leveraging the Developer APIs that Workato provides.

For example:

• You can use the Export Manifest API to retrieve recipe package.

• Then, use the Retrieve Package Download URL API to download the package and store it in your desired location (e.g., a GitHub repo or local folder).

• For deploying to another environment, the Import Package API can be used along with the appropriate folder ID of the destination environment.

This approach allows you to build a CI/CD pipeline manually and also integrate version control by syncing your recipes with GitHub using GitHub Actions or similar CI tools.
docs url: https://docs.workato.com/en/workato-api/recipe-lifecycle-management.html#export-package-based-on-a-m...

and base URL changes based on your workspace region.

Let me know if you’d like a step-by-step breakdown or need help setting this up.