Quickstart
Send your first alert and build your first workflow in under 10 minutes.
Before you start
You need an AlertFlow account. Sign up free — no credit card required.
Step 1 — Create your organization
After sign-up, AlertFlow prompts you to create an organization. This is your MSP's workspace — all integrations, team members, and workflows live here.
- Enter your organization name (e.g. "Acme MSP").
- Choose your plan (Starter is free).
- Click Create Organization.
You land on the dashboard. It's empty — let's fix that.
Step 2 — Create your first integration
An integration is a named connection between a monitoring source and AlertFlow. Each one gets a unique ingest token (URL) that your tools POST to.
- 1Open Integrations
In the left sidebar, click Integrations, then New Integration.
- 2Choose a type
Select Generic Webhook (or pick your specific tool from the list — Kaseya VSA, ConnectWise, etc.).
- 3Name it
Give it a descriptive name: "Kaseya Production" or "Test Integration".
- 4Save and copy the token
Click Create. Copy the Webhook URL — it looks like:
https://app.yourdomain.com/api/inbound/webhook/abc123xyz
Step 3 — Send a test alert
Use curl to POST a test alert to the ingest URL you just copied:
curl -X POST https://app.yourdomain.com/api/inbound/webhook/YOUR_TOKEN \
-H "Content-Type: application/json" \
-d '{
"title": "High CPU on WEB-01",
"severity": "high",
"source": "manual-test",
"labels": {
"host": "WEB-01",
"client": "Acme Corp"
}
}'
A 200 or 202 response means the alert was queued successfully.
You can also use the Test button inside the integration modal to fire a sample alert without needing curl.
Step 4 — View the alert
- Click Alerts in the left sidebar.
- Your test alert appears at the top of the list: High CPU on WEB-01, status firing, severity high.
- Click the alert to open its detail panel — you can see the raw payload, labels, and status history.
Step 5 — Build your first workflow
Now let's make AlertFlow do something useful when an alert fires.
- 1Open Workflows
Click Workflows in the sidebar, then New Workflow.
- 2Name and trigger
- Name: "Critical Alert → SMS"
- Trigger: Alert Firing
- 3Add a condition
Drag a Condition node onto the canvas. Configure it:
- Field: Severity
- Operator: equals
- Value: critical
This gates the rest of the workflow — only critical alerts continue.
- 4Add a notify step
Drag a Notify node and connect it after the condition's true branch. Configure it:
- Channel: SMS
- Recipients: your phone number (add it first in Settings → Profile)
- Message:
🔴 {{alert.title}} — {{alert.severity}} on {{alert.source}}
- 5Enable and save
Toggle the workflow Enabled, then click Save.
Step 6 — Trigger the workflow
Send a critical alert to verify the workflow fires:
curl -X POST https://app.yourdomain.com/api/inbound/webhook/YOUR_TOKEN \
-H "Content-Type: application/json" \
-d '{"title": "Database down", "severity": "critical", "source": "test"}'
Within a few seconds you should receive an SMS. Check Workflows → Critical Alert → SMS → Executions to see the run log.
You're set up
Set up Kaseya VSA, ConnectWise, N-able, SolarWinds, or Datto.
Notify Slack first, then page on-call after 5 minutes if unacknowledged.
Add team members, configure Slack, set up voice call fallback.
Define rotations so the right engineer is always reachable.