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


Google Cloud Pub\Sub
⚙
Recruitee

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

Google Cloud Pub\Sub
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google Cloud Pub\Sub, Recruitee, 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 Recruitee integration works as expected. Depending on your setup, data should flow between Google Cloud Pub\Sub and Recruitee (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 Recruitee
Google Cloud Pub/Sub + Recruitee + Slack: When a new message arrives in a specific Google Cloud Pub/Sub topic, indicating a new candidate application, the automation finds the candidate in Recruitee and sends a notification to the HR team in a designated Slack channel.
Recruitee + Google Cloud Pub/Sub + Google Sheets: When a new candidate is added in Recruitee, a message is sent via Google Cloud Pub/Sub. This message triggers the automation to add a new row in a Google Sheet with the candidate's data.
Google Cloud Pub\Sub and Recruitee integration alternatives

About Google Cloud Pub\Sub
undefined
Similar apps
Related categories
About Recruitee
Automate your hiring process with Recruitee in Latenode. Trigger workflows on new applications to screen candidates, send automated messages, and update other systems. Connect Recruitee to HR tools for seamless data flow and custom talent pipelines. Simplify recruiting tasks using Latenode's visual editor and scaling options.
Related categories
See how Latenode works
FAQ Google Cloud Pub\Sub and Recruitee
How can I connect my Google Cloud Pub\Sub account to Recruitee using Latenode?
To connect your Google Cloud Pub\Sub account to Recruitee 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 Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger Recruitee actions from Google Cloud Pub\Sub messages?
Yes, you can! Latenode lets you trigger Recruitee actions from Pub/Sub. Automatically create new candidate profiles using incoming message data, streamlining your recruiting workflows and saving time.
What types of tasks can I perform by integrating Google Cloud Pub\Sub with Recruitee?
Integrating Google Cloud Pub\Sub with Recruitee allows you to perform various tasks, including:
- Create new Recruitee candidates from Google Cloud Pub\Sub message data.
- Update candidate information based on Pub/Sub event triggers.
- Send custom notifications via Pub/Sub for new Recruitee applications.
- Archive candidate profiles based on Pub/Sub data analysis.
- Log recruitment activity using Pub/Sub messages for auditing.
How do I handle errors from Pub/Sub in my Latenode workflows?
Latenode provides robust error handling. Use "Try/Catch" blocks and detailed logging to manage Pub/Sub errors and ensure workflow stability.
Are there any limitations to the Google Cloud Pub\Sub and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require custom JavaScript code.
- Large message volumes from Pub/Sub can impact workflow execution time.
- Real-time synchronization depends on the responsiveness of both APIs.