Can HumDay connect to Google Identity Toolkit?

Yes. HumDay reads Google Identity Toolkit's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 27 operations are documented.

Do I need to write code to automate Google Identity Toolkit?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Identity Toolkit account.

What can HumDay do in Google Identity Toolkit?

20 of the 27 documented operations change something in Google Identity Toolkit, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Identity Toolkit account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Identity Toolkit is held behind that approval.

Automate Google Identity Toolkit

HumDay reads Google Identity Toolkit’s own published API description and derives 27 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Identity Toolkit is

The Google Identity Toolkit API lets you use open standards to verify a user's identity.

API host: identitytoolkit.googleapis.com

What HumDay can do in Google Identity Toolkit

20 documented operations change something in Google Identity Toolkit.

POSTRevokes a user's token from an Identity Provider (IdP)./v2/accounts:revokeToken
POSTSends the MFA challenge/v2/accounts/mfaSignIn:start
POSTCreates and returns the passkey challenge/v2/accounts/passkeySignIn:start
POSTFinishes enrolling a second factor for the user./v2/accounts/mfaEnrollment:finalize
POSTVerifies the passkey assertion and signs the user in./v2/accounts/passkeySignIn:finalize
POSTFinishes enrolling a passkey credential for the user./v2/accounts/passkeyEnrollment:finalize
POSTCreate an Oidc Idp configuration for an Identity Toolkit project./v2/{parent}/oauthIdpConfigs
POSTCreate a default supported Idp configuration for an Identity Toolkit project./v2/{parent}/defaultSupportedIdpConfigs
DELETEDelete an Oidc Idp configuration for an Identity Toolkit project./v2/{name}
PATCHUpdate an Oidc Idp configuration for an Identity Toolkit project./v2/{name}
POSTGets the access control policy for a resource./v2/{resource}:getIamPolicy
POSTSets the access control policy for a resource./v2/{resource}:setIamPolicy
POSTReturns the caller's permissions on a resource./v2/{resource}:testIamPermissions
POSTVerifies the MFA challenge and performs sign-in/v2/accounts/mfaSignIn:finalize
POSTStep one of the MFA enrollment process./v2/accounts/mfaEnrollment:start
POSTRevokes one second factor from the enrolled second factors for an account./v2/accounts/mfaEnrollment:withdraw
POSTStep one of the passkey enrollment process./v2/accounts/passkeyEnrollment:start
POSTInitialize Identity Platform for a Cloud project./v2/{project}/identityPlatform:initializeAuth
POSTCreate a tenant. Requires write permission on the Agent project./v2/{parent}/tenants
POSTCreate an inbound SAML configuration for an Identity Toolkit project./v2/{parent}/inboundSamlConfigs

What HumDay can read from Google Identity Toolkit

These are the operations a schedule or a trigger can watch.

GETList all default supported Idps./v2/defaultSupportedIdps
GETList tenants under the given agent project./v2/{parent}/tenants
GETList all Oidc Idp configurations for an Identity Toolkit project./v2/{parent}/oauthIdpConfigs
GETList all default supported Idp configurations for an Identity Toolkit project./v2/{parent}/defaultSupportedIdpConfigs
GETGets parameters needed for reCAPTCHA analysis./v2/recaptchaConfig
GETRetrieve an Oidc Idp configuration for an Identity Toolkit project./v2/{name}
GETList all inbound SAML configurations for an Identity Toolkit project./v2/{parent}/inboundSamlConfigs

How automating Google Identity Toolkit works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Identity Toolkit account.
Grant access, then go live. You approve the specific Google Identity Toolkit operations it may use — and only those.