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

Add the Google Cloud BigQuery (REST) Node
Select the Google Cloud BigQuery (REST) node from the app selection panel on the right.

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

Google Cloud BigQuery (REST)
⚙
Streamtime
Authenticate Streamtime
Now, click the Streamtime node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Streamtime settings. Authentication allows you to use Streamtime through Latenode.
Configure the Google Cloud BigQuery (REST) and Streamtime 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 BigQuery (REST) and Streamtime 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
⚙
Streamtime
Trigger on Webhook
⚙
Google Cloud BigQuery (REST)
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Google Cloud BigQuery (REST), Streamtime, 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 BigQuery (REST) and Streamtime integration works as expected. Depending on your setup, data should flow between Google Cloud BigQuery (REST) and Streamtime (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 BigQuery (REST) and Streamtime
Streamtime + Google Cloud BigQuery (REST) + Google Sheets: When a job is completed in Streamtime, its data is sent to Google Cloud BigQuery for analysis. The results of the analysis, specifically project hours and calculated costs, are then reported in Google Sheets.
Streamtime + Google Cloud BigQuery (REST) + Slack: When a project is updated in Streamtime, BigQuery analyzes the data to check if the project is over budget. If the project exceeds the budget, a notification is sent to the project manager in Slack.
Google Cloud BigQuery (REST) and Streamtime integration alternatives
About Google Cloud BigQuery (REST)
Automate BigQuery data workflows in Latenode. Query and analyze massive datasets directly within your automation scenarios, bypassing manual SQL. Schedule queries, transform results with JavaScript, and pipe data to other apps. Scale your data processing without complex coding or expensive per-operation fees. Perfect for reporting, analytics, and data warehousing automation.
Similar apps
Related categories
About Streamtime
Streamtime project management inside Latenode: automate tasks like invoice creation based on project status, or sync time entries with accounting. Connect Streamtime to other apps via Latenode's visual editor and AI tools. Customize further with JavaScript for complex workflows. Manage projects and data automatically.
Related categories
See how Latenode works
FAQ Google Cloud BigQuery (REST) and Streamtime
How can I connect my Google Cloud BigQuery (REST) account to Streamtime using Latenode?
To connect your Google Cloud BigQuery (REST) account to Streamtime on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Cloud BigQuery (REST) and click on "Connect".
- Authenticate your Google Cloud BigQuery (REST) and Streamtime accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I analyze project profitability using BigQuery data in Streamtime?
Yes, you can. Latenode lets you pull BigQuery data, transform it with JavaScript or AI, and then push streamlined profitability reports into Streamtime. This gives a clear view of project performance.
What types of tasks can I perform by integrating Google Cloud BigQuery (REST) with Streamtime?
Integrating Google Cloud BigQuery (REST) with Streamtime allows you to perform various tasks, including:
- Automatically updating Streamtime projects based on BigQuery data analysis.
- Creating custom financial reports in Streamtime using BigQuery datasets.
- Triggering Streamtime tasks based on data thresholds met in BigQuery.
- Synchronizing client data between Google Cloud BigQuery (REST) and Streamtime.
- Generating alerts in Streamtime based on anomalies detected in BigQuery data.
HowsecureisGoogleCloudBigQuery(REST)datatransferonLatenode?
Latenode uses secure connections and encryption to protect your data during transfer between Google Cloud BigQuery (REST) and other applications.
Are there any limitations to the Google Cloud BigQuery (REST) and Streamtime integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Initial data synchronization may take time depending on dataset size.
- Complex data transformations might require JavaScript knowledge.
- Streamtime's API rate limits may impact high-volume data updates.