Amazon SES

Overview

Connect Amazon SES with Flows360

Amazon SES integration for Flows360 workflows.

Use the Amazon SES connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and no declared triggers.

Available actions

• Send Email
• Create Email Template
• Send Templated Email
• Update Email Template
• Create Custom Verification Email Template
• Send Custom Verification Email
• Update Custom Verification Email Template

Available triggers

• No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: Amazon SES
• Package: @activepieces/piece-amazon-ses@0.1.7
• Exact artifact digest: sha256:e30da613194ac5a953ff3de61781dab9c725f798aefe7ff25ef061d6b3d0b267
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Send Email (send_email), Send a customizable email via Amazon SES with verified sender addresses Classification: read.
• Create Email Template (create_email_template), Create a reusable HTML or text email template with variables Classification: read.
• Send Templated Email (send_templated_email), Send personalized emails using pre-created templates Classification: read.
• Update Email Template (update_email_template), Modify an existing email template with new content Classification: read.
• Create Custom Verification Email Template (create_custom_verification_email_template), Create custom email template for identity verification Classification: read.
• Send Custom Verification Email (send_custom_verification_email), Send verification email to add an email address to SES identities Classification: read.
• Update Custom Verification Email Template (update_custom_verification_email_template), Modify an existing custom verification email template Classification: read.

Trigger contracts

• No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Setup

Setup

1. Add the Amazon SES connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• Access Key ID (accessKeyId), required; stored as a sensitive connection value.
• Secret Access Key (secretAccessKey), required; stored as a sensitive connection value.
• Region (region), required.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-amazon-ses@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 7 actions and 0 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Related documentation