topic Re: Workato Connector - Developer API in Workato Pros Discussion Board

Workato Connector - Developer API

saraiva — Tue, 29 Jul 2025 16:27:52 GMT

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.

Re: Workato Connector - Developer API

gary1 — Tue, 29 Jul 2025 17:28:19 GMT

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

Re: Workato Connector - Developer API

mppowe — Mon, 04 Aug 2025 18:02:50 GMT

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

Re: Workato Connector - Developer API

rajeshjanapati — Tue, 05 Aug 2025 06:09:44 GMT

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-manifest

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.

Re: Workato Connector - Developer API

saraiva — Tue, 05 Aug 2025 09:22:28 GMT

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!

Re: Workato Connector - Developer API

saraiva — Tue, 05 Aug 2025 09:26:20 GMT

Hello @rajeshjanapati (or should I say AI?),

Sorry mate, but AI answers can help when we provide the right prompt - which you don't.
I've just asked if there's an already-made connector for Workato Developer API, which I may have missed somewhere, but by the answers of other (real) users apparently there isn't.

Thanks for your effort, but I prefer sharing ideas with real people.

Re: Workato Connector - Developer API

saraiva — Tue, 05 Aug 2025 10:09:46 GMT

[UPDATE] For the sake of informing other user that bump on this same question...

There's no Workato Developer API connector at the time of writing.
However, as shared by @alain-bates here, there's the connector "CICD for Workato V3" in the community which can be a good starting point. Check it here:

Re: Workato Connector - Developer API

alain-bates — Tue, 05 Aug 2025 09:43:50 GMT

Yes, there is a connector called CICD for Workato that's included in the CI/CD and AQS accelerator packages that you can request from your customer success manager. I've used it before to automate building and exporting release packages and also to update project properties from a recipe.

A version of the connector from 2023 is available in the Community Library too (at least in the EU region).

CICD for Workato V3 adapter | Workato

Re: Workato Connector - Developer API

saraiva — Tue, 05 Aug 2025 10:04:08 GMT

Hello @alain-bates !

Thanks for sharing that connector. I haven't seen it.
That's part of the solution indeed, despite it not having all the actions I need (Test Automation for instance), it's a pretty good start. I've checked and the connector is also available in the US Data Center.
I think I'll use the authentication part of it for my custom connector.

You were very helpful!

Cheers!