Appearance
AWS SES
Send transactional and marketing emails with Amazon Simple Email Service.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://email.us-east-1.amazonaws.com/v2 |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | aws-ses |
Using AWS SES in a workflow
- Go to Connections and click New Connection.
- Pick AWS SES 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 /v2/email/outbound-emails | Send an email |
GET /v2/email/identities | List verified identities |
POST /v2/email/identities | Verify an email identity |
GET /v2/email/templates | List email templates |
POST /v2/email/templates | Create an email template |
GET /v2/email/account | Get account details |
GET /v2/email/suppression/addresses | List suppressed addresses |
GET /v2/email/configuration-sets | List configuration sets |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /v2/email/outbound-emails
Send an email
| Detail | Value |
|---|---|
| Operation ID | cloud.sendEmail |
| Method | POST |
| Path | /v2/email/outbound-emails |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.sendEmail. - 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 AWS SES API reference.
GET /v2/email/identities
List verified identities
| Detail | Value |
|---|---|
| Operation ID | cloud.listEmailIdentities |
| Method | GET |
| Path | /v2/email/identities |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listEmailIdentities. - 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 AWS SES API reference.
POST /v2/email/identities
Verify an email identity
| Detail | Value |
|---|---|
| Operation ID | cloud.createEmailIdentity |
| Method | POST |
| Path | /v2/email/identities |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createEmailIdentity. - 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 AWS SES API reference.
GET /v2/email/templates
List email templates
| Detail | Value |
|---|---|
| Operation ID | cloud.listEmailTemplates |
| Method | GET |
| Path | /v2/email/templates |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listEmailTemplates. - 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 AWS SES API reference.
POST /v2/email/templates
Create an email template
| Detail | Value |
|---|---|
| Operation ID | cloud.createEmailTemplate |
| Method | POST |
| Path | /v2/email/templates |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createEmailTemplate. - 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 AWS SES API reference.
GET /v2/email/account
Get account details
| Detail | Value |
|---|---|
| Operation ID | cloud.getAccount |
| Method | GET |
| Path | /v2/email/account |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getAccount. - 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 AWS SES API reference.
GET /v2/email/suppression/addresses
List suppressed addresses
| Detail | Value |
|---|---|
| Operation ID | cloud.listSuppressedDestinations |
| Method | GET |
| Path | /v2/email/suppression/addresses |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listSuppressedDestinations. - 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 AWS SES API reference.
GET /v2/email/configuration-sets
List configuration sets
| Detail | Value |
|---|---|
| Operation ID | cloud.listConfigurationSets |
| Method | GET |
| Path | /v2/email/configuration-sets |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS SES connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listConfigurationSets. - 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 AWS SES API reference.