Integrations

CT Networks works on top of the systems you already use

Coworkers operate on real event context from the tools event teams already run. Each integration is scoped to specific actions, audit trails, and the workflows it unlocks.

SupportedIn progressPlanned

Ticketing & payments

Stripe

Supported

Live attendee orders, refunds, and abandoned checkouts attached to the event workspace.

Actions

  • Read order and refund history
  • Trigger reminders against incomplete checkouts

Workflows it enables

Email

Email (transactional)

Supported

Outbound communication for confirmations, reminders, and approval-bound coworker messages.

Actions

  • Send templated reminders inside playbook runs
  • Hold sensitive sponsor and speaker outreach in the approval queue

Calendar

Google Calendar

In progress

Event schedule, session rooms, and speaker call times for the coworker team.

Actions

  • Read schedule into the workspace context
  • Surface schedule conflicts in the command center

Spreadsheets

Google Sheets

In progress

Existing rosters, sponsor trackers, and staffing sheets brought into the event workspace without rebuilding them.

Actions

  • Sync rows into rosters
  • Read sponsor deliverable trackers into sponsor playbooks

CRM

HubSpot

Planned

Sponsor and partner relationship history available to the Sponsor Operator.

Actions

  • Read sponsor account history
  • Write sponsor activity back to the CRM with attribution

Workflows it enables

Messaging

Slack

Planned

Operator notifications, escalations, and approval pings inside the team's existing workspace.

Actions

  • Send approval requests to operators
  • Surface live incidents to a command-center channel

Workflows it enables

Analytics

Posthog

Planned

Funnel and engagement signals from the registration and event surfaces.

Actions

  • Read drop-off and conversion events into the workspace
  • Surface anomalies as command center alerts

Storage

File storage

Planned

Sponsor assets, speaker decks, and event runbooks tracked alongside coworker activity.

Actions

  • Attach files to playbook runs and approval requests
  • Track missing assets against contracted deliverables

Don't see your stack?

Integrations are added as the workflows that need them mature. If your event team depends on a system that isn't listed, tell us which workflow it would unlock and we'll prioritize it against our roadmap.