5
Human readable webhook URLs
Source: directus/directus#22593 · opened by @inovosel
Summary Currently webhook flows have an URL with webhook trigger id (/flows/trigger/:this-webhook-trigger-id) so it's hard to identify what that webhook does based only on the url. Basic Example An example of current webhook trigger url: Alias with custom slug or a slug based on a flow name: Motivation It's hard to track what each trigger does just based on the URL, especially if multiple links are provided to a third party that needs access to your API. Without access to Directus or additional documentation it's impossible to identify them. Detailed Design Having an alternative alias with custom slug or slug automatically generated based on the flow's name would make working with webhooks easier, especially when working with multiple webhooks. • adding an additional (optional) Slug field to webhook flow • automatically filling the Slug field with slugified name of the flow • option to override autofilled slug with custom value…
No pledges yet. Be the first to back this.
Comments
Similar requests
Internal Linking Solution
52 votes · 0 comments
Allow manually setting the order in the collection chooser dropdown in the builder interface
1 vote · 0 comments
Flows support for saving binary data as a file
31 votes · 0 comments
Add support for accessing raw request body in custom endpoints
2 votes · 0 comments
Add ability to add headers to webhook requests
1 vote · 0 comments
No comments yet.