Every Trigger can be configured with an AJV schema which will be run against the payload provided to the Trigger. If it fails then a validation response is returned and the Trigger is not invoked. This is handy when you have multiple possible sources or, as can be the case with https:POST Triggers, you want faster feedback on an invalid payload.

Merchant Portal Forms (merchant-customer widget)

When you define an https:POST Trigger for a Blueprint it is picked up and used by the Merchant portal, to render a form for a user to directly submit data to the Trigger.

ajv-schema-forms

Currently we only supoort a subset of AJV schema attributes for rendering a form. You can find the documentation on what is supported here.

Full support for AJV is on the roadmap. Let us know if this is a requirement of yours, [email protected].