Jira and Google Workspace Admin
Start a workflow in one and act in the other, with every step on the record. Ask your AI for it, or build it yourself.
- Jira steps
- 17
- Google Workspace Admin steps
- 32
Ideas for Jira and Google Workspace Admin
Each one is a real trigger and action. Ask your AI for any of them, in your own words, and it builds the workflow.
- When
New issueThen
Create user - When
New userThenCreate an issue
- When
Issue updatedThen
Update user - When
New or updated userThenMove an issue to a new status
- When
Issue status changedThen
Create user alias - When
New groupThenComment on an issue
Templates that use Jira and Google Workspace Admin
What each app adds
Jira
Triggers
- New issueRuns when an issue is created in Jira.
- Issue updatedRuns when an existing issue changes in Jira: its fields, status, assignee or a new comment, with the issue as it is now.
- Issue status changedRuns each time an issue moves to another status in Jira, such as from In Progress to Done, with who moved it and when.
- New commentRuns when someone comments on an issue in Jira, with the comment, who wrote it and the issue it is on.
Actions
- List projectsList the Jira projects your connected account can see.
- Create an issueCreate an issue in a Jira project, with a title and, if you like, a description, type, priority, assignee, due date, labels and component. To make a sub-task, choose a sub-task type and the issue it belongs under.
- List the statuses an issue can move toList the statuses a Jira issue can move to from the one it is in now, with the move that takes it to each.
- Move an issue to a new statusMove a Jira issue to another status, such as In Progress or Done. The project's workflow decides which statuses it can move to from the one it is in now.
- Comment on an issuePost a comment on a Jira issue.
- Get an issueLook up a Jira issue: its title, description, status, assignee, priority, labels and due date.
Google Workspace Admin
Triggers
- New userRuns for each new user in Google Workspace Admin. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
- New or updated userRuns for each user added or changed in Google Workspace Admin. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
- New groupRuns for each new group in Google Workspace Admin. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
- New or updated groupRuns for each group added or changed in Google Workspace Admin. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
- New organizational unitRuns for each new organizational unit in Google Workspace Admin. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
- New or updated organizational unitRuns for each organizational unit added or changed in Google Workspace Admin. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
Actions
- List usersList the people in your Google Workspace, one page at a time (up to 500 a page), each with their name, email, last sign-in and whether they are suspended. Beta: turn on Read every page to get everyone in one step. To find people who haven't signed in for a while, use "List users who haven't signed in" instead.
- List users who haven't signed inBeta. List the Google Workspace users who haven't signed in for a number of days (inactive, dormant or unused accounts), ready for a report: each person's name, email, last sign-in date and days since, longest first, with a count. Google's directory cannot search by last sign-in, so this reads every page of users itself and keeps the ones that match: no loop, filter or paging steps needed. Suspended and archived accounts are left out unless you ask for them. People who have never signed in are included and marked.
- Get userLook up one person in your Google Workspace by email address or ID, with their name, last sign-in, organizational unit and whether they are suspended or an administrator.
- Create userCreate a Google Workspace account for a new person, with their name, sign-in email address and password.
- Update userChange a person's Google Workspace account: their name, email address, password, organizational unit, or suspend or restore them. Only the fields you fill in change.
- Delete userDelete a person's Google Workspace account. It can be restored for 20 days with Restore user.
How to connect Jira and Google Workspace Admin
Connect your AI
Add Lodol to Claude, ChatGPT, Cursor or any MCP tool in one step, or open the editor.
Connect Jira and Google Workspace Admin
Sign in to each once in your workspace. Their keys are encrypted and used by name.
Describe it, then turn it on
Say what should happen, and when. Try a run, then turn it on; every run is traced.
Questions about Jira and Google Workspace Admin
Yes. Connect each app once in your Lodol workspace and any workflow can use both: 13 actions and 4 triggers in Jira, and 26 actions and 6 triggers in Google Workspace Admin.
Ask Claude, ChatGPT, Cursor or any AI tool connected to Lodol, in your own words, and it builds the workflow in your workspace. Or add the steps yourself in the visual editor, or start from one of the 1 template that already use both.
Free includes 100 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes.
Connect Jira and Google Workspace Admin.
Ask for it in Slack, Claude or ChatGPT. Lodol does it every time, and tells you if anything breaks.
Free plan, no credit card