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


Google Cloud Pub\Sub
⚙

Process Street


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

Process Street
Trigger on Webhook
⚙

Google Cloud Pub\Sub
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Google Cloud Pub\Sub, Process Street, 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 Process Street integration works as expected. Depending on your setup, data should flow between Google Cloud Pub\Sub and Process Street (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 Process Street
Google Cloud Pub/Sub + Process Street + Slack: When a new message is received in Google Cloud Pub/Sub, a new workflow run is initiated in Process Street, and a notification is sent to a Slack channel.
Process Street + Google Cloud Pub/Sub + Google Sheets: When a Process Street workflow run is completed, a message is published to Google Cloud Pub/Sub, and relevant data from the workflow run is logged into a Google Sheet.
Google Cloud Pub\Sub and Process Street integration alternatives

About Google Cloud Pub\Sub
undefined
Similar apps
Related categories

About Process Street
Use Process Street in Latenode to run repeatable tasks like onboarding or reports as part of larger workflows. Automatically trigger actions in other apps (CRM, databases) when checklist items are completed, keeping processes moving. This avoids manual updates and ensures audit trails, all at Latenode's execution-based pricing.
Related categories
See how Latenode works
FAQ Google Cloud Pub\Sub and Process Street
How can I connect my Google Cloud Pub\Sub account to Process Street using Latenode?
To connect your Google Cloud Pub\Sub account to Process Street 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 Process Street accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger Process Street checks from Pub\Sub messages?
Yes, you can! Latenode's visual editor simplifies setting up triggers. Automate task assignments and data capture, ensuring consistent processes and streamlined workflows.
What types of tasks can I perform by integrating Google Cloud Pub\Sub with Process Street?
Integrating Google Cloud Pub\Sub with Process Street allows you to perform various tasks, including:
- Automatically creating Process Street checklists from Google Cloud Pub\Sub messages.
- Updating checklist items in Process Street based on Pub\Sub data.
- Triggering notifications in Process Street when a new message arrives in Pub\Sub.
- Populating Process Street variables with data extracted from Pub\Sub payloads.
- Starting or stopping Process Street workflows based on Pub\Sub message content.
What Google Cloud Pub\Sub message attributes are accessible in Latenode?
Latenode provides access to all standard Pub\Sub message attributes, enhancing workflow customization and data handling within your automations.
Are there any limitations to the Google Cloud Pub\Sub and Process Street integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by the Google Cloud Pub\Sub and Process Street APIs may affect high-volume workflows.
- Complex data transformations might require JavaScript code within Latenode.
- Initial setup requires familiarity with Google Cloud Pub\Sub topics and subscriptions.