auth0-svg

Auth0

Identity Machine-to-machine client

Manage Auth0 users, roles, connections and applications on your tenant from any Windmill script, flow or app.

Set up in 3 steps

1

Create a machine-to-machine application

In the Auth0 dashboard, create a Machine to Machine application, authorise it against the Auth0 Management API, and grant only the scopes your scripts need.

2

Add the resource in Windmill

Open Resources, add a resource of type auth0. domain is your tenant host — yourtenant.eu.auth0.com — plus the client id and secret.

3

Run your first script

Fork any script below and read before writing anything.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

auth0 — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
domainstringYesYour Auth0 tenant domain, e.g. your-tenant.us.auth0.com or your-tenant.eu.auth0.com (no scheme, no trailing slash). Use a custom domain only if your Management API tokens are issued for it.
client_idstringYesClient ID of the Machine-to-Machine application authorized for the Auth0 Management API.
client_secretstringYesClient secret of the Machine-to-Machine application authorized for the Auth0 Management API.

Questions

Why a client pair and not a token?

The scripts exchange these for a short-lived Management API token on each run, so nothing expires in the resource.

A call fails on insufficient scope

Scopes are granted to the application against the Management API, not to the token. Add the scope on the application in Auth0 — the credentials stay the same.

Are my credentials stored on the hub?

Never. They live only in your own Windmill workspace, encrypted at rest.