# Import Inputs from LangSmith
Generated: 2026-11-02T05:43:11.615Z
Source build: local
Canonical docs: https://teammately.ai/docs
---
id: integrations.langsmith
title: Import Inputs from LangSmith
summary: Connect the intended LangSmith Workspace with its service key and endpoint, then explicitly import selected tracing inputs.
kind: quickstart
product_area: data_integrations
status: stable
updated: 2026-10-31
canonical: /docs/integrations/langsmith
---
# Import Inputs from LangSmith
## Prerequisites
Obtain a LangSmith service API key for the intended Workspace, its immutable Workspace ID and the API endpoint for that deployment. Review service-key access and expiration.
## Connect the Workspace
1. In LangSmith, create the service key in **Settings → API Keys**.
2. Copy the Workspace ID from **Settings → General**.
3. Open **Admin → Integrations → LangSmith** in Teammately.
4. Choose a descriptive **Display name**, enter the matching Workspace ID, key and endpoint in **Connection setup**, and add the connection.
The Teammately workspace uses one LangSmith Workspace connection. Rotate credentials on the existing connection instead of changing its intended scope accidentally.
## Select tracing inputs
In **Assets → Cases**, choose the integration, select the intended tracing Project within the connected Workspace, browse its records and explicitly import selected inputs. Connecting alone does not import traces. Reconcile imported content with [Project Input Schema](/docs/project-settings/input-schema).
## Verify and recover
Check the selected Workspace and tracing Project, then inspect actual imported Case content and source identity. For access failures, review key scope/expiration, Workspace ID and regional endpoint together. Revoking the provider key affects this connection; replace credentials through its owning connection controls.
## Related reference pages
{% related-card-grid %}
- [Import Case Examples](/docs/integrations/import-case-examples)
- [Project Input Schema](/docs/project-settings/input-schema)
- [Dataset upload troubleshooting](/docs/troubleshooting/dataset-upload)
{% /related-card-grid %}
---
id: integrations.import-case-examples
title: Import Case Examples
summary: Bring real product behavior examples into a Project and reconcile them against Project Input Schema before benchmark use.
kind: task
product_area: data_integrations
status: stable
updated: 2026-10-30
canonical: /docs/integrations/import-case-examples
---
# Import Case Examples
## Prerequisites
- A target Project and permission to work with Cases.
- The current Project Input Schema, including required input architecture and case-material fields.
- Source examples with stable provenance or customer correlation IDs.
- Any files referenced as Case materials.
- An operator who can resolve ambiguous column mappings and rejected rows.
## Before and after
| before | after |
| --- | --- |
| Source rows mix input, prior messages, context, outputs, and notes | Each admitted Case has canonical input, named Case materials, and customer-owned attributes |
| File references are local paths or source-system links | Required files are Teammately artifacts with processing state |
| Source identifiers are known only outside Teammately | Correlation IDs remain attached without replacing backend-issued Case IDs |
| No benchmark membership is implied | Imported Cases are reusable Project Assets and can be selected deliberately for benchmark work |
## Import workflow
### Task steps: Import Case examples
1. Open Project Settings and inspect **Project Input Schema**. Confirm whether the Project expects plain text, chat, or structured input and which Case materials are required.
2. Prepare a small representative sample. Separate the Case input from candidate output, human correction, and source-system bookkeeping.
3. Open the Case import flow from the Project's Cases or Case Pool surface and upload the supported source file.
4. Map source columns to input, named Case materials, and customer attributes. Do not map candidate output into Case input merely because it shares a row.
5. Preview the normalized Cases. Inspect conversations, structured values, file associations, empty required fields, and duplicate source identifiers.
6. Resolve validation and artifact-processing failures before admitting the full collection.
7. Complete the import, then inspect the admitted Cases in Assets. Confirm Case identity, current version, source context, and material readiness.
8. Add Cases to coverage or a Benchmark Dataset only after the team has reviewed whether they belong there.
## Object and state changes
Import creates reusable Project Cases and can create artifact-processing work for referenced files. Reimporting a synchronized source example can create a new Case version when canonical content changes.
Import does not automatically approve a Case, assign coverage facets, add it to every Benchmark, create a Dataset Snapshot, attach candidate outputs, or declare the Case representative.
## Success criteria
- Every admitted Case matches the current Project Input Schema.
- Input, conversation history, Case materials, attributes, and outputs remain distinct.
- Required artifacts are ready or visibly pending; none are silently missing.
- Source correlation survives without replacing Teammately Case identity.
- Rejected rows have an understood field-level reason.
- Benchmark membership remains a separate deliberate action.
## Common failure modes
- Treating every source column as arbitrary metadata instead of mapping the canonical input.
- Flattening a multi-turn conversation into one unstructured string.
- Attaching the model's answer as input rather than as external Run output.
- Relying on filenames or input text as durable Case identity.
- Importing the full corpus before validating a representative sample.
- Assuming upload completion means artifact processing and Case admission completed.
- Sending required context as a Reference Material when it must travel with each Case.
{% example-demo title="Support transcript import" %}
A source row contains a ticket ID, three messages, the assistant's answer, region, and the policy PDF used by the support specialist.
The importer keeps the ticket ID as customer correlation, represents the three-message history as chat input, attaches the PDF to the configured `policy_document` Case material, and keeps region as an attribute. The assistant answer is not stored in Case input; it can later enter as an external Run output or an accepted target through its owning workflow.
{% /example-demo %}
## Related reference pages
{% related-card-grid title="Related reference pages" %}
- [Project Input Schema](/docs/project-settings/input-schema)
- [Cases](/docs/assets/cases)
- [Integrations](/docs/integrations)
- [Cases](/docs/object-model/cases)
{% /related-card-grid %}
## Related troubleshooting pages
{% related-card-grid title="Related troubleshooting pages" %}
- [Case upload troubleshooting](/docs/troubleshooting/dataset-upload)
- [Unclear Cases](/docs/troubleshooting/unclear-cases)
- [Missing Outputs](/docs/troubleshooting/missing-outputs)
{% /related-card-grid %}
---
id: admin-console.integrations
title: Workspace Integrations
summary: Connect messaging, repository, trace-store, and training services through their own authorization and operating controls.
kind: reference
product_area: admin_console
status: stable
updated: 2026-10-30
canonical: /docs/admin-console/integrations
---
# Workspace Integrations
## Definition
Open **Admin → Integrations** to connect workspace services. Each connection supplies a specific workflow rather than a general permission to read or write every external resource.
## Fields, states, or lifecycle rules
- Messaging connections support their configured notification and test operations.
- Repository connections discover repositories accessible to the authorizing account.
- Trace-store connections supply their supported capture/import workflow.
- Training connections are selected separately by a Benchmark preparation.
- Connection state, account authorization and a successful downstream operation remain distinct.
## Messaging
Slack and Microsoft Teams have provider-specific connection controls. For Teams, installation and a personal-message test are distinct operations. Workspace settings alone do not confirm installation or that automatic notifications are enabled.
Read provider errors as operational outcomes rather than treating a visible integration card as proof of delivery.
## Repositories and trace stores
GitHub.com, GitLab.com and Bitbucket Cloud connections discover the repositories allowed by the account and installation. Bind the intended repository through Reference Materials and inspect its indexed content.
LangSmith and Langfuse have their own connection surfaces. Keep original record identity and scope when importing material; connected access does not approve the captured behavior.
## Training and inference
Weights training selects an active service connection, supported model and compatible method. Connection checks do not certify quota, create-job permission, storage access or training quality.
Some evaluation paths require an existing callable inference deployment. A training job does not automatically allocate serving resources for every service. The deployment-to-output association can be user-reported where the adapter identifies it that way.
## Credentials and resource boundaries
For setup steps and provider-specific recovery, use the [integration guides](/docs/integrations#connection-setup-guides). Each guide distinguishes workspace connection, Project selection and a successful downstream operation.
Use the provider's owning connection flow and approved secret mechanism. Keep access scoped to the authorized account, identity and resource. Existing Vertex and Baseten training adapters do not authorize Google platform storage, ambient developer credentials or a provider fallback.
A failed service operation should remain actionable in its owning workflow rather than being hidden by a substitute local service.
## Related task pages
{% related-card-grid title="Related task pages" %}
- [Reference Materials](/docs/agent-setup/reference-materials)
- [Export, Train, and Evaluate](/docs/weights-training/exports-and-training)
- [Fieldloop](/docs/fieldloop)
- [Admin Console](/docs/admin-console)
{% /related-card-grid %}