Skip to content
For LLMsView as Markdown·

SendGrid

Send transactional and marketing emails via the SendGrid API.

DetailValue
CategoryCommunication
Base URLhttps://api.sendgrid.com/v3
AuthenticationBearer Token
Endpoints6
Connector keysendgrid

Using SendGrid in a workflow

  1. Go to Connections and click New Connection.
  2. Pick SendGrid from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
POST /mail/sendSend an email
GET /marketing/contactsList all contacts
PUT /marketing/contactsAdd or update contacts
GET /marketing/listsGet all mailing lists
GET /templatesList transactional templates
GET /statsGet 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

DetailValue
Operation IDemail.send
MethodPOST
Path/mail/send

Parameters

No parameters.

Request Body

FieldType
personalizationsarray
fromobject
subjectstring
contentarray

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.send.
  4. 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

DetailValue
Operation IDemail.listContacts
MethodGET
Path/marketing/contacts

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listContacts.
  4. 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

DetailValue
Operation IDemail.upsertContacts
MethodPUT
Path/marketing/contacts

Parameters

No parameters.

Request Body

FieldType
contactsarray

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.upsertContacts.
  4. 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

DetailValue
Operation IDemail.listMailingLists
MethodGET
Path/marketing/lists

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listMailingLists.
  4. 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

DetailValue
Operation IDemail.listTemplates
MethodGET
Path/templates

Parameters

NameLocationTypeRequired
generationsquerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.listTemplates.
  4. 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

DetailValue
Operation IDemail.getStats
MethodGET
Path/stats

Parameters

NameLocationTypeRequired
start_datequerystringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your SendGrid connection from the Connection dropdown.
  3. In the Operation dropdown, select email.getStats.
  4. 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.