Email and messaging
Connect SendGrid
Your application calls one EchoRelay URL. When SendGrid changes its API, you update the mapping, not your application.
How SendGrid signs requests
An API key, sent as a bearer token in the Authorization header.
Can you connect it today?
Yes. Add a bearer-token credential with your SendGrid API key.
A sample mapping
Your application sends the first request below. The mapping turns it into the body of PUT /v3/marketing/contacts, shown second.
Your request
{
"people": [
{
"email": "ana@example.com",
"firstName": "Ana"
}
]
}
What SendGrid receives
{
"contacts": [
{
"email": "ana@example.com",
"first_name": "Ana"
}
]
}
The mapping
{
"$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
"root": {
"type": "object",
"id": "root",
"properties": {
"contacts": {
"type": "arrayMap",
"id": "contacts",
"source": {
"type": "field",
"id": "people",
"path": "people"
},
"element": {
"type": "object",
"id": "contact",
"properties": {
"email": {
"type": "field",
"id": "email",
"path": "email"
},
"first_name": {
"type": "field",
"id": "first-name",
"path": "firstName"
}
}
}
}
}
}
}
The grammar, the answer mapping and the dry run are in the mapping docs.
What you bring
This is not a ready-made connector. You bring a sample request or SendGrid’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.
SendGrid facts on this page were read 2026-10-29 from SendGrid API authentication, SendGrid API reference: add or update a contact. Another service? Check it here.
Connect everything. Deploy nothing.
No credit card required.