PipedreamHQ
New Components - opsgenie
Resolves #11627.
Note to QA: To manage alerts, use the API key in Teams->Integrations, not the API key in Settings->Api Key Management
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| docs-v2 | ⬜️ Ignored (Inspect) | Visit Preview | Apr 24, 2024 8:07pm | |
| pipedream-docs | ⬜️ Ignored (Inspect) | Apr 24, 2024 8:07pm | ||
| pipedream-docs-redirect-do-not-edit | ⬜️ Ignored (Inspect) | Apr 24, 2024 8:07pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
@vunguyenhung
Note to QA: To manage alerts, use the API key in
Teams->Integrations, not the API key inSettings->Api Key Management
Hey @michelle0927, I see, we need another API Key. After using the API Key in Teams > Integration, I can create the alert
Though the use of API key from Teams > Integration is not visible to users on the connection popup
I think we need to improve the connection popup to add the field for Team Integration API Key (optional), and note that it is needed for using Alert related actions
I've created a ticket here to improve the connection popup: https://github.com/PipedreamHQ/pipedream/issues/11641
I think we can mark this ticket as blocked until the ticket above is done. What do you think @malexanderlim @michelle0927?