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

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


Cloudinary

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


Cloudinary
⚙

SendPulse


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

SendPulse
Trigger on Webhook
⚙

Cloudinary
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Cloudinary, SendPulse, 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 Cloudinary and SendPulse integration works as expected. Depending on your setup, data should flow between Cloudinary and SendPulse (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Cloudinary and SendPulse
Shopify + Cloudinary + SendPulse: When a new product is added to Shopify, its images are optimized using Cloudinary. SendPulse then sends an email to subscribers, promoting the new product.
SendPulse + Cloudinary + Facebook: When a new subscriber event occurs in SendPulse, related images are fetched from Cloudinary. These images are then used to create a Facebook ad campaign.
Cloudinary and SendPulse integration alternatives

About Cloudinary
Automate image and video optimization with Cloudinary in Latenode. Resize, convert, and deliver media assets based on triggers or data from any app. Streamline content workflows by integrating Cloudinary’s powerful transformations directly into your automated processes, reducing manual work. Scale efficiently and pay only for execution time.
Similar apps
Related categories

About SendPulse
Use SendPulse in Latenode for automated email & SMS marketing. Trigger campaigns based on real-time events, segment contacts dynamically, and personalize messages using data from any app. Automate list cleaning and optimize send times in response to user behavior. Connect SendPulse to any data source for smarter, event-driven communication workflows.
Related categories
See how Latenode works
FAQ Cloudinary and SendPulse
How can I connect my Cloudinary account to SendPulse using Latenode?
To connect your Cloudinary account to SendPulse on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Cloudinary and click on "Connect".
- Authenticate your Cloudinary and SendPulse accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I personalize marketing emails with Cloudinary images?
Yes! Latenode allows dynamic insertion of Cloudinary images into SendPulse emails. Enhance engagement by tailoring visuals based on recipient data using no-code logic and JavaScript.
What types of tasks can I perform by integrating Cloudinary with SendPulse?
Integrating Cloudinary with SendPulse allows you to perform various tasks, including:
- Automatically adding Cloudinary images to SendPulse email templates.
- Triggering SendPulse campaigns based on new image uploads in Cloudinary.
- Updating contact profile pictures in SendPulse from Cloudinary assets.
- Creating personalized image galleries hosted on Cloudinary and emailed via SendPulse.
- Tracking image engagement from SendPulse emails using Cloudinary analytics.
Can I use Cloudinary transformations directly within Latenode flows?
Yes! Latenode supports direct integration with Cloudinary's powerful transformation features, applying them dynamically within your automation workflows for enhanced image delivery.
Are there any limitations to the Cloudinary and SendPulse integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex image transformations may impact workflow execution time.
- Free SendPulse accounts have limitations on the number of emails sent.
- Large Cloudinary asset libraries could require optimized data handling.