Workato
Workato recipes get Strkr events as triggers and the public API for writes. IT and RevOps teams standardized on Workato can plug Strkr in without a bespoke connector.
Everything Workato does inside Strkr.
- Trigger Workato recipes on Strkr events
- Full read/write via REST API
- Enterprise IPaaS governance preserved
- Pairs with native integrations
Native code, not a shim.
OAuth where available
Workato will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Workato once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Workato from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Workato is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Workato is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.