How to connect Amazon SES and Zendesk Sell
Create a New Scenario to Connect Amazon SES and Zendesk Sell
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 Zendesk Sell will be your first step. To do this, click "Choose an app," find Amazon SES or Zendesk Sell, 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 Zendesk Sell Node
Next, click the plus (+) icon on the Amazon SES node, select Zendesk Sell from the list of available apps, and choose the action you need from the list of nodes within Zendesk Sell.


Amazon SES
⚙
Zendesk Sell

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

Amazon SES
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Amazon SES, Zendesk Sell, 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 Zendesk Sell integration works as expected. Depending on your setup, data should flow between Amazon SES and Zendesk Sell (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 Zendesk Sell
Amazon SES + Zendesk Sell + Slack: When an email fails to send via Amazon SES, a lead is created in Zendesk Sell to follow up with the potentially missed opportunity. A notification is then sent to a Slack channel to alert the sales team.
Zendesk Sell + Amazon SES + Google Sheets: When a new deal is created in Zendesk Sell, a welcome email is sent to the lead via Amazon SES. The lead's information is then logged into a Google Sheet for tracking and analysis.
Amazon SES and Zendesk Sell 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 Zendesk Sell
Sync Zendesk Sell with Latenode to automate sales tasks. Create visual workflows to update deals, manage contacts, and trigger actions based on sales activity. Enhance your CRM data with enrichment tools, route leads intelligently, and automate follow-ups — all in a scalable, low-code environment.
Related categories
See how Latenode works
FAQ Amazon SES and Zendesk Sell
How can I connect my Amazon SES account to Zendesk Sell using Latenode?
To connect your Amazon SES account to Zendesk Sell 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 Zendesk Sell accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically send personalized follow-up emails after deal updates?
Yes, you can! Latenode's visual editor makes it simple to trigger personalized Amazon SES emails when a Zendesk Sell deal stage changes, improving engagement and closing rates.
What types of tasks can I perform by integrating Amazon SES with Zendesk Sell?
Integrating Amazon SES with Zendesk Sell allows you to perform various tasks, including:
- Sending automated welcome emails to new Zendesk Sell contacts.
- Creating email sequences triggered by deal stage changes.
- Notifying sales reps of important deal updates via email.
- Sending customer satisfaction surveys after deal completion.
- Automatically adding new Zendesk Sell contacts to email lists.
Can I use custom JavaScript with Amazon SES in Latenode?
Yes! Latenode supports custom JavaScript, letting you manipulate data or add complex logic to your Amazon SES workflows.
Are there any limitations to the Amazon SES and Zendesk Sell integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Amazon SES sending limits apply; monitor your SES quotas.
- Complex data transformations might require JavaScript knowledge.
- Zendesk Sell API rate limits can impact high-volume workflows.