n8n
Fire Strkr webhook events into a self-hosted or n8n Cloud workflow. Developer-leaning teams get full control over where data lives and how it transforms. Native Strkr endpoints stay the fast path; n8n covers the custom tail.
Everything n8n does inside Strkr.
- Trigger n8n workflows on Strkr events
- Self-hosted or n8n Cloud supported
- Full read/write via REST API
- Keeps automation code in your repos
Native code, not a shim.
OAuth where available
n8n 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 n8n once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect n8n from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
n8n is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If n8n is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.