Sendgrid Connector

SendGrid provides a cloud-based service that assists businesses with email delivery. The service manages various types of email including shipping notifications, friend requests, sign-up confirmations, and email newsletters.

4.8 on G2
Weld · Data Sources
SendgridLive
segmentSynced
senderSynced
legacy_campaignSynced
legacy_segment_recipientSyncing
legacy_segment_recipient_custom_fieldQueued
Lands insnowflakebigquerydatabricksAgent context over MCP
How it works

Set up in minutes.
No code, no maintenance.

Sendgrid

Sendgrid

Data source

Authenticating...
Ready to connect
Overview

Sendgrid in your warehouse.
Ready for your agents.

SendGrid provides a cloud-based service that assists businesses with email delivery. The service manages various types of email including shipping notifications, friend requests, sign-up confirmations, and email newsletters. Weld's Sendgrid connector is fully managed: it extracts data from Sendgrid, 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.

AgentsQuery over MCPYour warehouse40 tables, with agent contextWeldExtract, load, keep in syncSendgridSource
Agent context

Sendgrid data schema.
The map your agents read.

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

tables
40
fields
335
relationships
5
Open the schema explorer
Open the full schema explorer
Weld MCP server

Ask your agent.
It already knows Sendgrid.

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

  • Agent contextSendgrid tables, fields and joins
  • QuerySQL against your warehouse
  • OperateCheck, rerun and refresh syncs
Claude CodeOpus 5
>

How many legacy_campaign rows do we have per sender? Use our Sendgrid data.

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

●weld·search_available_references
⎿raw.sendgrid.legacy_campaign
raw.sendgrid.sender
+ 38 more Sendgrid tables
●weld·get_reference_schema
⎿legacy_campaign · 12 columns
joins sender on sender_id
●weld·run_query
⎿select s.id, count(*) from {{raw.sendgrid.legacy_campaign}} l
join {{raw.sendgrid.sender}} s on l.sender_id = s.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Sendgrid data in your warehouse
>Ask about your Sendgrid data
Weld Connect API

Set it up in code.
One REST API.

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

POST/elt_syncs
▌
FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Talk to us

Put your Sendgrid data to work.

Connect Sendgrid, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

SendgridSource
WeldWeld
MCPAgents