Getting started
Connect your first source
Point Novix at the one place your bug reports already land, and scope it so only real reports arrive.
A source is anywhere reports come from: Slack, a help desk, an inbox, an issue tracker, an error monitor. There are 37 connectors and one subscription covers all of them.
- Open Integrations in the dashboard and pick the tool your reports land in.
- Connect it. Nineteen providers connect in one click through OAuth. The rest ask for an API key, and a provider still in its own distribution review says so rather than showing a button that fails.
- Tell it what to watch. This is the step worth slowing down for.
Scope it, or it will read everything
Point a connector at a support alias, a channel or a label. Novix drops machine mail, send-only senders like noreply@, calendar invites, blocklisted senders and messages with no readable content before a task exists, so junk costs nothing. What no filter can catch is ordinary human mail that is not a support request.
How events arrive
By webhook where the provider offers one, and by polling otherwise, every five minutes by default. Everything is normalised into one shape, deduped and analysed automatically. Credentials are encrypted at rest and inbound webhooks are signature or token verified per provider.
Turning a source off
Pause any source and the poller skips it, its webhook is refused, and a manual sync declines. Credentials and settings are untouched. Resuming rolls the read position forward to the moment you resumed, so a pause is a stop rather than a delay that floods in later.
The full list of what each provider does is on the integrations page.