CONNECT APP
Build with Amazon SES
Communication
- API key
MCP
Give your agent Amazon SES tools
Every Amazon SES action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Amazon SES account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "amazon_ses",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Email Template:
const result = await mcp.callTool({
name: "amazon_ses-create-email-template",
arguments: {
region: "AWS Region",
TemplateName: "Template Name",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "amazon_ses",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Email Template:
result = await session.call_tool("amazon_ses-create-email-template", {
"region": "AWS Region",
"TemplateName": "Template Name",
})SDK
Run Amazon SES actions from your backend
Connect a user's Amazon SES account once, then run Create Email Template on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "amazon_ses-create-email-template",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
amazon_ses: { authProvisionId: "apn_xxxxxxx" },
region: "AWS Region",
TemplateName: "Template Name",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="amazon_ses-create-email-template",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"amazon_ses": {"authProvisionId": "apn_xxxxxxx"},
"region": "AWS Region",
"TemplateName": "Template Name",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "amazon_ses-create-email-template",
"configured_props": {
"amazon_ses": { "authProvisionId": "apn_xxxxxxx" },
"region": "AWS Region",
"TemplateName": "Template Name"
}
}'TOOLS
Amazon SES actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Email Template
actionCreate a HTML or a plain text email template. See the docsWritev0.0.3 -
Get Email Template
actionGet an email template. See the docsRead-onlyv0.0.3 -
Send Email
actionSend an email using Amazon SES. Supports simple email messaging. See the docsWritev0.9.7 -
Send Templated Email
actionSend an email replacing the template tags with values using Amazon SES. See the docsWritev0.0.3 -
Update Email Template
actionUpdate an email template. See the docsWritev0.0.3
EVENTS
Amazon SES triggers
Event sources your backend can deploy for users and receive through a webhook.
No Amazon SES triggers are available yet.
MULTI-APP
Use Amazon SES with other popular apps
Most products don't stop at one integration. Pair Amazon SES with the other apps your users rely on, and ship use cases that span both.
- App slug
- amazon_ses
- Authentication
- API key
- Categories
- Communication
- Actions
- 5
- Triggers
- 0
- API proxy
- Not available