Appearance
SendGrid
Send transactional and marketing emails via the SendGrid API.
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.sendgrid.com/v3 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | sendgrid |
Using SendGrid in a workflow
- Go to Connections and click New Connection.
- Pick SendGrid from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /mail/send | Send an email |
GET /marketing/contacts | List all contacts |
PUT /marketing/contacts | Add or update contacts |
GET /marketing/lists | Get all mailing lists |
GET /templates | List transactional templates |
GET /stats | Get email statistics |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /mail/send
Send an email
| Detail | Value |
|---|---|
| Operation ID | email.send |
| Method | POST |
| Path | /mail/send |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
personalizations | array |
from | object |
subject | string |
content | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.send. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.
GET /marketing/contacts
List all contacts
| Detail | Value |
|---|---|
| Operation ID | email.listContacts |
| Method | GET |
| Path | /marketing/contacts |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.listContacts. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.
PUT /marketing/contacts
Add or update contacts
| Detail | Value |
|---|---|
| Operation ID | email.upsertContacts |
| Method | PUT |
| Path | /marketing/contacts |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
contacts | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.upsertContacts. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.
GET /marketing/lists
Get all mailing lists
| Detail | Value |
|---|---|
| Operation ID | email.listMailingLists |
| Method | GET |
| Path | /marketing/lists |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.listMailingLists. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.
GET /templates
List transactional templates
| Detail | Value |
|---|---|
| Operation ID | email.listTemplates |
| Method | GET |
| Path | /templates |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
generations | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.listTemplates. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.
GET /stats
Get email statistics
| Detail | Value |
|---|---|
| Operation ID | email.getStats |
| Method | GET |
| Path | /stats |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
start_date | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your SendGrid connection from the Connection dropdown.
- In the Operation dropdown, select
email.getStats. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream SendGrid API reference.