Integrations Overview

Integrations are notification channels that Pingward uses to alert you when issues occur.

Available Integrations

Integration	Description
Email	Send alerts via SMTP
Slack	Post to Slack channels
Webhooks	Send to any HTTP endpoint
SMS	Text message alerts via Twilio

Creating an Integration

1. Go to Integrations in the sidebar
2. Click Add Integration
3. Select the integration type
4. Configure the settings
5. Click Test to verify it works
6. Save the integration

Routing Rules

Integrations don't receive alerts by default. You need to create routing rules to connect issues to integrations.

Creating a Routing Rule

1. Go to Routing Rules
2. Click New Rule
3. Configure conditions (optional):
   • Severity levels
   • Error categories
   • Specific tests
   • Tags
4. Add actions (integrations to notify)
5. Save the rule

Condition Types

Condition	Description
Severity	Match specific severity levels (Critical, High, etc.)
Error Categories	Match specific error types (Timeout, ServerError, etc.)
Tests	Match specific tests by ID
Tags	Match tests with specific tags

Examples

Page on-call for critical issues:

Conditions: Severity = Critical
Actions: PagerDuty Integration

Notify different teams by tag:

Conditions: Tags = payments
Actions: Slack #payments-team

Conditions: Tags = auth
Actions: Slack #identity-team

Default catch-all:

Conditions: (none)
Actions: Email to ops@company.com

Priority

Rules are evaluated in priority order. Higher priority rules are checked first. When a rule matches, its actions execute, but evaluation continues to check other rules.

Integration Status

Each integration shows:

• Last Used - When it last sent a notification
• Last Error - Any recent delivery failures
• Active - Whether it's enabled

Testing Integrations

Click Test on any integration to send a test notification. This helps verify:

• Credentials are correct
• Network access works
• The destination receives messages

Best Practices

Start Simple

Begin with one or two integrations:

1. Primary alert channel (Slack or email)
2. Escalation channel (PagerDuty or SMS)

Use Severity-Based Routing

Route by severity to avoid alert fatigue:

• Critical/High → Immediate channels (Slack, PagerDuty)
• Medium/Low → Batch channels (Email digest)

Test Before Deploying

Always test integrations before relying on them:

1. Create the integration
2. Click Test
3. Verify you received the test notification
4. Create routing rules

Monitor Integration Health

Check the integrations page regularly:

• Look for delivery errors
• Verify last-used timestamps
• Disable unused integrations