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


Google Cloud Pub\Sub
⚙

RD Station


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

RD Station
Trigger on Webhook
⚙

Google Cloud Pub\Sub
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Google Cloud Pub\Sub, RD Station, 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 RD Station integration works as expected. Depending on your setup, data should flow between Google Cloud Pub\Sub and RD Station (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 RD Station
Google Cloud Pub/Sub + RD Station + Google Sheets: When a message is received in Google Cloud Pub/Sub, extract the lead's information and update their contact details in RD Station. Then, log this activity by adding a new row in Google Sheets, recording the update.
RD Station + Google Cloud Pub/Sub + Slack: When a new lead converts in RD Station, a message is published to a Google Cloud Pub/Sub topic. This triggers a notification to be sent to a designated Slack channel, alerting the sales team about the new conversion.
Google Cloud Pub\Sub and RD Station integration alternatives

About Google Cloud Pub\Sub
undefined
Similar apps
Related categories

About RD Station
Use RD Station in Latenode to automate marketing tasks. Update leads, trigger personalized emails, and track campaign performance, all inside automated workflows. Integrate RD Station data with other apps, enrich with AI, and build custom logic without code. Scale your marketing automation affordably and visually.
Similar apps
Related categories
See how Latenode works
FAQ Google Cloud Pub\Sub and RD Station
How can I connect my Google Cloud Pub\Sub account to RD Station using Latenode?
To connect your Google Cloud Pub\Sub account to RD Station 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 RD Station accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger RD Station actions from Pub/Sub messages?
Yes, you can! Latenode enables this, automating lead nurturing. React instantly to Pub/Sub events, updating RD Station for targeted marketing.
What types of tasks can I perform by integrating Google Cloud Pub\Sub with RD Station?
Integrating Google Cloud Pub\Sub with RD Station allows you to perform various tasks, including:
- Automatically creating or updating leads in RD Station from Pub/Sub messages.
- Triggering email marketing campaigns based on real-time data from Pub/Sub.
- Segmenting contacts in RD Station based on Pub/Sub event attributes.
- Sending personalized RD Station messages based on Pub/Sub triggers.
- Updating RD Station custom fields with data streamed via Pub/Sub.
How does Latenode handle Pub/Sub message volume?
Latenode scales to handle high Pub/Sub message volumes. Use our no-code tools and robust infrastructure for seamless processing.
Are there any limitations to the Google Cloud Pub\Sub and RD Station integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large Pub/Sub message payloads may impact workflow execution time.
- RD Station API rate limits can affect the speed of data updates.
- Complex data transformations may require custom JavaScript code.