# Webtask credentials for deployment pipeline

**URL:** <https://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981>\
**Category:** Get Help\
**Tags:** tokens, webtask, hooks, deployment\
**Created:** [December 14, 2017, 1:01pm UTC](https://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981 "2017-12-14T13:01:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jerome.paul](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@jerome.paul](https://community.auth0.com/u/jerome.paul)\
**Post date:** [December 14, 2017, 1:01pm UTC](https://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981/1 "2017-12-14T13:01:29Z")

</div>

We prefer having an automated process to deploy anything.

I’ve been looking at options to deploy an Auth0 Hook from my build pipeline. The Tenant settings show a way to initialise the `wt-cli` ([https://manage.auth0.com/#/tenant/webtasks](https://manage.auth0.com/#/tenant/webtasks)), however the token shown doesn’t seem to have an expiry, or a way to revoke it, and is not contextualised to the currently logged in auth0 user…

I’ve looked at using `wt init` without a token, however that does not seem capable of linking to an Auth0 Tenant…

Does anyone have a deploy pipeline for Auth0 hooks?

It would be great to be able to programmatically get a time-limited token using perhaps the Management API with an accompanying Client ID and Secret.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [December 14, 2017, 7:54pm UTC](https://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981/2 "2017-12-14T19:54:00Z")

</div>

I’m not aware of short term plans to include that as part of management API, but things change so not saying it will never happen. However, **at this time, deployment automation of hooks would need to be performed through the [CLI interface](https://auth0.com/docs/hooks/cli)**.

In relation to the token characteristics, have in mind that you can use the [Webtask API to issue a derived token](https://webtask.io/docs/api_issue) from the one you obtained and that might give you the characteristics you’re looking for in terms of expiration/revocation. I confess that I never actually do what I’m mentioning and this statement is purely backed by me looking at the docs.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/webtask-credentials-for-deployment-pipeline/8981/3 "2018-03-02T05:57:48Z")

</div>


