Zapier
For the 5,000+ apps where a native integration does not make sense. Strkr events trigger Zaps and your Zap writes back via the public API. Native integrations should always win on cost and latency, so plan on using Zapier only as a fallback.
Everything Zapier does inside Strkr.
- Trigger Zaps on deal stage changes, lead routing, and more
- Read and write any object via the public REST API
- Covers the long tail without native engineering investment
Native code, not a shim.
OAuth where available
Zapier 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 Zapier once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Zapier from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Zapier is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Zapier is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.