Extending Ticqex
Activation config
The committed file that controls which channels and integrations are on.
Channels and integrations are switched on per deployment in config/ticqex.config.json (committed; config/ticqex.config.example.json is the template):
{
"channels": { "email": { "enabled": true, "integration": "resend" } },
"integrations": { "resend": { "enabled": true } }
}- A channel describes product behavior (email conversations on tickets).
- An integration is the external provider that powers it (Resend).
- A channel binds to exactly one enabled integration that has the capabilities it needs.
There is no UI for this — it's deliberately a deployment decision, validated at startup and by:
pnpm config:check— validates the bindings and that the required env vars for enabled integrations are present.pnpm config:sync— validates the activation JSON and prints the planned channel field sync as a dry run.
The file path can be overridden with the TICQEX_CONFIG_FILE env var.
When a channel is disabled, its settings sections, board surfaces, and webhook handlers simply don't load.