Connect ServiceWorks and Urban Airship

Both apps 36ServiceWorks 14Urban Airship 22

• Trigger
  Job Completed

  Triggers when a ServiceWorks job in the last 30 days reaches your completed status.

• Trigger
  New Job

  Triggers when a new job appears on the ServiceWorks calendar (scheduled from 30 days ago to 90 days ahead).

• Action
  Create Customer

  Creates a new customer in ServiceWorks with contact details and a service address.

• Action
  Create Job

  Creates a new job (work order) for a ServiceWorks customer, optionally scheduled.

• Action
  Find Customer by Phone

  Finds ServiceWorks customers that have the given phone number.

• Action
  Get Customer Service History

  Returns a ServiceWorks customer's past service jobs.

• Action
  List Jobs

  Lists ServiceWorks calendar jobs in a date range, optionally filtered by technician, type or status.

• Action
  List Payments

  Lists ServiceWorks payment history, one page at a time.

• Action
  Schedule Job

  Schedules or reschedules a ServiceWorks job trip.

• Action
  Search Customers

  Finds ServiceWorks customers by name or customer ID, with their addresses.

• Action
  Send Text to Customer

  Sends an SMS text message to a ServiceWorks customer.

• Action
  Set Customer Note

  Sets the note on a ServiceWorks customer.

• Action
  Set Job Note

  Sets the note on a ServiceWorks job trip.

• Action
  Update Customer

  Updates an existing ServiceWorks customer's name, company, email and phone numbers.

• Trigger
  New Channel

  Triggers when a new channel (device, email address or other endpoint) is registered in the Airship project.

• Action
  Add open channel

  Registers a new open channel, or updates the existing open channel for the same platform and address, and returns its channel ID.

• Action
  Add scheduled push

  Schedules a push notification to be sent at a future time, at each device's local time, at the optimal send time, or on a recurring cadence.

• Action
  Add segment

  Creates a new audience segment in Airship from a name and targeting criteria.

• Action
  Add SMS channel

  Registers a mobile phone number as an SMS channel in Airship, optionally marking it as already opted in.

• Action
  Add static list

  Creates a static list in Airship with a name, optional description and extra metadata. List contents are uploaded separately.

• Action
  Add Tags to Named User

  Adds tags in a tag group to a named user.

• Action
  Associate Named User

  Associates a device channel with a named user (your own user ID).

• Action
  Delete schedule

  Deletes a scheduled message so it will not be sent.

• Action
  Delete segment

  Deletes an audience segment.

• Action
  Delete static list

  Deletes a static list from your Airship project.

• Action
  Disassociate Named User

  Removes a channel or an email address from a named user in Airship.

• Action
  Find Email Channel

  Finds the email channel registered for an email address.

• Action
  Get Channel

  Returns one Airship channel (a device, email address or other endpoint) with its type, opt-in state, named user and tags.

• Action
  Get Named User

  Returns a named user with its tags, attributes and associated channels.

• Action
  List Channels

  Returns the Airship project's channels (devices, email addresses and other endpoints).

• Action
  List schedules

  Returns the scheduled push notifications in your Airship project, up to 200 per call.

• Action
  List segments

  Returns the audience segments defined in your Airship project, with each segment's id and display name.

• Action
  List static lists

  Returns all static lists in your Airship project with their metadata (name, description, status, channel count).

• Action
  Register Email Channel

  Registers an email address as an Airship email channel, opted in to commercial email.

• Action
  Remove Tags from Named User

  Removes one or more tags in a tag group from a named user.

• Action
  Send Push Notification

  Sends a push notification to every device of a named user.

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