bezosacademy — Customer Success Report

1. Employee Offboarding (Asana + Zendesk)

Category: IAM — Employee offboarding, Identity lifecycle automation

Description: An end-to-end offboarding workflow triggered by Asana project creation events. When a new offboarding project appears in Asana, Blink detects it via webhook, creates corresponding Zendesk tickets, and builds warehouse task records by polling Zendesk on a recurring schedule. The pipeline is kept alive by daily webhook re-registration.

Business problem solved: Manual coordination between HR (Asana), IT ticketing (Zendesk), and a data warehouse during employee departures is error-prone and slow. This automation ensures offboarding tasks are created, tracked, and warehoused consistently without human handoffs.

Integrations: Asana, Zendesk, Blink Tables (data warehouse)

2. Network Infrastructure Monitoring (Meraki)

Category: Other — IT/OT & network infra monitoring

Description: Daily automated monitoring of Cisco Meraki WAN uplink health across the network. One playbook checks uplink statuses each morning and sends an alert email only when changes are detected; a second delivers a broader daily network health report with rich HTML formatting. An on-demand utility supports ad-hoc Meraki API queries.

Business problem solved: Network operations teams lack visibility into WAN health degradation until users report outages. These automations provide proactive, daily uplink change detection and operational reporting without requiring manual checks.

Integrations: Cisco Meraki, Blink Email, Blink Tables

3. Endpoint & Device Compliance

Category: Other — Endpoint hygiene & MDM ops

Description: A set of automations designed to build and maintain a unified device inventory by ingesting data from Intune (Windows) and Jamf (macOS and mobile). A main orchestrator runs these ingestion jobs in sequence and logs compliance run results to a Blink table. Currently inactive — all playbooks show zero executions.

Business problem solved: Without a unified device inventory spanning MDM platforms, compliance teams cannot reliably answer questions about managed device coverage, OS versions, or missing agents. This pipeline was designed to centralize that data automatically.

Integrations: Microsoft Intune, Jamf, Blink Tables

4. HR Data Privacy & Compliance

Category: GRC — AI / HR compliance automation, DSAR & privacy automation

Description: A scheduled daily job that clears the race/ethnicity field in Greenhouse for all applicable records. Produces a summary report of removed and failed records, emailed via Blink.

Business problem solved: Retaining sensitive demographic data past its purpose violates privacy policies and HR compliance requirements. This automation enforces a data minimization policy daily without requiring HR or IT to perform manual database operations.

Integrations: Greenhouse, Blink Email, Blink Tables

5. IAM & Access Management

Category: IAM — Access review & group mgmt, Identity sync & directory mgmt

Description: Two on-demand utilities for group membership management and calendar delegation via Microsoft Entra ID. Both are available for manual invocation but show no executions in the past 12 months, suggesting they are either newly built or rarely needed.

Integrations: Microsoft Entra ID (Active Directory)

6. Development / Testing

Category: Other — IT helpdesk & ticket routing, SaaS / IT administration

Description: A collection of prototype and test playbooks covering web forms, age-check logic, Microsoft Forms webhooks, and Asana webhook validation. None have production executions.

Strengths

• Offboarding pipeline is production-grade and high-volume. The Asana → Zendesk → warehouse offboarding chain ran over 550 times in total across its pipeline stages (414 subflow executions processing individual tickets, 121 main orchestrator runs, 13 event triggers). This is clearly a core operational dependency.
• Network monitoring is fully automated. Both the WAN status check and the daily Meraki report have run consistently — approximately 40 executions each, aligning with weekday schedules across ~8 months. Proactive alerting is in place.
• HR compliance automation is active. The Greenhouse data sanitization job runs daily and is one of the more privacy-sensitive automations in the tenant — a strong GRC signal.
• Well-structured multi-workspace architecture. The tenant uses separate workspaces to isolate operational vs. sandbox workflows, a good practice for governance.

Gaps & Opportunities

• Device Compliance pipeline is built but idle. The Intune + Jamf → unified inventory system (6 playbooks) has zero executions. This represents a ready-built capability that hasn't been activated — scheduling the main orchestrator or connecting it to a trigger would immediately deliver endpoint compliance coverage.
• IAM utilities are underutilized. "Add to Group" and "Delegate Calendar Access" are available on-demand but unused. Converting these to self-service web forms or connecting them to an HR event stream (e.g., Workday, BambooHR) would multiply their value.
• No SOC or security alerting automation. The tenant has no active workflows covering threat detection, alert triage, phishing response, or vulnerability management. Given the school environment (student and staff PII), this is a meaningful coverage gap.
• Microsoft Forms integration explored but not deployed. The Microsoft Forms Testing webhook exists but was never used in production. If forms-based intake is a use case (e.g., IT helpdesk requests), this could be completed.

Integration Ecosystem