Connect Syncro to Spike.sh

Both apps 40Syncro 15Spike.sh 25

• Trigger
  New Customer

  Triggers when a new customer is created in Syncro.

• Trigger
  New Invoice

  Triggers when a new invoice is created in Syncro.

• Trigger
  New RMM Alert

  Triggers when a new RMM alert is raised on a monitored asset in Syncro.

• Trigger
  Ticket Status Changed

  Triggers when a Syncro ticket moves to a different status.

• Action
  Create Appointment

  Creates an appointment in Syncro, optionally linked to a customer, ticket and technicians.

• Action
  Create Contact

  Creates a contact under an existing Syncro customer.

• Action
  Create Customer

  Creates a new customer in Syncro with contact details, address, and notification preferences.

• Action
  Create Estimate

  Creates an estimate for a customer in Syncro, optionally with line items.

• Action
  Create Lead

  Creates a new lead in Syncro with the contact details and optional ticket information you provide.

• Action
  Create Ticket

  Creates a ticket for a customer in Syncro.

• Action
  Create Ticket Timer Entry

  Logs a time entry against a Syncro ticket, recording when work started and ended (or how long it took) and any notes.

• Action
  Find Customer

  Finds customers by search text, email, name, business name or ID and returns the matching customers.

• Action
  Update Contact

  Updates an existing contact in Syncro, changing its name, address, email, phone and other details.

• Action
  Update Customer

  Updates an existing customer in Syncro. Only the fields you fill in are changed.

• Action
  Update Ticket

  Updates an existing Syncro ticket's subject, status, assignment, dates and other details. Only the fields you fill in are changed.

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