Hey everyone, wanted to close the loop on this.
Last week we did indeed find an error in our documentation about custom triggers and fixed it. Specifically, the documentation had the wrong JSON response body and did not include any information about authorization.
Here’s the section we updated, if you’re interested:
