FAQ
Zenphi helps IT teams standardize and execute workflows that are typically handled through tickets, hand-offs, and manual admin actions. Common examples include employee onboarding and offboarding, access lifecycle enforcement, group and shared drive governance, device and asset workflows, and recurring audit/reporting tasks.
The goal isn’t just automation—it’s consistent execution. Each workflow runs with the same logic every time, with built-in approvals, checks, and audit logs across Google Workspace and connected systems.
Yes. Zenphi is available directly on Google Cloud Marketplace, which means your subscription can be billed through Google — simplifying procurement and invoicing.
Even better, if your organization has an existing Google Cloud spend commitment, your Zenphi purchase can draw down on that commit, helping you maximize the value of your current budget. Read more on it here
Most automation platforms are designed for general-purpose orchestration—connecting apps and moving data between systems. Zenphi is different: it focuses on operational execution for IT teams, with workflows that enforce policies and complete actions reliably across Google Workspace and your connected tools.
Instead of relying on brittle scripts or bot-driven automation, Zenphi provides deterministic workflows with clear ownership, approvals, and audit trails—so routine operations are executed consistently, even when teams, systems, and requirements change.
Most teams start with workflows that are high-volume, high-risk, and easy to get wrong when handled through tickets or manual admin work. The most common first candidates are user onboarding and offboarding and data archiving, access provisioning and revocation, group and shared drive governance, and recurring compliance checks such as external sharing audits.
These workflows usually touch multiple systems, create repeated context-switching for IT, and carry real risk when execution is inconsistent. Standardizing them first delivers fast operational control and reduces exceptions immediately.
Custom scripts can solve a problem quickly—but they tend to become fragile over time. APIs change, logic forks, ownership gets unclear, and exceptions pile up. Eventually, teams spend more time maintaining scripts than executing the work they were written for.
Zenphi provides a governed execution layer: workflows are easier to standardize, update, and audit, with built-in approvals, error handling, and traceability. You keep full control over how tasks run—without accumulating long-term automation debt.
Zenphi facilitates the automation process, ensuring your data remains within your Google Workspace environment for utmost security and control. Learn more about Zenphi’s data security policy.
Auditability in Zenphi means that every workflow run is traceable end to end: what triggered it, what data was used, what decisions were made (including approvals), what actions were executed, and whether anything failed or required intervention.
Instead of reconstructing evidence across tickets, admin logs, and spreadsheets, teams get a consistent execution record by default—making audits, internal reviews, and compliance reporting more repeatable and less disruptive.
Zenphi workflows can be triggered in several practical ways, depending on how your IT team operates and where work starts. Common triggers include form submissions and self-service requests, scheduled or recurring runs (for audits and periodic checks), events and changes in Google Workspace (such as changes in the Directory, Groups, OUs), and actions coming from connected systems like HR, ticketing, or asset tools (via HTTP triggers).
This allows teams to shift from ticket-driven execution to event-driven execution—so policies and operational tasks run consistently when the right signal occurs, not only when someone remembers to act.