ActionAWS SESUpdated May 2026

What sender identities are verified in AWS SES?

Short answer: Drop the "AWS SES → List Verified Identities" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 AWS SES actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page Size page_size	number	Optional	Max identities to return (1-1000).

Sample request

{
  "page_size": "{{trigger.page_size}}"
}

Returns

{
  "EmailIdentities": [
    {
      "IdentityName": "no-reply@acme.com",
      "IdentityType": "EMAIL_ADDRESS",
      "SendingEnabled": true,
      "VerificationStatus": "SUCCESS"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Verified Identities.

Any of these apps can fire this action as part of a workflow.

Google Sheets → AWS SES

2 Google Sheets triggers

HubSpot → AWS SES

18 HubSpot triggers

FAQ

Questions about List Verified Identities.

What does the List Verified Identities action do in AWS SES?

Returns every verified sender email/domain in the connected SES region. SES blocks sends from unverified identities, so this is the pre-flight check before Send Email — confirm the from-address is verified or your sends will silently fail.

What inputs does List Verified Identities require?

List Verified Identities has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if AWS SES returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Verified Identities support batch operations?

Yes. Run List Verified Identities inside a Loop node to process arrays. Tiny Command handles AWS SES's rate limits automatically so you don't have to throttle manually.

More actions