Google BigQuery and Pinecone Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Google BigQuery and Pinecone to automate database workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Google BigQuery and Pinecone

Detailed info you need to know about Google BigQuery and Pinecone integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Google BigQuery

    • Database
    • 1 trigger
    • 19 searches
    • 29 actions

    Query and manage Google BigQuery datasets, tables, jobs and routines. Run SQL and stream rows.[5]

  • Pinecone

    • Database
    • 37 searches
    • 40 actions

    Vector database and assistant platform for AI search.[6]

How to connect Google BigQuery to Pinecone

Set up your Google BigQuery and Pinecone integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Google BigQuery and Pinecone work in WEXTL?

WEXTL exposes actions and triggers for Google BigQuery and Pinecone that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Google BigQuery triggersPinecone actions

Google BigQuery modules

  • Cancel a Job Stops a BigQuery job that is still running, found by its Job ID in a project. Use Location when the job is in a single region or outside the us and eu multi-regions. Output includes the job Status and Statistics.
  • Create a Dataset Creates a dataset named by Dataset ID. Use Location to choose where its data lives and Default Table Expiration Ms to set an expiry for new tables.
  • Create a Job Kicks off a BigQuery job of any kind (query, load, copy or extract) from a Configuration without waiting for it to finish. Follow the new job with Get a Job or Watch Jobs.
  • Create a Routine Adds a stored function or procedure to a dataset, defined by a Routine ID and Routine Type. Use Definition Body for its code and Arguments to declare its inputs.
  • Create a Row Access Policy Restricts which rows of a table certain people can read. Use Filter Predicate for the condition rows must meet and Grantees for who may see them, under a new Policy ID.
  • Create a Table Registers a table under a Table ID inside a dataset. Use Schema to define its columns, View to base it on a query, or Time Partitioning and Clustering to organise how rows are stored.
  • Delete a Dataset Deletes a dataset from your project. Turn on Delete Contents to remove the tables inside it too, otherwise a dataset that still has tables cannot be deleted.
  • Delete a Job Deletes one BigQuery job by its Job ID. Use Location to name the region the job ran in.
  • Delete a Model Removes a BigQuery ML model from a dataset by Model ID.
  • Delete a Routine Removes a user-defined function or procedure using its Routine ID.
  • Delete a Row Access Policy Lifts a row-level restriction on a table by deleting one policy.
  • Delete a Table Deletes the table identified by Table ID.
  • Delete Row Access Policies in Batch Clears several row access policies from one table in a single call. Use Policy IDs to name them all, and Force to delete a policy even when it is the last one on the table.
  • Edit a Dataset Updates the Description, Labels and Default Partition Expiration Ms of a dataset. Use Access to adjust who can reach it.
  • Edit a Model Updates the Description, Friendly Name or Labels of a BigQuery ML model.
  • Edit a Table Applies a partial change to a table, such as a new Friendly Name, Description, Schema or Labels. Use View to change the query of a saved view.
  • Execute a Query Runs a SQL statement and waits for the answer. Turn on Dry Run to validate it without running it, set Use Legacy SQL for old syntax, and pass Query Parameters for parameterised SQL.
  • Get a Dataset Shows the settings of one dataset by Dataset ID, including its Access list and default expiry values.
  • Get a Job Looks up one job by Job ID to see its Configuration, Status and Statistics. Add Location when the job ran in a specific region.
  • Get a Model Opens a BigQuery ML model by Model ID to read its Description, Encryptionconfiguration and the trial it chose as best.
  • Get a Routine Reads one stored function or procedure by Routine ID, including its Definitionbody, Arguments and Determinismlevel.
  • Get a Routine IAM Policy Shows who holds which roles on a routine, with an Etag and Version. Use Options to request a specific policy version.
  • Get a Row Access Policy Fetches the policy behind a Policy ID, showing the Filterpredicate and Grantees it applies.
  • Get a Row Access Policy IAM Policy Reads the IAM bindings of a row access policy, with Auditconfigs and an Etag.
  • Get a Table Returns the Schema, Clustering and Creationtime of a table via its Table ID.
  • Get a Table IAM Policy Lists the roles granted on a table, with Auditconfigs. Use Options to read a specific policy Version.
  • Get Query Results Fetches the answer of a query that already ran, using its Job ID. Output includes Rows, Schema and Cachehit, plus a Pagetoken for further pages.
  • Get the Service Account Finds the service account BigQuery uses for a project, returned as its Email.
  • Insert Rows Streams new rows into a table from Rows in one call. Turn on Skip Invalid Rows to keep going past bad ones. Output includes any Inserterrors.
  • List Datasets Lists the datasets in a project. Use Filter to match labels, All to include hidden datasets, and Limit to cut the result short.
  • List Jobs Pages through BigQuery jobs, one item per job. Narrow them with State Filter, Min Creation Time, Max Creation Time or Parent Job ID, and include jobs owned by other people through All Users.
  • List Models Lists every BigQuery ML model inside a dataset, each as a separate item with its Creationtime and Description. Use Limit to read only a few of them.
  • List Projects Finds the Google Cloud projects your credential can open, each with its ID, Friendly Name and Numeric ID.
  • List Routines Lists the functions and procedures stored in a dataset, one item each. Use Filter with routineType to show only one kind, and Read Mask to limit which fields are included.
  • List Row Access Policies Shows every row access policy attached to a table as separate items with Filterpredicate and Grantees. Use Limit to receive fewer policies.
  • List Table Data Reads rows straight from a table without running a query. Use Selected Fields to return only some columns and Limit to take a smaller slice. Output has the row values under F.
  • List Tables Finds the tables and views in a dataset, giving the Schema and Creationtime of each. Use Limit to stop after the first few.
  • Make an API Call Makes an authorized free-form request to the Google BigQuery REST API with your saved credential.
  • Set a Routine IAM Policy Replaces the access policy of a routine from Policy. Add an Update Mask to limit which parts are written.
  • Set a Table IAM Policy Writes a new access policy onto a table from Policy. Narrow the change with Update Mask.
  • Test IAM Permissions on a Routine Checks which of the listed Permissions the current user holds on a routine. The granted ones are echoed back.
  • Test IAM Permissions on a Row Access Policy Tests a list of Permissions against one row access policy. The ones the caller actually holds are returned.
  • Test IAM Permissions on a Table Asks BigQuery which of the named Permissions apply to the caller on a table.
  • Undelete a Dataset Brings back a dataset that was deleted recently. Set Deletion Time to pick a particular deleted version, otherwise the latest one is restored.
  • Update a Dataset Overwrites a dataset with a fresh Friendly Name, Description, Location and Labels. Edit a Dataset covers more settings, including Access.
  • Update a Routine Changes a stored routine by its Routine ID. Use Definition Body, Language and Arguments to change its code and inputs, and Return Type to change what it returns.
  • Update a Row Access Policy Rewrites a row access policy with a new Filter Predicate and Grantees.
  • Update a Table Replaces a table definition: Friendly Name, Description, Schema, View and Labels. Use Edit a Table for a partial change.
  • Watch Jobs Checks a project on your schedule and starts the workflow once for each newly created BigQuery job. Use Limit to read fewer jobs on every poll.

