> ## Documentation Index
> Fetch the complete documentation index at: https://docs.botcadence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS SES

> Send email from a verified Amazon SES identity

AWS SES lets Botcadence send campaign, nudge, and automation email from an address or domain you have verified in Amazon SES. It also powers the [Send with AWS SES](/docs/build/workflows/tools/send-ses) tool.

## Before you connect

Prepare these values from AWS:

* An **AWS Access Key ID** and **AWS Secret Access Key** with permission to send email through SES
* The verified **From Address** you want recipients to see
* The AWS **Region** where the SES identity is verified

The access key should be limited to the SES actions your project needs. Do not paste a root-account key.

## Connect AWS SES

<Steps>
  <Step title="Open the connection form">
    In your project, open **Integrations → Add Integration**, find **AWS SES**, and select **Connect**.
  </Step>

  <Step title="Enter the AWS details">
    Enter the access key, secret key, from address, and region. The region must match the region where AWS SES knows the identity.
  </Step>

  <Step title="Save and verify">
    Save the form and wait for the connection to finish. The integration row should show **Connected**.
  </Step>
</Steps>

<Check>
  Use the connection with the AWS SES tool or an email automation and send a test to an address you control. AWS SES must allow `ses:SendEmail` for the verified identity.
</Check>

## Use the connection

* Enable [Send with AWS SES](/docs/build/workflows/tools/send-ses) on the workflow node and select this connection.
* Select the connection when an automation asks for an email destination.
* Use it for campaign or nudge email when the dashboard offers an email integration selector.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The connection saves but email fails">
    Confirm that the region, from address, and SES identity all match. Check that the IAM user can call `ses:SendEmail` and that AWS has not placed the account in the SES sandbox.
  </Accordion>

  <Accordion title="Recipients do not see the message">
    Check the recipient address, spam folder, and SES sending statistics. If the account is in the sandbox, AWS may allow mail only to verified recipients.
  </Accordion>

  <Accordion title="I changed the AWS secret key">
    Edit or reconnect the AWS SES integration with the new credentials. Existing workflows use the saved connection until you update it.
  </Accordion>
</AccordionGroup>