Add Labels to Source
Tool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
Twilio Segment is a customer data platform that helps businesses collect, clean, and control their customer data.
Tool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
Tool 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.
Tool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation.
Fetch daily API call counts by Segment Source for a given reporting period. Optional page size and cursor parameters let you navigate the results. An empty result does not necessarily establish that there was no usage.
Retrieve a Segment Destination's configuration by its unique ID using the configured region.
Import historical events in bulk into Segment with their original timestamps, for backfilling past activity. Imports use the US tracking service even when the workspace is configured for the EU region.
List warehouses connected to a Segment Source by source ID. Specify a page size from 1 to 1,000 and an optional cursor to navigate results. An empty result does not necessarily establish that no warehouses are connected.
Get an event delivery metrics summary for a Destination and Source. An HTML response may produce an empty metrics list rather than actual delivery data.
Retrieve schema configuration settings for a Segment Source by its ID, including settings for track, identify, and group calls. Returned settings may include placeholders rather than the Source's actual configuration.
Remove a specified write key from a Segment Source, for example during security maintenance or key rotation. A reported success does not always independently confirm that the key was revoked.
Tool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities.
Tool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits.
Tool to identify a user and set/update traits via Segment HTTP Tracking API.
Tool to record a page view via Segment HTTP Tracking API. Use when sending page views with optional page name and properties.
Tool to record a mobile app screen view. Use when tracking screen views in a mobile app via Segment HTTP Tracking API.
Tool to record a custom user event via Segment HTTP Tracking API. Use when sending events to Segment with valid identity.
Update an existing Segment Source by ID, changing its name, slug, enabled status, or type-specific settings. Provide at least one of these fields. The returned Source may reflect the submitted values rather than independently confirmed settings.
The Segment integration connects your Dench AI CRM directly to Segment, so agents can read and act on your Segment data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
17 actions are available for agents to invoke on your behalf. Every call runs through Segment's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Segment and click Connect — you'll authorize access through Segment's own sign-in flow. No API keys or code required.
Ask an agent to use Segment in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Segment integration connects your AI CRM to Segment, so AI agents can work with your Segment data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Segment integration currently exposes 17 actions, including Add Labels to Source, Batch Segment Analytics Events, Delete Source, Get Daily Per Source API Calls Usage, Get Destination, and Import Historical Data. Agents invoke them on your behalf from chat or from automations.
No. You connect Segment from your Dench workspace using Segment's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Segment's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Segment connection from your workspace settings at any time.