Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.whatsable.app/llms.txt

Use this file to discover all available pages before exploring further.

Never commit tokens or API keys to Git. Treat NOTIFYER_API_TOKEN and the Developer API key as production secrets.

​
Required environment variables

VariableRequiredDefaultUsed for
NOTIFYER_API_BASE_URLyes—Base API host (must be HTTPS), e.g. https://api.insightssystem.com
NOTIFYER_API_TOKENyes (most scripts)—JWT returned by setup-notifyer/scripts/login.js
NOTIFYER_CHAT_ORIGINnohttps://chat.notifyer-systems.comOrigin header for chat endpoints when overridden
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."

​
Auth modes (critical)

Notifyer has three auth modes depending on the API surface. The same JWT is used for Console and Chat modes — only the header formatting differs.
ModeHeaderWhere it’s used
ConsoleAuthorization: Bearer <jwt>setup-notifyer and automate-notifyer (most endpoints)
ChatAuthorization: <jwt> (raw)chat-notifyer and some web endpoints (labels/recipients/chat)
DeveloperAuthorization: <api_key> (raw)Make/Zapier/n8n modules + direct developer send APIs
If you see HTTP 401 across many scripts, your JWT likely expired. Re-run setup-notifyer/scripts/login.js and re-export NOTIFYER_API_TOKEN.

​
Origin headers & CORS behavior

Many Xano endpoints enforce allowed origins. The skills’ shared HTTP client automatically sends a correct Origin header per mode:
  • Console-mode requests use Origin: https://console.notifyer-systems.com
  • Chat-mode requests use Origin: https://chat.notifyer-systems.com (override with NOTIFYER_CHAT_ORIGIN)
This is important because “missing Origin” can cause silent or confusing auth failures on endpoints that validate it.

​
Persisting environment variables

Add these exports to your shell profile: 
# ~/.zshrc
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."

​
Security notes for CLI usage

Passing secrets via CLI flags (like --password) can expose them via process lists (ps aux) on shared machines. Prefer using a password manager/secure terminal, and avoid logging stdout in shared CI environments.