See llms.txt for all machine-readable content.

Google BigQuery and Rootly integration

Save yourself the work of writing custom integrations for Google BigQuery and Rootly and use n8n instead. Build adaptable and scalable Data & Storage, Development, workflows that work with your technology stack. All within a building experience you will love.

How to connect Google BigQuery and Rootly

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Google BigQuery and Rootly integration: Create a new workflow and add the first step

Answer BigQuery questions in Microsoft Teams with Claude 3.5 dual agents

Quick overview Turn Microsoft Teams into a natural language BI tool. This dual-agent Claude workflow intelligently classifies user questions, generates safe BigQuery SQL, executes the query, and returns a plain-English summary alongside a data preview directly to your Teams channel. How it works The workflow listens for new messages in a designated Microsoft Teams channel or chat. It checks a 24-hour static data cache for your BigQuery schema. If the cache is missing or expired, it automatically fetches the latest INFORMATION_SCHEMA metadata. A main Claude 3.5 Sonnet agent classifies the user's intent (analytical, conversational, or unsafe) and identifies the relevant database tables. If the intent is analytical, a specialized Claude SQL sub-agent generates a read-only SELECT query tailored exactly to your schema. The workflow executes the query against BigQuery (safely constrained to a maximum of 100 rows). A final Claude agent translates the raw query results into a concise, plain-English summary. The answer is posted back to Teams as an Adaptive Card, complete with a formatted data preview and the generated SQL code. Non-analytical questions or pipeline errors are intelligently routed to receive standard conversational replies in Teams. Setup CRITICAL SECURITY: Restrict your Google Cloud Service Account IAM roles to BigQuery Data Viewer and BigQuery Job User ONLY. Do not use a highly privileged account. Configure your Microsoft Teams trigger and posting credentials, specifying the target team and channel for the bot to operate in. Configure your Google BigQuery credentials to allow reading metadata and executing queries. Configure your Anthropic credentials for the three Claude LangChain nodes. Update the "Configure Variables" node with your specific GCP Project ID and BigQuery Dataset ID. Requirements A Google Cloud project with BigQuery enabled and existing structured datasets. An Anthropic API key with access to the Claude 3.5 Sonnet model. Microsoft Teams administrator access to authorize the n8n integration. Customization Distributed Environments: If you are running n8n with multiple worker nodes (Queue Mode), you must swap the $getWorkflowStaticData() schema cache logic to read/write from a dedicated Key-Value store (like Redis or Supabase) to ensure state synchronization. UI Layout: Modify the Create Teams Adaptive Card node to add corporate branding, custom colors, or alter the FactSet data preview structure. Additional info This architecture features built-in pipeline protections, including strict 40,000-character payload limits to prevent LLM context window blowouts, and fallback handling for "zero-row" query results to ensure users are never left without a response.

Build your own Google BigQuery and Rootly integration

Create custom Google BigQuery and Rootly workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Google BigQuery supported actions

Supported methods for Rootly

Delete
Get
Head
Options
Patch
Post
Put

To set up Rootly integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Rootly to query the data you need using the API endpoint URLs you provide.

See the example here

Requires additional credentials set up

Use n8n's HTTP Request node with a predefined or generic credential type to make custom API calls.

Google BigQuery and Rootly integration details

Google BigQuery

Google BigQuery

Many businesses use the Google Cloud service BigQuery for data reporting. BigQuery is categorized as an Advanced Data Connector. The amount of data that needs to be processed could be quite large (up to 10,000 columns and tens of millions of rows).

Rootly

Rootly

Rootly is a platform that streamlines incident management by automating manual tasks. Trusted by thousands globally, it simplifies the incident resolution process, ensuring consistency and efficiency for users.

Other integrations with Google BigQuery and Rootly

The SOAR platform you want

Mountains of monotonous tasks make building and monitoring your workflows a chore. Not anymore.

Learn more

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQ about Google BigQuery integrations

Looking to integrate Slack and VirusTotal in your company?

Three colleagues talking around laptops at a shared desk

Trusted by teams building smarter workflows.

Why

Why use n8n to integrate Google BigQuery with Rootly

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship

Man in a brown jacket working at his desk by a window