Connect MySQL to Spike.sh

Both apps 35MySQL 10Spike.sh 25

• Trigger
  New or Updated Row

  Triggers when a new row is added or modified.

• Trigger
  New or Updated Row (Custom Query)

  Fires for each new or changed row returned by a SELECT statement you write against the connected MySQL database.

• Trigger
  New Row

  Triggers when you add a new row.

• Trigger
  New Table

  Fires when a new table appears in the connected MySQL database.

• Action
  Add Row

  Adds a new row.

• Action
  Delete Row

  Delete the rows in a table whose chosen column equals a value.

• Action
  Find Row

  Finds a row in a table via a lookup column.

• Action
  Find Rows via Custom Query

  Run an author-written SELECT against the connected MySQL database and return every row it produced. Mirrors PostgreSQL 715ae2ac, SQL Server 8e0bbb5d and Oracle 2c308e4d; MySQL placeholder style is ?.

• Action
  Find Row via Custom Query

  Runs a SELECT statement you write against the connected MySQL database and returns the first row it matches.

• Action
  Update Row

  Updates an existing row.

• 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.