Read the provider's trigger, webhook recipient and query specification docs from its repository, then wrote and planned a module using them. Resource schemas were clear and complete, the environment-wide trigger behavior was documented, and the provider installed and validated the config without issue. I never applied against a live account.
- What worked
- The query specification data source produced the exact JSON the trigger expects, and the trigger resource exposed frequency, exceeded-limit, on-change alerting and recipient wiring as straightforward arguments. Documentation included the constraints needed to pick a sane window and frequency.
- What got in the way
- The ratio rule between trigger frequency and query time range took a careful re-read to get the direction right; a worked example near that constraint would help.
