Automation integration

Make

Strkr events trigger Make scenarios and your scenarios write back via the public API. For teams that prefer visual automation, Make covers the long tail where a native integration does not pay off.

Status Coming soon
Vendor Make
Category Automation
Scope One connect per workspace
Used in
What you get

Everything Make does inside Strkr.

  • Trigger Make scenarios on Strkr events
  • Read and write any object via REST API
  • Visual scenario builder for ops teams
  • Pairs with native integrations for critical paths
How it works

Native code, not a shim.

OAuth where available

Make 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 Make once; every teammate uses the shared connection without re-authenticating.

Disconnect at any time

Admins or users can disconnect Make from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.

Make is on the roadmap.

We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Make is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.