Connect Sprig and Syncro

Both apps 38Sprig 19Syncro 19

• Trigger
  New Study

  Triggers when a new study (survey) is created in Sprig.

• Trigger
  New Survey Response

  Triggers when a new answer to a Sprig survey question is submitted.

• Action
  Create Invitations

  Creates a batch of single-use invitation links for a Sprig survey.

• Action
  Create Survey

  Creates a draft shareable Sprig survey. Questions are added separately.

• Action
  Delete Draft Study

  Deletes a draft Sprig study. Only draft studies can be deleted.

• Action
  Delete Question

  Deletes a question from a Sprig study. Needs the study's current version.

• Action
  Get Question

  Returns one question of a Sprig study, with its options.

• Action
  Get Study

  Returns one Sprig study by its ID, including its current version.

• Action
  Get User

  Returns a Sprig user by user ID, with attributes and tracked events.

• Action
  List Attributes

  Returns the user attributes defined in the Sprig environment.

• Action
  List Events

  Returns the tracked events defined in the Sprig environment.

• Action
  List Invitations

  Returns invitation links of a Sprig survey, filtered by status.

• Action
  List Questions

  Returns the questions of a Sprig study.

• Action
  List Studies

  Returns a page of Sprig studies (surveys), optionally filtered by status or type.

• Action
  List Survey Responses

  Returns exported Sprig survey responses, optionally for one survey.

• Action
  Purge Visitors

  Requests deletion of Sprig users and all their data, by email or user ID (up to 100).

• Action
  Update Study Name

  Renames a Sprig study. Needs the study's current version from Get Study.

• Action
  Upsert User

  Creates or updates a Sprig user by user ID, setting email and attributes.

• Action
  Validate Study

  Checks a Sprig study and returns any issues that would block it from launching.

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

  Triggers when a new payment is recorded in Syncro.

• Trigger
  New RMM Alert

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

• Trigger
  New Ticket

  Triggers when a new ticket is created in Syncro, optionally limited to a customer, contact, status, assignee or search.

• Trigger
  Ticket Resolved

  Triggers when a ticket is marked Resolved 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
  Log Call

  Logs a phone call in Syncro by phone number and returns the matching customer's name and ticket status.

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

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