IT Workflow Automation Tools: ITSM, Infrastructure, Integration and Google Workspace Admin Compared

The layers of IT automation

Tool lists fail because they mix layers, so a patching tool sits next to a ticketing tool as if they competed. They don't. The table separates five layers, with examples taken from each vendor's own documentation and where each kind of tool tends to run out of road.

The layers stack instead of competing. A new hire's request can start in a service desk, trigger a Google Workspace account, enroll a laptop and open a cloud role, and each step belongs to a different tool.

Tickets, requests and approvals

If the work arrives as a request that people have to approve, track and close, an IT service management platform is the natural home for it.

ServiceNow describes Flow Designer as a no-code environment for building workflows, available with the ServiceNow AI Platform. Its documentation lists codeless flow building, application-specific actions, a decision builder for complex logic and role-based flow management, which lets a flow run with its own roles. It is built for large organizations that want one platform across IT and other departments.

Jira Service Management adds a customer portal and a rule builder on top of Jira. Atlassian's guidance on automating the lifecycle of a request walks through the typical steps: assign the request by type, notify the user, auto-approve against set criteria, send SLA warnings, resolve with knowledge articles, provision resources and close after fulfilment. It fits teams that already work in Atlassian tools.

Where it stops: these platforms automate what happens to a record inside them. Changing a server or a device still needs a tool from another layer, and changing a Google Workspace account needs an integration or workflow step that can call Google's admin functions.

Servers and cloud infrastructure

Ansible is Red Hat's automation platform for servers, networks and clouds. Red Hat's datasheet describes it as built on an agentless framework, and its automation is written as playbooks in human-readable YAML. It suits system administrators and DevOps teams who want repeatable configuration and patching.

Terraform is HashiCorp's infrastructure as code tool. HashiCorp's own introduction says it manages infrastructure with configuration files rather than a graphical interface, works across multiple cloud platforms through more than 1,000 providers, and tracks real infrastructure in a state file that can be kept under version control.

Where it stops: both are code-first. They are the right choice when engineers own the process, and a poor fit when the person who needs the automation is an IT generalist or an operations manager who doesn't write code.

Devices and endpoints

Microsoft Intune manages devices and apps across an organization. According to Microsoft's documentation, you can define and enforce compliance policies such as password complexity and encryption, deploy apps, and run remote actions such as locating a device, changing a password or wiping it, across Windows, Android, macOS and iOS.

Where it stops: it manages the device, not the business process around it. Deciding that a leaver's laptop should be wiped is a workflow, and the wipe itself is an Intune action. Teams usually connect the two.

Connecting apps

Integration platforms move work between apps. Zapier is built around triggers and actions: a trigger is the event that starts the automation, such as a new user, and an action is what it then does. n8n describes itself in its documentation as a fair-code licensed tool that connects any app with an API to any other with little or no code, and it can be self-hosted, which some teams choose for privacy and security. Make is a visual alternative in the same group.

Where it stops: approvals, audit trails and error handling differ between tools, and pricing models differ too, so check how cost grows with the number of runs before you build anything business-critical on one.

Google Workspace administration

This is the layer generic tool lists skip. Google Workspace has its own administration functions, and there are three ways to automate them.

Call the Admin SDK directly. Google's Directory API lets you create and manage users and administrators, groups and group memberships, devices on your domain and your organizational structure, and audit the apps users have granted access to and revoke unauthorized ones. It is the most complete option and also the one that needs a developer to build and maintain it.

Use an integration platform's Google Workspace Admin app. Zapier lists a Google Workspace Admin integration for managing users, groups and roles, with a "New User" trigger and an "Add User to Group" action among its examples. For simple provisioning that may be all you need. Before you rely on it, compare its action list with the tasks you actually run, because the number of admin actions a connector exposes is what decides whether it covers your process.

Use a workflow platform built around admin actions. Zenphi's listing on the Google Workspace Marketplace describes dedicated Google Admin automation actions, including user provisioning, automated access revocation and audits of licences, shared files and email forwarding rules. The practical difference is not that other tools can't touch the Admin API. It is that provisioning, approvals and a logged record can sit in the same flow, without code. Zenphi is our product, so weigh that listing as a vendor description.

A quick test for any tool in this layer: list the five admin tasks you run most, such as creating a user, adding them to groups, moving them to an organizational unit, revoking an app's access and removing a leaver, and check each one against the tool's action list before you commit.

What this looks like in practice

Three organizations show the range, from day-to-day admin to offboarding at scale. The figures below are reported by each customer in our own case studies, so read them as customer-reported results rather than independent benchmarks.

The Google Cloud Space example is worth sitting with, because it is a team at Google using this approach for its own Workspace admin. Its Cloud Space Architect, Jens Gössing, described investing in the process logic once so that, in his words, human error is no longer a thing. The common thread across all three is not a single admin action, since creating a user or revoking access is the same everywhere. It is running the whole sequence the same way every time, with approvals and a record, which is what a workflow layer adds over a one-off script or a connector.

What a combined setup looks like

Most teams end up with a small stack, with one tool per layer. Here is one illustrative example for onboarding, not a recommendation of specific products:

1. A new-hire request is raised and approved in the service desk.
2. An integration or workflow step creates the Google Workspace account and adds the person to the right groups.
3. A device-management tool enrolls the laptop and applies its compliance policy.
4. Infrastructure access for engineers is granted through the configuration tool.
5. Each step is logged so you can show who approved and when.

The last point is the one teams skip. Sensitive access changes should keep an approval and a record, whichever layer performs them.

Which layers do you need?

Pick the jobs you want to automate. The tool shows which layers they fall into and which tools from this guide belong to each, so you can see whether one tool will cover the list. It is a starting point, not a verdict.

FAQ

Sources

• ServiceNow — Flow Designer
• Atlassian — Automate the lifecycle of a request
• Red Hat — Ansible Automation Platform datasheet
• TechTarget — Ansible definition
• HashiCorp — What is infrastructure as code with Terraform
• Microsoft Learn — Intune devices and apps API overview
• n8n documentation
• Zapier — Google Workspace Admin integration
• Google for Developers — Directory API (Admin SDK)
• Google Workspace Marketplace — Zenphi listing
• Zenphi — Gordon Food Service case study
• Zenphi — Google Cloud Space Munich case study
• Zenphi — High-turnover offboarding case study

Pages were checked on October 14, 2026 and can change. We did not test the third-party tools, so their descriptions follow each vendor's own documentation. The Zenphi listing and the Gordon Food Service figure come from Zenphi pages, so read them with that in mind.