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

Add the Google Cloud Pub\Sub Node
Select the Google Cloud Pub\Sub node from the app selection panel on the right.


Google Cloud Pub\Sub

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


Google Cloud Pub\Sub
⚙

Cloudinary


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

Cloudinary
Trigger on Webhook
⚙

Google Cloud Pub\Sub
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Google Cloud Pub\Sub, Cloudinary, 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 Google Cloud Pub\Sub and Cloudinary integration works as expected. Depending on your setup, data should flow between Google Cloud Pub\Sub and Cloudinary (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Cloud Pub\Sub and Cloudinary
Google Cloud Pub/Sub + Cloudinary + Google Cloud Storage: When a new message is received in Google Cloud Pub/Sub, containing information about an image, the image is uploaded to Cloudinary. After upload, the image is archived to Google Cloud Storage.
Cloudinary + Google Cloud Pub/Sub + Slack: When a new resource is uploaded to Cloudinary, a message containing the resource's details is published to a Google Cloud Pub/Sub topic. This triggers a Slack notification, informing users about the new image.
Google Cloud Pub\Sub and Cloudinary integration alternatives

About Google Cloud Pub\Sub
undefined
Similar apps
Related categories

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
See how Latenode works
FAQ Google Cloud Pub\Sub and Cloudinary
How can I connect my Google Cloud Pub\Sub account to Cloudinary using Latenode?
To connect your Google Cloud Pub\Sub account to Cloudinary on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Cloud Pub\Sub and click on "Connect".
- Authenticate your Google Cloud Pub\Sub and Cloudinary accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate image processing upon Pub\Sub message?
Yes, you can! Latenode allows triggering Cloudinary transformations directly from Pub\Sub events. Benefit from automated resizing, watermarking, and optimization, streamlining your media workflow.
What types of tasks can I perform by integrating Google Cloud Pub\Sub with Cloudinary?
Integrating Google Cloud Pub\Sub with Cloudinary allows you to perform various tasks, including:
- Automatically uploading images to Cloudinary upon receiving a Pub\Sub message.
- Triggering image transformations in Cloudinary based on Pub\Sub data.
- Creating image backups in Cloudinary when new messages arrive in Pub\Sub.
- Dynamically updating Cloudinary metadata using information from Pub\Sub.
- Generating image thumbnails and delivering them via Google Cloud Pub\Sub.
How does Latenode handle Pub\Sub message authentication?
Latenode supports secure authentication using Google Cloud service accounts, ensuring safe and reliable Pub\Sub message processing and delivery.
Are there any limitations to the Google Cloud Pub\Sub and Cloudinary integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Maximum message size limitations imposed by Google Cloud Pub\Sub.
- Cloudinary API rate limits may impact high-volume image processing.
- Complex data transformations may require custom JavaScript code.