Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Actions UI] Webhook action form with Body editor should support different HTTP body types, not only JSON #72202

Closed
YulNaumenko opened this issue Jul 16, 2020 · 4 comments
Closed

[Actions UI] Webhook action form with Body editor should support different HTTP body types, not only JSON #72202

YulNaumenko opened this issue Jul 16, 2020 · 4 comments
Labels
enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@YulNaumenko
Copy link
Contributor

Currently, if we created a Webhook connector (for example for Twilio):
img1
Supported content type for a POST request HTTP body isn't a JSON. It is application/x-www-form-urlencoded
But when we open and add a proper text to a Body parameter it will show a JSON error in the editor:
img2

Webhook action form should support different HTTP body types: text, json, form?
@YulNaumenko YulNaumenko added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jul 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@hendry-lim
Copy link

+1 for XML

@pmuellr pmuellr mentioned this issue Oct 6, 2020
Open
@gmmorris gmmorris added Feature:Actions Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework and removed Feature:Alerting labels Jun 29, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@mikecote mikecote mentioned this issue Oct 4, 2022
Open
@banderror
Copy link
Contributor

Related issue: #141176

@ymao1
Copy link
Contributor

ymao1 commented Jan 5, 2023

Closing due to lack of interest.

@ymao1 ymao1 closed this as completed Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: Done
Milestone
No milestone
Development

No branches or pull requests
7 participants
@gmmorris @kobelb @banderror @ymao1 @elasticmachine @hendry-lim @YulNaumenko