Email and GitHub
Who this is for: anyone checking whether Liitora connects Email and GitHub, and what a library workflow that does so can access.
Before you start: nothing, to read this page. Each workflow below lists the connections and company variables it needs.
Library workflows that connect them
Section titled “Library workflows that connect them”One library workflow connects Email and GitHub.
Leaver access check
Section titled “Leaver access check”When HR reports that someone has left, check Entra ID and GitHub for access that is still there, open a ticket for each remaining account and email the owner.
| What | Details |
|---|---|
| Publisher | Liitora (Published by Liitora) |
| Signature | Liitora signs version 1.0.0 and its content hash sha256:56ebe1168502e98b5279e5b107adee161d98aee6b1da63964d52dbb8ac68301c, and checks both again before it copies the workflow into your company. |
| Connections | github-org: GitHub. Reads organisation membership. Read-only for this workflow.m365: Microsoft 365 (Microsoft Graph). Reads whether the account is enabled. Needs only User.Read.All.service-desk: Your service desk. Creates one ticket per remaining account. |
| Company variables | entra_owner, github_org, github_owner |
| Secrets | None |
| Sends out | |
| Personal data | The leaver’s employee id, user principal name and GitHub handle, sent to your service desk and to the system owners. |
| Checks | Liitora checked that the connections, company variables, secrets and saved state it declares match what the workflow uses. Its 7 tests pass against the real test runner. |
Read the full trust page of Leaver access check.