ActionAWS SESUpdated September 2026
What sender identities are verified in AWS SES?
Short answer: You can list verified identities in AWS SES by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AWS SES List Verified Identities action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
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 run history shows the failed step with its input and the error message AWS SES returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Verified Identities support batch operations?
Run List Verified Identities inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within AWS SES's rate limits.
More actions