Segment for AI agents
Agents read Segment at once. Changes and sends are held for a person's approval by default.
About Segment
Twilio Segment is a customer data platform that helps businesses collect, clean, and control their customer data.
What an agent can do in Segment
Every Segment action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Segment without asking first. 5 actions.
- Get Daily Per Source API Calls UsageTool to fetch daily API call counts per source for a given period. Use when you need daily breakdown of API usage by source after determining the reporting period.
- Get DestinationTool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint;
- List Connected Warehouses From SourceTool to list warehouses connected to a Source. Use when you need to retrieve warehouses for a given source ID.
- List Delivery Metrics Summary from DestinationGet an event delivery metrics summary from a Destination. Primary attempt uses Segment Public API; fallback to legacy app host if needed. On HTML fallback responses, returns a minimal valid envelope t
- List Schema Settings in SourceRetrieve schema configuration settings for a Source.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 12 actions.
- Segment AliasTool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities.
- Batch Segment Analytics EventsTool to send multiple analytics calls in a single batch request. Use when you want to reduce HTTP overhead by batching Identify/Track/Page/Screen/Group calls into one request.
- Delete SourceTool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation.
- Segment GroupTool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits.
- Segment IdentifyTool to identify a user and set/update traits via Segment HTTP Tracking API.
- Import Historical DataTool to import historical data in bulk with support for historical timestamps. Use when you need to backfill or import past events with their original timestamps into Segment.
- Segment Page ViewTool to record a page view via Segment HTTP Tracking API. Use when sending page views with optional page name and properties.
- Segment Screen EventTool to record a mobile app screen view. Use when tracking screen views in a mobile app via Segment HTTP Tracking API.
- Segment Track EventTool to record a custom user event via Segment HTTP Tracking API. Use when sending events to Segment with valid identity.
- Update SourceTool to update a Source's metadata and settings. Use when you need to modify an existing Source after confirming its ID.
- Add Labels to SourceTool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
- Remove Source Write KeyTool to remove a write key from a Source. Use when you need to revoke an existing write key for security or rotation.
Changes wait in Needs you
Changes and sends in Segment are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Segment questions
Can an agent change data in Segment on its own?
Not by default. Changes and sends in Segment are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Segment?
This connector lists 5 read actions. Reads run at once, without waiting for approval.
How does Segment connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.