Get source
Retrieve selected source configuration and tracking-plan ID without write keys or settings.
Connector library
Segment connector.
Inspect Segment workspace source and destination configurations through selected metadata summaries, including source-to-destination connections.
Connector download
Download Segment
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Base URL
- Package size
- 9 KB
- SHA-256
3caba9edb4184d091f97b671060eaa060bb7d186c225d2c322116fdf11a6a1fe
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-03 · Implemented source
Inspect Segment workspace source and destination configurations through selected metadata summaries, including source-to-destination connections.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Retained immutable historical scaffold archive.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
List sources
Return selected source summaries using the explicitly documented alpha pagination contract.
Get destination
Retrieve selected destination configuration without settings or embedded credentials.
List destinations
Return one page of selected destination configurations in the workspace.
List connected destinations
Return a page of selected destination configurations connected to a source using the documented alpha pagination contract.
Vendor API
API and access
Implementation considerations
- Confirm consent fields, subscription status, suppression rules, required identifiers, and workspace/account scope.
- For broad marketing APIs, start with contact CRUD, event tracking, list or segment membership, and reporting reads.
- Avoid overwriting consent, source, or attribution fields without explicit customer mapping rules.
Related connectors
More in Marketing, Analytics & Revenue APIs
Support
Need help with Segment?
Tell us what you need to connect or change.