# Using the management API in flow actions

**URL:** <https://community.auth0.com/t/using-the-management-api-in-flow-actions/60689>\
**Category:** Get Help\
**Tags:** actions, auth0\
**Created:** [April 7, 2021, 1:38pm UTC](https://community.auth0.com/t/using-the-management-api-in-flow-actions/60689 "2021-04-07T13:38:38Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![alexab](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/alexab/32/13403_2.png) [@alexab](https://community.auth0.com/u/alexab)\
**Post date:** [April 9, 2021, 6:50am UTC](https://community.auth0.com/t/using-the-management-api-in-flow-actions/60689/5 "2021-04-09T06:50:35Z")

</div>

Thanks for a great reply. So in the ideal world, I would like:

1. The management API was just ready to use without a require statement, or at least could be initialized without any required parameters (it should be able to grab domain, clientId, secrets etc. from the context).
2. My specific use-case was user linking and user/app metadata updates, but when I look at the documentation for the management API, I can see many potential relevant operations 🤔

I hope that answers the question. Now that I have your attention, would you mind taking a look at one of my other questions regarding actions [here](https://community.auth0.com/t/postloginaction-throw-error/60759)? I know that I can always contact auth0 support and get really good help, I just think it makes more sense for the general public to have these things covered. In my opinion it’s just faster/better to find the answers in the community that opening/closing support cases 🙃

---

_[View the full topic](https://community.auth0.com/t/using-the-management-api-in-flow-actions/60689)._
