NotiStudio Documentation
NotiStudio watches your developer and business tools and routes the events they emit into the chat channels your team already uses. Connect a source, connect a destination, draw a route between them, and the right events show up where the right people will see them.
Core concepts
- Sources — where signals come from (GitHub, Stripe and Vercel today, with more on the way). You connect a source once — via OAuth, an app install, or (for Stripe) a guided webhook setup.
- Destinations — where notifications go (Discord and Slack channels). You connect a destination via a one-click OAuth flow; NotiStudio stores only the channel's webhook URL, encrypted.
- Projects — hubs you create to group related work. You bind a source's resource (a repository or a Vercel team) to a project.
- Routes — rules that connect a project to a destination, with optional filters on event category and severity. An event is delivered when it matches an enabled route.
Connecting a source
GitHub
Install the NotiStudio GitHub App on your account or organization and pick the repositories to share. NotiStudio receives repository events (pushes, deployments, workflow runs, and more) via signed webhooks. You can connect multiple GitHub accounts.
Stripe
Stripe connects without any OAuth grant: the connect wizard gives you a webhook URL unique to your workspace, you create a webhook endpoint for it in your own Stripe dashboard (the wizard pre-selects the recommended events), and paste the endpoint's signing secret back. NotiStudio verifies every delivery against that secret — stored encrypted — and surfaces your payments, payouts, failed charges, disputes, and churn in chat. Optionally, add a restricted read-only API key (never a secret key — those are rejected) to import up to the last 30 days of history. Your payment data stays minimal by design: payloads are redacted to non-personal, operational fields before anything is stored.
Vercel
Install the NotiStudio Vercel integration on your team. NotiStudio receives deployment events and turns the terminal ones into signals: a successful deploy, a failed deploy, and a canceled deploy. See "The Vercel integration" below.
Connecting a destination
From the Integrations page, click Connect Discord or Connect Slack, authorize the channel, and NotiStudio stores that channel's incoming-webhook URL (encrypted at rest). A channel that is later revoked is detected automatically and marked for reconnection.
Routing events
In Pipelines, bind a source resource to a project, then add a route from that project to a destination. A route can filter by:
- Category — what the signal is about (code, deploy, error, money, work, security, customer). Leave empty to match any.
- Level — how urgent it is (success, info, warning, critical). Leave empty to match any.
When a source delivers an event, NotiStudio resolves the projects that resource feeds, finds the matching routes, de-duplicates the destinations, and delivers the notification to each — retrying transient failures.
The Vercel integration
The NotiStudio Vercel integration sends your team's deployment outcomes to chat:
deployment.succeeded→ a success signal,deployment.error→ a critical signal,deployment.canceled→ a warning signal.
To set it up: install the integration, then on the Integrations page click Connect Vercel. Bind your Vercel team to a project, add a route to a Discord or Slack channel, and your deploys will start posting there. Every webhook is verified with an HMAC-SHA1 signature before it is processed.
Security
NotiStudio verifies the signature of every inbound webhook, encrypts destination secrets at rest, never stores your source providers' access tokens, and scopes all data to your account. For more, see our Privacy Policy.
Need help?
Visit Support or email jc@codefactory.ai.