Traede Connector

Traede is a B2B platform designed to streamline wholesale operations for fashion brands and retailers.

Start for free View documentation

4.8 on G2

Weld · Data Sources

TraedeYour warehouseLive

variant19 columnsSynced

product19 columnsSynced

order47 columnsSynced

invoice22 columnsSyncing

customer19 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Traede

Data source

Authenticating...

Ready to connect

Overview

Traede in your warehouse.
Ready for your agents.

Traede is a B2B platform designed to streamline wholesale operations for fashion brands and retailers. Weld's Traede connector is fully managed: it extracts data from Traede, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

Traede data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Traede is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 32
fields: 359
relationships: 16

production_order_delivery_note

variant

Traede models.
What the numbers mean.

Open-source SQL that turns the raw Traede tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions, not guesses.

Open the models

Weld MCP server

Ask your agent.
It already knows Traede.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Traede context, finds the tables it needs and queries your warehouse.

Agent contextTraede tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextTraedetables32fields359joins16

How many invoice rows do we have per customer? Use our Traede data.

Reading the Traede context first, so the query uses the right tables and keys.

●weld·search_available_references

⎿raw.traede.invoice

raw.traede.customer

+ 30 more Traede tables

●weld·get_reference_schema

⎿invoice · 22 columns

joins customer on customer_id

●weld·run_query

⎿select c.id, count(*) from {{raw.traede.invoice}} i

join {{raw.traede.customer}} c on i.customer_id = c.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from Traede data in your warehouse

>Ask about your Traede dataMCP

Destinations

Load Traede into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

Traede setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Traede connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Traede ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "traede",
    "destination_schema_name": "traede_data",
    "sync_interval": "0 * * * *"
  }'
▌