Expose HTTP Verb to Workflows when triggered by a Webhook

[Christopher_B]

Feature Request: Include an "httpMethod" or "httpRequestMethod" (or some similarly named) attribute inside of the startTrigger object of a Workflow triggered by webhook.

Use Case
General: Create RESTful programmatic access to Retool DB. In order to CRUD resources. These resources will then be displayed via the UI of a Retool App.

Specific: We use an external landing page builder and we want to send analytics "event" resources to the Retool DB and then display them on an analytics page built in Retool.

Existing Workarounds and Limitations

1. We could create distinct workflows which include the method in the path such as "getEvent" and "createEvent". However, REST is becoming an ubiquitous standard and we would prefer to model the API around resources.
2. Include a "method" attribute in the POST body and send a value like "GET" or "POST". The workflow then branches off of this. This adds unnecessary data. We currently are using this workaround.
3. Build an API outside of Retool and access the data via a REST API resource within the Retool app. This is feasible, but we would prefer to centralize our data if possible. The Retool DB interface and workflows interface also has the added benefit that non-software engineer co-workers can contribute to the work.

See the attached screenshot for illustration.

[Paulo]

Hi @Christopher_B, I found the internal FR that @Jack_T added your +1 to. Since this topic is more detailed and contains an excellent illustration, we'll leave it open to collect +1s.

We'll update you here with any news from our devs!