Pinecone modules

  • Cancel a Bulk Import Stops a bulk import that is still running into an index.
  • Cancel a Conversion Job Stops a running index conversion job.
  • Chat with an Assistant Asks an assistant a question and gets an answer built from its files, with Citations. Send one Message or a whole Messages conversation, and choose the Model and Temperature.
  • Convert an Index Starts a conversion of a pod index into a new index called New Index Name, with the schema from Fields. Use On Error to choose what happens to records that cannot convert.
  • Create a Backup Takes a backup of an index and labels it with an optional Name and Description.
  • Create a Backup Schedule Sets up automatic backups of an index under Name, repeating at a Frequency and keeping each backup for Keep For Days.
  • Create a Bulk Import Loads records from a Storage URI into an index in the background, billed per record. Use Integration ID for a private bucket and On Error for failed records.
  • Create a Namespace Makes a namespace inside an index under Name. A Schema can list which fields are filterable.
  • Create a Namespace Alias Adds an alias called Alias Name that points to a Target Namespace, so callers can use one stable name.
  • Create a Vector Index Builds an index of a chosen Vector Type in a Cloud and Region, with a Dimension and similarity Metric. Turn on Deletion Protection and add Tags if wanted.
  • Create an Assistant Sets up an assistant under a Name, with optional Instructions, Region and Metadata.
  • Create an Index Makes a serverless index in a Cloud and Region from the Fields of its schema. Turn on Deletion Protection to block removal and add Tags to label it.
  • Create an Index from a Backup Restores a backup into a fresh index named New Index Name. Follow the restore with the Restore Job ID that is returned.
  • Delete a Backup Removes a stored backup of an index.
  • Delete a Backup Schedule Deletes a recurring backup schedule of an index.
  • Delete a Namespace Deletes a namespace together with the data inside it.
  • Delete a Namespace Alias Removes an alias that pointed at a namespace.
  • Delete All Documents Clears out one namespace by deleting all of its documents once Confirm is turned on.
  • Delete All Vectors in a Namespace Empties one namespace of its vectors after you turn on Confirm.
  • Delete an Assistant Removes an assistant. This cannot be undone.
  • Delete an Assistant File Removes one uploaded file of an assistant.
  • Delete an Index Deletes an index. This cannot be undone, and it fails while deletion protection is on.
  • Delete Documents Removes documents from a namespace, either the Document IDs given or those matching a Filter.
  • Delete Vectors Removes a batch of vectors from an index by their Vector IDs.
  • Delete Vectors by Metadata Deletes the vectors whose metadata satisfies a Filter.
  • Fetch Documents Pulls documents from a namespace, optionally for given Document IDs or a Filter, returning only the Include Fields requested.
  • Fetch Vectors Retrieves vectors by Vector IDs, returning their Values and Metadata.
  • Fetch Vectors by Metadata Shows the vectors whose metadata matches a Filter, with their Values and Metadata.
  • Generate Embeddings Turns Texts into vectors with an embedding Model. Use Input Type and Truncate to tune the call and read Total Tokens for the usage.
  • Get a Backup Fetches a backup with its Name, Description and Source Index Name.
  • Get a Backup Schedule Checks a recurring backup schedule and shows its Name and Schedule Type.
  • Get a Bulk Import Checks one bulk import and reports its Status and Percent Complete.
  • Get a Conversion Job Checks an index conversion and shows its Source Index Name and Target Index Name.
  • Get a Model Retrieves one inference model with its Short Description, Type and Default Dimension.
  • Get a Namespace Looks up one namespace and reports its Record Count and Size Bytes.
  • Get a Namespace Alias Looks up an alias and shows the Target Namespace it points to.
  • Get a Restore Job Checks a restore job, showing its Status and Target Index Name.
  • Get an Assistant Shows one assistant with its Name, Instructions, Status and Host.
  • Get an Assistant File Looks up one assistant file, returning its Name and Size. Turn on Include Download URL to also get a download link.
  • Get an Assistant Operation Checks an assistant operation such as a file upload, reporting its Operation Type and Status.
  • Get an Index Pulls an index with its Host, Status, Deployment and Schema.
  • Get Index Stats Counts the vectors of an index, giving the Total Vector Count, Dimension and Index Fullness. A Filter counts only matching vectors.
  • List Assistant Files Shows the files uploaded to an assistant, with a Name and Size for each. Use Metadata Filter to keep matching files.
  • List Assistant Operations Gathers the operations run on an assistant, such as uploads, optionally for one Operation Type or Status.
  • List Assistants Shows your assistants with their Name, Status and Host.
  • List Backup Schedule History Gathers the backups that a schedule produced, each with its Backup ID and Name.
  • List Backup Schedules Reads the recurring backup plans of an index, each with a Name and Schedule Type.
  • List Backups Pulls the backups stored for an index, naming each by Name and Description. Turn on Include Deleted to see removed ones.
  • List Bulk Imports Collects the bulk imports run against an index, showing Status and Percent Complete.
  • List Conversion Jobs Returns index conversion jobs with their Source Index Name and Target Index Name.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Google BigQuery and Pinecone integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Google BigQuery and Pinecone on WEXTL®

