How to connect Amazon SES and Launch27
Create a New Scenario to Connect Amazon SES and Launch27
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Amazon SES, triggered by another scenario, or executed manually (for testing purposes). In most cases, Amazon SES or Launch27 will be your first step. To do this, click "Choose an app," find Amazon SES or Launch27, and select the appropriate trigger to start the scenario.

Add the Amazon SES Node
Select the Amazon SES node from the app selection panel on the right.


Amazon SES

Configure the Amazon SES
Click on the Amazon SES node to configure it. You can modify the Amazon SES URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Launch27 Node
Next, click the plus (+) icon on the Amazon SES node, select Launch27 from the list of available apps, and choose the action you need from the list of nodes within Launch27.


Amazon SES
⚙
Launch27

Authenticate Launch27
Now, click the Launch27 node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Launch27 settings. Authentication allows you to use Launch27 through Latenode.
Configure the Amazon SES and Launch27 Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Amazon SES and Launch27 Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Launch27
Trigger on Webhook
⚙

Amazon SES
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Amazon SES, Launch27, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Amazon SES and Launch27 integration works as expected. Depending on your setup, data should flow between Amazon SES and Launch27 (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Amazon SES and Launch27
Launch27 + Amazon SES + Google Sheets: When a new booking is created in Launch27, a confirmation email is sent to the customer via Amazon SES. The booking details are then logged in a Google Sheet for tracking and analysis.
Amazon SES + Launch27 + Slack: When a verified email bounces in Amazon SES, the flow finds the customer's booking information in Launch27 using email. Slack then sends a direct message to the cleaning business owner, alerting them about the bounce and providing the booking details.
Amazon SES and Launch27 integration alternatives

About Amazon SES
Automate email sending with Amazon SES in Latenode. Send transactional emails, notifications, and marketing campaigns within your automated workflows. Use Latenode's visual editor to connect SES to other apps, add conditional logic, and handle bounces – simplifying email management and scaling your communication flows without coding.
Similar apps
Related categories
About Launch27
Automate Launch27 booking & service management within Latenode. Create flows that sync bookings with calendars, trigger follow-ups based on booking status, or generate reports. Use Latenode's visual builder & JS node for custom logic, connecting Launch27 data to other apps without code limits. Scale operations with affordable, usage-based pricing.
Related categories
See how Latenode works
FAQ Amazon SES and Launch27
How can I connect my Amazon SES account to Launch27 using Latenode?
To connect your Amazon SES account to Launch27 on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Amazon SES and click on "Connect".
- Authenticate your Amazon SES and Launch27 accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate customer feedback follow-ups after booking?
Yes, you can! Latenode allows you to automatically send tailored feedback emails via Amazon SES after a Launch27 booking, improving customer engagement with personalized, automated workflows.
What types of tasks can I perform by integrating Amazon SES with Launch27?
Integrating Amazon SES with Launch27 allows you to perform various tasks, including:
- Send booking confirmations via personalized emails using Amazon SES.
- Automate reminder emails for upcoming appointments.
- Send promotional offers to new customers.
- Trigger customer satisfaction surveys post-service.
- Manage bounced email addresses and update customer records.
How secure is Amazon SES integration on Latenode?
Latenode uses secure authentication methods and encryption to protect your Amazon SES credentials, ensuring secure data transfer and compliance.
Are there any limitations to the Amazon SES and Launch27 integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Attachments in Amazon SES emails are limited by Amazon SES's file size restrictions.
- Complex conditional logic may require JavaScript code within Latenode.
- Rate limits apply based on your Amazon SES sending limits and Launch27 API usage.