Connect Google BigQuery to Spike.sh

Both apps 39Google BigQuery 14Spike.sh 25

• Trigger
  New Job Completed

  Triggers when a BigQuery job in the project finishes, whether it succeeded or failed.

• Trigger
  New Row

  Triggers when a new row is added to a table. New rows are detected by a column you name that increases for newer rows, such as a creation time or a sequential ID.

• Trigger
  Query Job Completed (With Row Data)

  Triggers when a SELECT query job in the project finishes successfully, and includes its result rows.

• Trigger
  Updated Row

  Triggers when a row in a table is added or changed, detected by a last-updated timestamp column you name.

• Action
  Create Row

  Creates a new row of data in a table. Note: Does not create a job.

• Action
  Create Rows

  Creates new rows of data in a table (accepts line items). Note: Does not create a job.

• Action
  Delete Rows

  Deletes every row in a table whose match column equals the value you give.

• Action
  Find One Row

  Finds the first row in a table whose column equals the value you give.

• Action
  Get Rows for Job Completed

  Returns the result rows of a finished query job.

• Action
  Import Data

  Imports a JSON, CSV, Avro or Parquet file from Cloud Storage into a table. Waits up to about 40 seconds for the import to finish; larger imports keep running in BigQuery and return state RUNNING.

• Action
  List Datasets

  Returns the datasets in a Google Cloud project.

• Action
  List Tables

  Returns the tables in a BigQuery dataset.

• Action
  Run a Query

  Runs a SQL query against a table in BigQuery.

• Action
  Update Row(s)

  Updates every row in a table whose match column equals the value you give, setting the columns you choose.

• Action
  Acknowledge incident

  Acknowledge one or more Spike.sh incidents by counter id or incident id.

• Action
  Add alert rule

  Create a new alert routing/automation rule with conditions and actions.

• Action
  Add escalation

  Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

• Action
  Add integration

  Create a new integration for a team (source system that sends alerts into Spike).

• Action
  Add on-call

  Create a new on-call schedule for a team.

• Action
  Add service

  Create a new service in a team, with name and description.

• Action
  Create Incident

  Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

• Action
  Delete alert rule

  Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

• Action
  Delete escalation

  Archives (soft-deletes) a Spike escalation policy by its ID.

• Action
  Escalate incident

  Escalates one or more Spike incidents to the next step of their escalation policy.

• Action
  Get escalation

  Get escalation policy details by id.

• Action
  Get incident

  Fetch a single incident by counter id.

• Action
  Get integration

  Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

• Action
  Get service

  Get a Spike service's details, along with its incidents and open-incident count.

• Action
  List alert rules

  Lists all alert rules (enabled and disabled) configured for a Spike team.

• Action
  List escalations

  Lists the escalation policies that belong to a Spike team.

• Action
  List incidents

  Lists the incidents for a Spike.sh team.

• Action
  List on-calls

  Lists the on-call schedules for a team.

• Action
  List services

  Lists the services in a Spike team.

• Action
  List teams

  Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

• Action
  Resolve incident

  Resolve one or more incidents by counter id array.

• Action
  Update alert rule

  Replace an existing Spike alert rule's name, conditions and actions.

• Action
  Update escalation

  Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

• Action
  Update on-call

  Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

• Action
  Update service

  Updates the name and/or description of an existing Spike.sh service.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.