Data integration

Segment

Forward every Strkr event (deal.stage_changed, lead.created, contact.updated, flow.ran) to your Segment workspace, which can fan out to BigQuery, Snowflake, Redshift, or anywhere else your data team already reads.

Status Coming soon
Vendor Twilio Segment
Category Data
Scope One connect per workspace
What you get

Everything Segment does inside Strkr.

  • Forward every Strkr event to your Segment workspace
  • Map Strkr objects to your warehouse schema
  • Replay historical events on first connect
How it works

Native code, not a shim.

OAuth where available

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

Disconnect at any time

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

Segment is on the roadmap.

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