Claim your 3-day trial to build Google BigQuery with Pinecone integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Google BigQuery and Pinecone.

How do I connect Google BigQuery and Pinecone?

Connect your Google BigQuery and Pinecone accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Google BigQuery and Pinecone?

Example: when the "Watch Jobs" trigger in Google BigQuery fires, WEXTL can "Cancel a Bulk Import" in Pinecone. Google BigQuery has 1 trigger (including Watch Jobs). Pinecone has 77 actions (including Cancel a Bulk Import, Cancel a Conversion Job, and Chat with an Assistant). Add filters and transforms between steps when you need them.[1]

Can Google BigQuery trigger actions in Pinecone, and Pinecone in Google BigQuery?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Google BigQuery and Pinecone?

No. Google BigQuery-to-Pinecone automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Google BigQuery integrate with Pinecone in real time?

Yes. Trigger-based automations start the moment Google BigQuery (or Pinecone) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Google BigQuery + Pinecone integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Google BigQuery with Pinecone?

You can build your Google BigQuery + Pinecone automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Google BigQuery and Pinecone integration.

  1. Google BigQuery and Pinecone integration source code, module specs and credentials implementation.
  2. Our Google BigQuery and Pinecone integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Google BigQuery and Pinecone, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Google BigQuery integration information
  6. Pinecone integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Google BigQuery and Pinecone integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Google BigQuery and Pinecone, or get started