Can I install a template without its sample records firing webhooks?

Be careful here: a Busabase template's sample records are normally merged during installation, even though its App code and Skill may still wait for review. A merged new record can fire a matching record-created webhook. “The template is awaiting review” does not make its sample data inert.

For a first inspection, run the CLI install with --dry-run and review the package in an isolated workspace that has no production webhook rules or external credentials. The CLI also offers --no-sample-records to propose template sample rows for review instead of merging them immediately; check the dry-run result for the particular package, because review-first installation can be blocked when sample rows contain relations to other new sample records. Once you understand the template, install into the intended workspace with a deliberate webhook plan. Do not assume there is a global switch that suppresses every external automation triggered by installation. Which template and which webhook rule are you trying to protect?