How to connect 123FormBuilder and Amazon SES
Create a New Scenario to Connect 123FormBuilder and Amazon SES
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 123FormBuilder, triggered by another scenario, or executed manually (for testing purposes). In most cases, 123FormBuilder or Amazon SES will be your first step. To do this, click "Choose an app," find 123FormBuilder or Amazon SES, and select the appropriate trigger to start the scenario.

Add the 123FormBuilder Node
Select the 123FormBuilder node from the app selection panel on the right.

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

123FormBuilder
β

Amazon SES

Authenticate Amazon SES
Now, click the Amazon SES node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Amazon SES settings. Authentication allows you to use Amazon SES through Latenode.
Configure the 123FormBuilder and Amazon SES 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 123FormBuilder and Amazon SES 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
β

Amazon SES
Trigger on Webhook
β
123FormBuilder
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring 123FormBuilder, Amazon SES, 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 123FormBuilder and Amazon SES integration works as expected. Depending on your setup, data should flow between 123FormBuilder and Amazon SES (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect 123FormBuilder and Amazon SES
123FormBuilder + Amazon SES + Google Sheets: When a new submission is received in 123FormBuilder, send a confirmation email via Amazon SES and log the submission data in a Google Sheet.
Amazon SES + 123FormBuilder + Slack: When a new verified identity is added in Amazon SES (simulating a bounce), create a support ticket in 123FormBuilder and notify the team on Slack.
123FormBuilder and Amazon SES integration alternatives
About 123FormBuilder
Streamline data collection by connecting 123FormBuilder to Latenode. Automatically trigger workflows when forms are submitted. Route form data to CRMs, databases, or email marketing tools. Use Latenode to validate entries, calculate scores, and manage follow-ups β automating processes with a no-code, scalable workflow.
Related categories

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
See how Latenode works
FAQ 123FormBuilder and Amazon SES
How can I connect my 123FormBuilder account to Amazon SES using Latenode?
To connect your 123FormBuilder account to Amazon SES on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select 123FormBuilder and click on "Connect".
- Authenticate your 123FormBuilder and Amazon SES accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send personalized emails on form submission?
Yes, you can! Latenode allows you to automate personalized email sending using Amazon SES upon 123FormBuilder submissions. Leverage advanced logic for tailored content delivery and enhanced engagement.
What types of tasks can I perform by integrating 123FormBuilder with Amazon SES?
Integrating 123FormBuilder with Amazon SES allows you to perform various tasks, including:
- Send automated welcome emails to new form submitters.
- Create custom email notifications for specific form entries.
- Automatically add form data to email contact lists.
- Trigger email campaigns based on form responses.
- Send file attachments collected via 123FormBuilder forms.
Can I use JavaScript within the 123FormBuilder + Amazon SES integration?
Yes, Latenode supports custom JavaScript code, enabling you to manipulate data and create complex workflows exceeding standard integration capabilities.
Are there any limitations to the 123FormBuilder and Amazon SES integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Amazon SES sending limits apply based on your Amazon SES account.
- Complex data transformations may require custom JavaScript coding.
- Large file attachments may impact workflow execution time.