Skip to content
ClickRuntime

Automate Segment

Keep an eye on your Segment workspace without opening it every day. Track how many events each source sends, catch destinations that stop delivering, and hear about a broken tracking setup before your reports go wrong. Describe what you want to your AI assistant, check what it will do, and it keeps running.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every morning at 7, email me yesterday's Segment event count for each source and flag any source that dropped more than 20% from the day before.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Segment

Spot a source that went quiet or a destination that is dropping events, while there is still time to fix it. These are ready-made starting points. Anything else you can describe works too.
Daily

Get a daily event count for each Segment source

Each morning you get yesterday's event volume per source, with any source down more than 20% called out.

See how it works
Hourly

Hear when a Segment destination starts failing

Within the hour, you know which destination is failing deliveries instead of finding gaps in a report later.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Segment, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Segment automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Segment should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every day, check my Segment sources and warn me if any source received far fewer events than its usual daily volume.

Every Monday, post a Slack summary of Segment event volume by source for last week, flagging sources that went quiet.

Every morning, check Segment for destinations with delivery failures, log them in Google Sheets and create a Linear issue for any destination failing two days in a row.

Beyond chat

Have Segment work when you're not in the chat

Connecting Segment to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Segment

Workspace checks use a Public API token that you create in Segment. Sending events uses a source write key instead.

Segment

Data / CDP

  1. In Segment, a Workspace Owner opens Settings, then Workspace settings, then Access Management, then Tokens, and creates a token.
  2. Choose a Public API token (not Config API), give it the Workspace Owner or Member role, and copy it straight away, because it is shown only once.
  3. If an automation should send events, open Connections, then Sources, pick the source, and copy its Write Key from Settings, then API Keys.
  4. In the ClickRuntime dashboard, save the token, and the write key if you use one, as secrets on Connections & secrets.

Good to know

Segment limits that affect automations

  • The Public API is only on Segment's Team and Business tiers, not the Free tier, so workspace checks need one of those.
  • Only Workspace Owners can create Public API tokens.
  • Segment revokes a token automatically if it is pushed to a public GitHub repository.
  • The source write key only sends events (track, identify). It cannot read workspace settings or metrics.

FAQ

Questions about automating Segment

What can ClickRuntime see in my Segment workspace?
What your Public API token allows: sources, destinations, tracking plans and their delivery metrics. It cannot see more than the token's role grants.
Which Segment plan do I need?
Team or Business. The Public API that workspace checks rely on is not available on the Free tier. Sending events with a write key works separately.
What is the difference between the token and the write key?
The Public API token manages and reads the workspace. The write key belongs to one source and only sends events to it. Store both as secrets in the ClickRuntime dashboard.
Can I use an old Config API token?
Use a Public API token. Segment no longer lets you create new Config API tokens.
Do I need AI for Segment automations?
No. Volume digests and delivery checks are plain comparisons. If you want a written summary added, AI comes with every ClickRuntime plan, so you don't need your own AI key.
Is this a Segment connector for ChatGPT or Claude?
Not for chatting with Segment data. A chat connector lets your assistant read and change Segment while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Segment event.

Related pages

Keep exploring

Tell your assistant what Segment should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude