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


Cloudinary
⚙

Google Cloud Pub\Sub


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

Google Cloud Pub\Sub
Trigger on Webhook
⚙

Cloudinary
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Cloudinary, Google Cloud Pub\Sub, 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 Google Cloud Pub\Sub integration works as expected. Depending on your setup, data should flow between Cloudinary and Google Cloud Pub\Sub (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 Google Cloud Pub\Sub
Cloudinary + Google Cloud Pub/Sub + Google Cloud Storage: When a new resource is uploaded to Cloudinary, it triggers a Pub/Sub notification. This notification then initiates the storage of the image in Google Cloud Storage.
Google Cloud Pub/Sub + Cloudinary + Slack: A Google Cloud Pub/Sub notification triggers image optimization in Cloudinary. After the image is transformed, a message is sent to a Slack channel notifying users of the completed processing.
Cloudinary and Google Cloud Pub\Sub 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 Google Cloud Pub\Sub
undefined
Similar apps
Related categories
See how Latenode works
FAQ Cloudinary and Google Cloud Pub\Sub
How can I connect my Cloudinary account to Google Cloud Pub/Sub using Latenode?
To connect your Cloudinary account to Google Cloud Pub/Sub 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 Google Cloud Pub/Sub accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger video transcoding upon file upload to Cloudinary using Google Cloud Pub/Sub?
Yes, you can. Latenode allows triggering workflows upon Pub/Sub events. Automatically start Cloudinary transcoding, streamlining media processing.
What types of tasks can I perform by integrating Cloudinary with Google Cloud Pub/Sub?
Integrating Cloudinary with Google Cloud Pub/Sub allows you to perform various tasks, including:
- Distributing processed Cloudinary assets via Pub/Sub topics.
- Triggering image analysis workflows based on Pub/Sub messages.
- Notifying subscribers about new media files uploaded to Cloudinary.
- Creating backups of Cloudinary assets to Google Cloud Storage.
- Dynamically resizing images based on subscriber requests.
Can I use JavaScript code to transform data between Cloudinary and Pub/Sub?
Yes, Latenode allows JavaScript code to reshape data, ensuring seamless integration between Cloudinary and Google Cloud Pub/Sub.
Are there any limitations to the Cloudinary and Google Cloud Pub/Sub integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require advanced JavaScript coding.
- Real-time synchronization depends on the Pub/Sub message delivery guarantees.
- Large file transfers may be subject to Cloudinary's and Google Cloud's bandwidth limits.