SevenRooms Connector

Connect SevenRooms to your data stack with Weld. Fully managed pipelines, set up in minutes, ready for your agents.

Start for free

4.8 on G2

Weld · Data Sources

SevenRoomsYour warehouseLive

venue64 columnsSynced

reservation98 columnsSynced

reservation_request32 columnsSynced

reservation_feedback15 columnsSyncing

client76 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

SevenRooms

Data source

Authenticating...

Ready to connect

Overview

SevenRooms in your warehouse.
Ready for your agents.

Weld's SevenRooms connector is fully managed: it extracts data from SevenRooms, 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

SevenRooms data schema.
The map your agents read.

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

tables: 10
fields: 396
relationships: 11

venue_group_client_id

external_client_notes

cancellation_policy_id

string

cancellation_policy

string

custom_booking_policy

string

custom_cancellation_policy

sevenrooms_public_key

shift_categories_display

venue_group_client_id

external_reference_code

unique_confirmation_prefix

string

Open the schema explorer Open the full schema explorer

Models

SevenRooms models.
What the numbers mean.

Open-source SQL that turns the raw SevenRooms 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 SevenRooms.

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

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

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextSevenRoomstables10fields396joins11

How many reservation rows do we have per venue? Use our SevenRooms data.

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

●weld·search_available_references

⎿raw.seven_rooms.reservation

raw.seven_rooms.venue

+ 8 more SevenRooms tables

●weld·get_reference_schema

⎿reservation · 98 columns

joins venue on venue_id

●weld·run_query

⎿select v.id, count(*) from {{raw.seven_rooms.reservation}} r

join {{raw.seven_rooms.venue}} v on r.venue_id = v.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from SevenRooms data in your warehouse

>Ask about your SevenRooms dataMCP

Destinations

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

Resources

Everything you need.
To get started.

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 SevenRooms 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 SevenRooms ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "seven-rooms",
    "destination_schema_name": "seven-rooms_data",
    "sync_interval": "0 * * * *"
  }'
▌