Google BigQuery and Ninox Integration

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

Keep Google BigQuery and Ninox matched by integrating their events and actions. When database events happen in Google BigQuery, update the Ninox automatically - without any line of code in visual workflow builder.

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

Learn about Google BigQuery and Ninox

Detailed info you need to know about Google BigQuery and Ninox 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]

  • Ninox

    • Database
    • 2 triggers
    • 14 searches
    • 9 actions

    Low-code database and workflow platform.[6]

How to connect Google BigQuery to Ninox

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

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

WEXTL exposes actions and triggers for Google BigQuery and Ninox 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 triggersNinox 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.

Ninox modules

  • Create a Record Inserts a row in a Ninox table, with one input per field of the chosen Table. Use Extra Fields for references or multiple choice columns. Returns the new ID and Sequence.
  • Create or Update a Record With an ID Writes a record to a Ninox table at one numeric Record ID. A free ID creates the record and an existing ID updates it. Extra Fields cover columns the form lacks.
  • Delete a File Deletes one attachment from a record. Turn on Confirm to acknowledge that the file cannot be recovered afterwards.
  • Delete a Record Deletes a record in a table. Switch Confirm on to confirm the call, because a deleted record cannot be undone.
  • Delete Records Removes many records from a table in one request. Use Confirm to approve it, as the deletion is permanent.
  • Download a File Fetches the content of an attachment on a record. Output holds the File, its File Name and Content Type.
  • Find a Record Looks in a table for the first record whose fields equal every value of Filters. Use Choice Style to set how choice fields are returned.
  • Get a Database Retrieves one Ninox database with its Settings, Schema and Version. Add the Schema Password for a password protected schema, otherwise Ninox answers with an encrypted schema.
  • Get a Record Shows a single record of a table with its fields, Created At and Modified At. Use Choice Style to switch how choice fields are returned.
  • Get a Table Pulls the definition of one table in a database, giving its ID, Name and Fields.
  • Get a Team Finds one Ninox team and returns its ID and Name.
  • List Database Changes Lists what changed anywhere in a database after a sequence number, taken from the seq of an earlier answer or of a record. The output holds Updates, Removes and the next Sequence.
  • List Databases Shows the databases of a team, each with its ID and Name. Use Limit to set the maximum number of databases returned.
  • List Record Files Shows the files attached to one record, each with its Name, Content Type, Size and Modified Date. Use Limit to cap how many files are returned.
  • List Table Changes Lists the changes in one table made after a sequence number. Use Since Sequence to set where to start. Each result gives the Updates, the Removes and a fresh Sequence.
  • List Tables Enumerates the tables inside a database with their ID, Name and Fields. Use Limit to decide how many tables come out.
  • List Teams Retrieves Ninox teams, each with an ID and Name. Use Limit to bound the number of teams.
  • Make an API Call Sends a free-form request to the Ninox REST API, signed with your saved credential.
  • Run a Query Executes a read-only Ninox script against a database and returns its Result. Use Query to write the script, such as a select on one table.
  • Run a Script Runs a Ninox script that may create, change or delete data and returns its Result. Turn on Confirm to run it, because the changes cannot be undone. On a private cloud the key needs the admin role.
  • Search Records Returns records from a table, each as its own result. Narrow them with Filters or a Script Filter, sort with Order By, keep only those above an ID using Only After Record ID, and set Limit for the count.
  • Update a Record Changes fields on a record that already exists. Use Clear Fields to empty fields, which wins over values filled in on the form, and Extra Fields for columns that form does not offer.
  • Upload a File Adds a file to the attachments of a record. Map File from an earlier step such as a download or an email attachment, and use File Name to store it under another name.
  • Watch New Records Polls a table on your schedule and fires for each record created since the last check. Use Limit to set how many of the newest records the first check takes.
  • Watch Updated Records Checks a table on a schedule and fires for every record that was created or modified since the previous check. Use Limit to cap the newest records returned on the first check.

Explore alternative integrations

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

Automate Google BigQuery and Ninox on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Google BigQuery and Ninox.

How do I connect Google BigQuery and Ninox?

Connect your Google BigQuery and Ninox 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 Ninox?

Example: when the "Watch Jobs" trigger in Google BigQuery fires, WEXTL can "Create a Record" in Ninox. Google BigQuery has 1 trigger (including Watch Jobs). Ninox has 23 actions (including Create a Record, Create or Update a Record With an ID, and Delete a File). Add filters and transforms between steps when you need them.[1]

Can Google BigQuery trigger actions in Ninox, and Ninox 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 Ninox?

No. Google BigQuery-to-Ninox 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 Ninox in real time?

Yes. Trigger-based automations start the moment Google BigQuery (or Ninox) 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 + Ninox 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 Ninox?

You can build your Google BigQuery + Ninox 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 Ninox integration.

  1. Google BigQuery and Ninox integration source code, module specs and credentials implementation.
  2. Our Google BigQuery and Ninox integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Google BigQuery and Ninox, 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. Ninox 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 Ninox integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Google BigQuery and Ninox, or get started