Actions are secure, tenant-specific, self-contained functions that allow you to customize the behavior of Auth0. Each action is bound to a specific triggering event on the Auth0 platform. Auth0 invokes the custom code of these Actions when the corresponding triggering event is produced at runtime. Actions will work in tandem with Rules and Hooks!
I’ve briefly tried to use the new Actions feature to see if it would give a proper session Id (the one that’s visible in the logs). Unfortunately, it doesn’t.
I have written quite a few Rules. My main point of constructive criticism for Actions is around the developing/debugging experience. With Rules I could put console.log statements everywhere and see the output in the debug window while logging on with a real user.
With the new Actions, it seems that the only way to test is to manually set a test payload, which doesn’t give me much confidence since I don’t know how a real payload will differ from what I put in.
With the new Actions, all console.log output is concatenated together in a string and truncated after 267 characters. This makes the development workflow for actions very difficult.
Hello Auth0 team,
I am seeking to use Actions to call a Graph API but am struggling to capture a user’s access_token from Auth0’s payload. Actions appears to only accept a nested object as a payload (per the sample payload in the sandbox) whereas the payload I’m receiving from Auth0 is flat. My question is two part 1) can I manipulate the object passed into my Action and if not 2) is there a way to write my action to work with a flat object? Thanks!
I love the new Actions and the possibilities they offer. I’d go ahead and rewrite all of the Rules into Actions as I find the API much more appealing. To make that happen though, I am missing a few things like either a Management API Token, or direct access to Roles and Permissions / Scopes. Either way would work though