Connections and secrets · connections/

Connect the tools you keep. The credentials stay with the platform.

The tools you keep, connected once for the whole workspace. Pipelines, ontology actions and the company agent all use the same connections, and none of them ever holds a token.

Connections declared in code and authorised here. The credentials stay with the platform, never in the repository.

segmentstream.com
The console's connections page: the 43 connections declared in our workspace's code, here the public reference lists of AI and search crawlers, each connected, with the key it is declared under

100+ pre-built integrations

Every major ad, affiliate and analytics platform, and the CRM, commerce, finance and messaging tools companies run, each connected once for the whole workspace.

100+ pre-built integrations, and any other service with an API connects the same way.

Pre-built integrations

100+ pre-built integrations: Google Ads, Meta, TikTok, LinkedIn, Microsoft, Amazon, The Trade Desk, Criteo, Awin and every other major ad platform, plus GA4, Shopify, HubSpot, Salesforce, Stripe, Klaviyo, Slack and more. Any other API connects with a key, OAuth 2.0 or client credentials.

Managed OAuth, already approved

Google Ads, Meta, Microsoft Advertising, TikTok, LinkedIn, X, HubSpot, Gmail, Google Sheets and WhatsApp connect through SegmentStream’s own approved applications. A member signs in once; there are no developer tokens to apply for and no app review to pass, and tokens refresh on their own.

Or your own app

Where a provider allows it, connect through your own app or a token you supply instead. The method changes only how the credential is obtained, never what the connection can do. Slack apps are created for you from the console.

Declared in code, held by the platform

Connections are declared in connections/ and authorised in the console. Calls go through the platform, so credentials never reach your code, your logs or an agent’s context.

MCP servers as connections

Connect any MCP server and its tools become tools of your workspace: the company agent and your team’s AI tools use them under the same roles as everything else.

Send data back out

Data goes back out through the same connections: offline conversions to ad platforms, lead grades to your CRM, rows to a sheet, from a pipeline or when someone acts on a record.

Inside actions

An ontology action can call a connection for one record: enrich a lead from Apollo, create a Stripe customer when a deal is won.

Pipelines and the agent

The same connections feed pipelines, and the company agent's channels run on them.

Secrets

Named workspace secrets for pipeline code, created from a file and never returned by the API.

In code

connections/connections.py
# connections/connections.pyfrom segmentstream_connections import (    ApolloConnection,    HubSpotConnection,    StripeConnection,    TelegramBotConnection,)connections = (    HubSpotConnection(key="hubspot"),    StripeConnection(key="stripe"),    ApolloConnection(key="apollo"),    TelegramBotConnection(key="telegram"),)
Pipeline SDK reference →

Use it, build on it, or have it built

Use it

Authorise Google Ads, HubSpot, Stripe and others in the console.

Build it with your agent

Your agent declares a connection for any API with a key and verifies it before anything uses it.

Have our engineers build it

Our engineers connect the tools you run today during a pilot.

Replaces Credential spreadsheets, API keys in environment variables and Connector setup in every tool.

Works with

Solutions built with it

Read more

Enterprise pilot

Start a pilot.

Want connections and secrets set up for you? Our forward-deployed engineers build it with you in your workspace, as code you own.

  • One solution, on your data, in your own workspace
  • First version live in two weeks
  • Parity proven before anything is switched off
  • Fixed scope and price, credited to your contract if you continue

Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.

How the pilot works

Goes to our founder’s inbox. No sales queue, no newsletter.

Build your company’s own software. Let agents run it.

$ segmentstream workspace create acme --region eu --subdomain acme

▸ Created workspace acme · database, warehouse and a private git repository

$ segmentstream workspace WORKSPACE-ID clone acme && cd acme

▸ your coding agent builds what your team asked for and runs the checks

$ git add -A && git commit -m "First version"

$ segmentstream deploy

▸ app, company agent, API and MCP tools live for your invited members

Start a pilot

Our engineers build the first version on your data in two weeks, at a fixed price.

Or build it yourself with your coding agent:

curl -fsSL https://segmentstream.com/install.sh | sh

We’ll email you product updates, tips and onboarding help. Unsubscribe anytime.