Segment

Category: Data / Analytics (CDP)
Connect by: Paste an API key
Official API docs: https://segment.com/docs/connections/sources/catalog/libraries/server/http-api/

What the agent can see

None.

What the agent can do

Capability	API call	Risk	Needs approval
Record an action a user performed: an event name + optional properties (requires userId and/or anonymousId). (docs)	POST /v1/track	🟢 low	— no
Tie a user to their actions and set traits about them (requires userId and/or anonymousId). (docs)	POST /v1/identify	🟢 low	— no
Associate a user with a group (account/org/company) and set group traits (requires groupId plus userId and/or anonymousId). (docs)	POST /v1/group	🟢 low	— no
Record a page view with an optional name + properties (requires userId and/or anonymousId). (docs)	POST /v1/page	🟢 low	— no

Connecting it

• You provide: Source Write Key
• Where to get it: Segment workspace → Sources → your source → Settings → API Keys → copy the Write Key. NOTE: the HTTP Tracking API is WRITE-ONLY — it ingests events/identities and forwards them to your source's connected destinations; there is no read endpoint, so this connector can SEND analytics but cannot query data back.
• Permissions/scopes: none / not scope-based

Account setup

• Account needed: A Segment workspace with at least one Source that has a Write Key.
• App registration: None — the Source Write Key is the only credential (HTTP Basic).
• Verification required: None for the Tracking API.
• Testing: Create a free/dev Segment source and use its Write Key; the source's debugger shows ingested events live.

Limits

Max 32 KB per message and 500 KB per batch (≤2500 events/batch). Segment recommends ≤1000 requests/sec and may queue excess. Invalid JSON / oversize → HTTP 400; invalid Write Key → HTTP 401; accepted → HTTP 200 {"success": true}.