capabilities.work

Configure Enterprise Pub/Sub Notifications

A 3-step recipe with Google Android. We can help you get access.

Recipe · 3 steps

Configure Enterprise Pub/Sub Notifications

with Google Android · Information Technology Management

Point an enterprise at a Pub/Sub topic and confirm the notification types stuck.

  1. Read the enterprise to capture the notification configuration in force before the change, so the patch can be reviewed or reverted.
  2. Patch the Pub/Sub topic and notification types. The updateMask restricts the write to these two fields so the enterprise display name, logo, and primary color are left intact.
  3. Read the enterprise back to confirm the topic persisted. A topic the Android Management service account cannot publish to is rejected here rather than failing silently later.
What you'll need to have ready
  • enterpriseName: The enterprise resource name (e.g. enterprises/LC0123abcd).
  • pubsubTopic: The Pub/Sub topic to publish to (e.g. projects/my-project/topics/android-notifications).
  • enabledNotificationTypes: The notification types to enable (e.g. ENROLLMENT, STATUS_REPORT, COMMAND).
For your developer

Arazzo workflow google-android:configure-enterprise-notifications, 3 operations: getEnterprise → patchEnterprise → getEnterprise. Specs on APIs.io.

More recipes with Google Android

Enroll a Device and Confirm It Checked InOffboard an EnterpriseOnboard an EnterpriseAudit an Enterprise FleetRoll Out a Policy Change and Verify It AppliedIssue a Remote Command and Poll the DevicePublish a Web App and Push It to a Policy