Configured with the customer
Trace expects to define identifiers, fields, access and queries during pilot scoping. This is not a one-click integration.
Integration readiness · No fake marketplace
Map the shortest safe path to the evidence.
Trace is not claiming a catalogue of live, self-serve connectors. Early pilots are scoped source by source, using controlled exports, manual imports or customer-approved least-privilege access where feasible.
Read the status before the logo
A named source is not a live connector claim.
Every status describes the proposed path for an early pilot. It does not promise general availability, instant setup or production readiness.
Evidence supplied under agreement
The customer produces a controlled export or file package. A transfer channel and deletion plan must be agreed before real data moves.
Not offered as a connector
The retrieval path is a design direction still requiring technical and security validation.
Research, not availability
Trace is evaluating data relevance, API constraints and demand. No implementation date is promised.
Current truth: Trace has not published evidence of live automated connectors. The directory below is an honest readiness map for manual pilot scoping.
Source directory
What Trace would look for—and the limits around it.
Open a source to see expected data, access approach, likely request relevance and the limitation that must travel with the result.
Identity
Profiles and authentication metadata that may support identity matching and source discovery.
Auth0 User identity and authentication metadata. Under evaluation
Proposed access path
Proposed scoped Management API access.
Likely request relevance
Identity support and access evidence.
Readiness limit
Not currently offered as an automated connector.
Clerk User profiles and authentication metadata. Under evaluation
Proposed access path
Proposed scoped backend API access.
Likely request relevance
Identity support and access evidence.
Readiness limit
Not currently offered as an automated connector.
Billing
Customer, subscription, invoice and payment metadata with retention questions kept visible.
Stripe Customer, subscription, invoice and payment metadata relevant to the requester. Pilot mapping
Proposed access path
Restricted API key or a controlled export.
Likely request relevance
Access and portability evidence; deletion depends on lawful retention decisions.
Readiness limit
Trace flags retention questions for authorised review.
Open the source-specific workflow →Support & CRM
Contacts, tickets and conversations that often sit outside the primary product database.
Intercom Contacts, conversations and support metadata. Manual import
Proposed access path
Customer export during early pilots.
Likely request relevance
Access and correction evidence.
Readiness limit
Automated retrieval is planned, not live.
HubSpot Contacts, companies, tickets and consent-related properties in scope. Manual import
Proposed access path
Customer export or scoped private app under pilot agreement.
Likely request relevance
Access, correction and deletion evidence where applicable.
Readiness limit
Portal-specific configuration is required.
Zendesk User profiles, tickets, comments and attachments. Planned
Proposed access path
Proposed read-only API scope.
Likely request relevance
Access and correction evidence.
Readiness limit
Under technical validation.
Data
Application records and stored objects identified through the customer’s schema and request scope.
Supabase Auth profiles, application tables and storage references selected during scoping. Pilot mapping
Proposed access path
Customer-approved, least-privilege access or a controlled export.
Likely request relevance
Access, portability and deletion evidence where applicable.
Readiness limit
No one-click connector is claimed. Retrieval is configured per pilot.
Open the source-specific workflow →Firebase Authentication records, Firestore collections and storage references in agreed scope. Pilot mapping
Proposed access path
Scoped service access or customer-generated export.
Likely request relevance
Access, portability and deletion evidence where applicable.
Readiness limit
Collection structure and security rules are reviewed during setup.
Open the source-specific workflow →Postgres Agreed tables and related requester records. Pilot mapping
Proposed access path
Read-only database role, replica, query runner or export.
Likely request relevance
Depends on schema and controller instructions.
Readiness limit
Custom queries require customer validation.
S3-compatible storage Objects linked to the requester through agreed identifiers. Manual import
Proposed access path
Scoped manifest or customer-provided package.
Likely request relevance
Access and portability evidence.
Readiness limit
Broad bucket access is not a default.
Custom
Controlled evidence paths for systems without a named integration approach.
Secure export Customer-selected evidence files. Manual import
Proposed access path
Agreed secure transfer channel.
Likely request relevance
Depends on request type and the evidence the customer can validly supply.
Readiness limit
Early pilots prioritise controlled exports over broad access.
Read-only API Customer-defined endpoints and response fields. Pilot mapping
Proposed access path
Least-privilege credentials with revocation controls.
Likely request relevance
Defined during scoping.
Readiness limit
Subject to technical and security review.
Access strategy
The first question is not “Can we connect?”
It is “What is the smallest, revocable path that can produce useful evidence under the agreed scope?”
- 01
Can the customer produce a controlled export?
For a first case, an export may reduce standing access and speed up validation. File transfer, integrity checks, storage and deletion still need an agreed method.
- 02
Would a narrow read-only role be safer?
Where repeated retrieval is justified, the design should restrict systems, tables, objects, endpoints and operations. “Read-only” still requires security review.
- 03
Can the customer run the retrieval?
A reviewed query, manifest or API export can keep credentials and execution inside the customer environment while preserving a documented evidence path.
- 04
What remains manual or unknown?
Unmapped tools, inconsistent identifiers and access failures become case warnings. Trace should not infer completeness from the sources it happened to reach.
Pilot source map
What implementation needs to establish.
The source map is the operational contract between the request and the evidence. It should be understandable without knowing the customer’s entire architecture.
System owner
Who can approve access, validate a query and explain the source.
Requester identifiers
Which stable identifiers link the person across systems—and where matching may fail.
Fields and objects
The in-scope records, attachments and metadata, plus known exclusions.
Access and revocation
How evidence can be retrieved, who grants access and how it is removed.
Retention questions
Where deletion requests may conflict with documented legal or operational retention.
Completion evidence
What proves the source was checked and which gaps must be disclosed to the reviewer.
Do not send credentials or personal dataApply with system names, scale and the current workflow.
Map my stack A controlled first request
Your first useful integration may be a better source map.
Start with the systems likely to matter for one request. Trace will propose an access path only after technical fit and security expectations are understood.