Connect Statusfield with your favorite tools and services

Integrations

Emails

Quick Start Guide

Statusfield helps you monitor the uptime and availability of critical online services. Get instant notifications when your monitored services experience issues.

<CardGroup cols={2}>
  <Card
    icon='🚀'
    title='Quick Start'
    description='Get up and running with Statusfield in minutes'
    href='/docs/quickstart'
  />
  <Card
    icon='🔌'
    title='Integrations'
    description='Connect with Slack, email, webhooks, and more'
    href='/docs/integrations'
  />
</CardGroup>

Key Features

- Real-time Monitoring: Track 2000+ services across major providers
- Smart Notifications: Get alerted via Email, Slack, Discord, or Webhooks
- Status History: View detailed incident timelines and component status
  {/ - API Access: Programmatic access to service status data /}

<Callout variant='info' title='Free Plan Available'>
  Start monitoring for free. No credit card required.
</Callout>

What You Can Monitor

Statusfield tracks services from major providers including:

- Cloud providers (AWS, Google Cloud, Azure)
- Developer tools (GitHub, GitLab, Vercel)
- Communication platforms (Slack, Discord, Zoom)
- And 2000+ more services

Getting Help

Need assistance? We're here to help:

- Check out our Quick Start Guide
- Explore Integrations
- Contact support via the in-app chat

Learn how to use Statusfield to monitor your critical services and get notified when things go wrong.

Documentation

Get instant notifications in your Discord channels when monitored services experience issues. Color-coded embeds make it easy to spot the severity at a glance.

<Callout variant='info' title='Paid Plan Required'>
  Discord notifications are available on the Hobby, Startup, and Pro plans.
  Upgrade your plan to get started.
</Callout>

Quick Start

<Steps>
  <Step title="Create a Discord Webhook">
    In your Discord server:
    1. Right-click the channel where you want notifications
    2. Select Edit Channel
    3. Go to Integrations > Webhooks
    4. Click New Webhook
    5. Name it "Statusfield" (optional)
    6. Click Copy Webhook URL

    <Callout variant="info" title="Permissions">
    You need Manage Webhooks permission in the Discord channel to create a webhook.
    </Callout>

  </Step>

  <Step title="Add Webhook to Statusfield">
    1. Go to statusfield.com/integrations
    2. Click the Discord card
    3. Click Add Discord Integration
    4. Enter a name (e.g., "#incidents", "DevOps Alerts")
    5. Paste the Discord webhook URL
    6. Click Add Discord

  </Step>

  <Step title="Test It Out">
    1. Click the menu (⋮) next to your Discord integration
    2. Select Test Notification
    3. Check that the test message appears in your Discord channel

  </Step>

  <Step title="Configure Notifications">
    When adding a monitor for a service:
    1. Go to statusfield.com/notifications
    2. Find the service in the list
    3. Configure when you want to receive notifications (status by column)
      - On any status change
      - On maintenance status
      - On degraded status
      - On major outage status
      - On partial outage status

    All statuses will notify you when the component went back to operational status.

  </Step>

</Steps>

Discord Message Format

Notifications appear as rich embeds in your Discord channel with color-coded borders:

- 🟢 Green — Operational
- 🟡 Yellow — Degraded
- 🟠 Orange — Partial Outage
- 🔴 Red — Major Outage
- ⚪ Gray — Maintenance

Each embed includes:

- Title — Service name and status change (e.g., "GitHub — Status Changed")
- Description — What changed (e.g., "API Requests is now Degraded")
- Current Status — The new status
- Previous Status — What the status was before the change
- Affected Components — List of impacted components (if applicable)
- Timestamp — When the change occurred
- Link — Click the embed title to view the service on Statusfield

Managing Discord Integrations

Add Multiple Channels

You can add multiple Discord webhooks (up to your plan limit) for:

- Different Discord servers
- Separate channels for different severity levels
- Team-specific alert channels

Each Discord integration can be configured independently for different services and notification levels.

Edit or Remove

1. Open statusfield.com/integrations > Discord
2. Click the menu (⋮) next to the integration
3. Select Edit to update the name or webhook URL
4. Select Delete to remove the integration

<Callout variant='warning' title='Warning'>
  Deleting a Discord integration removes all associated notification rules. This
  cannot be undone.
</Callout>

Troubleshooting

<Callout variant="warning" title="Not Receiving Discord Notifications?">
Common issues and solutions:

1. Webhook Was Deleted in Discord

- If someone deletes the webhook in Discord settings, notifications will fail silently
- Create a new webhook in Discord and update the URL in Statusfield

2. Channel Was Deleted or Archived

- Discord webhooks stop working if the target channel is removed
- Create a new webhook in an active channel

3. Webhook URL Is Invalid

- Discord webhook URLs must match the format: https://discord.com/api/webhooks/...
- Make sure you copied the full URL from Discord

4. Rate Limits

- Discord has rate limits on webhook messages
- If you're monitoring many services with frequent status changes, some messages may be delayed

</Callout>

Security & Privacy

- Webhook URLs are encrypted in our database
- All communication with Discord uses HTTPS
- We only send messages — we never read your Discord messages, channels, or user data
- No Discord bot is installed in your server

<Callout variant='info' title='Need Help?'>
  Contact our support team at
  support@statusfield.com
</Callout>

Send service status notifications to your Discord channels

Discord

Email is the primary notification method for Statusfield. Receive instant, reliable alerts when your monitored services experience issues, directly to your inbox.

<Callout variant='success' title='Default Email Address'>
  Your sign up email address is automatically added as an email address for
  notifications and used as your default email address for notifications for
  each new monitor you add. You can change the monitor's notification channels
  in statusfield.com/notifications
</Callout>

Quick Start

<Steps>
  <Step title="Add an Email Address">
    1. Go to statusfield.com/integrations
    2. Click the Email card
    3. Click Add Email Address
    4. Enter a name (e.g., "Personal", "Team Lead") and email address
    5. Click Add Email
  </Step>

  <Step title="Verify Your Email">
    Check your inbox for a verification email from noreply@send.statusfield.com. Click the verification link to activate notifications.

    <Callout variant="warning" title="Verification Required">
    Email notifications won't be sent until you verify your email address. The verification link expires after 24 hours.
    </Callout>

  </Step>

  <Step title="Test Your Setup">
    1. Click the menu (⋮) next to your email integration
    2. Select Test Email
    3. Check that the test message appears in your email inbox

  </Step>

  <Step title="Configure Notifications">
    When adding a monitor for a service:
    1. Go to statusfield.com/notifications
    2. Find the service in the list
    3. Configure when you want to receive notifications (status by column)
      - On any status change
      - On maintenance status
      - On degraded status
      - On major outage status
      - On partial outage status

    All statuses will notify you when the component went back to operational status.

  </Step>

</Steps>

Email Contents

Each notification email includes:

- Subject line - Service name and current status (e.g., "GitHub - Partial Outage")
- Service details - Which service and components are affected
- Status information - Current status with severity level
- Affected components - Complete list of impacted components
- Link - Button linking to full incident details on Statusfield

Managing Email Addresses

Add Multiple Emails

You can add multiple email addresses (up to your plan limit) for:

- Personal backup addresses
- Team distribution (e.g., "DevOps Team", "On-Call Engineer")
- Different departments
- External stakeholders

Each email can be configured independently for different services and notification levels.

<Callout variant='warning' title='Note'>
  Your default email (account email) cannot be edited or removed from
  integrations.
</Callout>

Troubleshooting Delivery

<Callout variant="warning" title="Not Receiving Emails?">
Common issues and solutions:

1. Check Spam Folder

- Look for emails from @send.statusfield.com
- Mark as "Not Spam" and add to safe senders

2. Verify Email Status

- Go to statusfield.com/integrations > Email
- Look for "Pending" badge > click (⋮) > Resend Verification

3. Corporate Email Filters

- Some organizations may delay delivery due to spam filters. Wait a few minutes and check your spam/junk folder.
- Some organizations (especially with Mimecast, Proofpoint) block automated emails
- Contact your IT department to whitelist send.statusfield.com
- Try adding a personal email (Gmail, Outlook) as backup

4. Email Forwarding Rules

- Check if you have filters that auto-archive or delete automated emails
- Ensure Statusfield emails aren't being automatically filtered

5. Inbox Full

- If your mailbox is full, you won't receive new emails
- Clear space and try sending a test email

</Callout>

<Callout variant='info' title='Need Help?'>
  Contact our support team at
  support@statusfield.com
</Callout>

Statusfield integrates with your existing workflow to deliver notifications where you need them. Choose from multiple notification channels and combine them for comprehensive coverage.

Available Integrations

<CardGroup cols={2}>
  <Card
    title='Email Notifications'
    description='Receive instant email alerts when services go down'
    href='/docs/integrations/email'
  />
  <Card
    title='Slack'
    description='Get notifications in your Slack channels'
    href='/docs/integrations/slack'
  />
  <Card
    title='Discord'
    description='Send notifications to your Discord channels'
    href='/docs/integrations/discord'
  />
  <Card
    title='Webhooks'
    description='Send custom HTTP requests when status changes'
    href='/docs/integrations/webhooks'
  />
  <Card
    title='API Access'
    description='Coming soon - Programmatic access to service status data'
    disabled
  />
  <Card
    title='MCP Server'
    description='Coming soon - Model Context Protocol for AI assistants'
    disabled
  />
</CardGroup>

Multiple Notification Channels

You can enable multiple integrations simultaneously. For example:

- Email for critical alerts
- Slack for team visibility
- Webhooks for automation

<Callout variant='info' title='Smart Notifications'>
  Statusfield only sends notifications when service status changes, preventing
  alert fatigue from duplicate notifications.
</Callout>

Integration Features

All integrations support:

- Real-time delivery - Notifications sent within seconds
- Status updates - Get notified when issues are resolved
- Component details - See which specific components are affected

Advanced Automation with Webhooks

Webhooks open up powerful automation possibilities:

- Integrate with custom tools and internal systems
- Trigger automation workflows via Zapier, Make, or n8n
- Build custom dashboards with real-time status data
- Connect to ITSM platforms like PagerDuty or ServiceNow

Learn more about webhooks →

Get instant notifications in your Slack workspace when monitored services experience issues. Perfect for keeping your team informed in real-time with collaborative incident response.

Overview

Statusfield supports two types of Slack integration:

1. OAuth Channels (Recommended) - Connect your Slack workspace and select channels from a list
2. Incoming Webhooks - Use Slack webhook URLs for simple one-way notifications

<Callout variant='info' title='Which Method Should I Use?'>
  OAuth is recommended for most users - it's easier to set up, more
  reliable, and allows you to pick channels from a list. Use webhooks only if
  you need to send notifications to external Slack workspaces you don't control.
</Callout>

Quick Start: OAuth Channels

<Steps>
  <Step title="Connect Your Slack Workspace">
    1. Go to statusfield.com/integrations
    2. Click the Slack card
    3. Click Connect Slack button
    4. Select your Slack workspace
    5. Click Allow to grant Statusfield permissions

    <Callout variant="info" title="Permissions">
    Statusfield requests permission to:
    - View channel names and topics
    - Post messages to channels you select
    - No access to message history or DMs
    </Callout>

  </Step>

  <Step title="Add a Channel">
    After connecting:
    1. Click Add Slack Integration button in the manage drawer
    2. Select "Add Channel" option
    3. Select desired channel from the list
    4. Click Add Channel button
    5. You can edit the channel name later in the manage drawer

    You can add multiple channels and configure each one independently.

  </Step>

  <Step title="Test It Out">
    1. Click the menu (⋮) next to your Slack integration
    2. Select Test Notification
    3. Check that the test message appears in your Slack channel

  </Step>

  <Step title="Configure Notifications">
    When adding a monitor for a service:
    1. Go to statusfield.com/notifications
    2. Find the service in the list
    3. Configure when you want to receive notifications (status by column)
      - On any status change
      - On maintenance status
      - On degraded status
      - On major outage status
      - On partial outage status

    All statuses will notify you when the component went back to operational status.

  </Step>

</Steps>

Quick Start: Slack Webhooks

<Steps>
  <Step title="Create a Slack Webhook">
    In your Slack workspace:
    1. Go to https://api.slack.com/apps
    2. Click Create New App > From scratch
    3. Name it "Statusfield" and select your workspace
    4. Navigate to Slack Features > Incoming Webhooks and toggle it on
    5. Click Add New Webhook
    6. Select the channel
    7. Copy the webhook URL (starts with https://hooks.slack.com/...)
  </Step>

  <Step title="Add Webhook to Statusfield">
    1. Go to statusfield.com/integrations
    2. Click the Slack card
    3. Click Add Slack Integration button
    4. Select "Slack Webhook" option
    5. Enter a name (e.g., "#engineering-alerts")
    6. Paste the webhook URL
    7. Click Add Webhook button

  </Step>

  <Step title="Test It Out">
    1. Click the menu (⋮) next to your Slack integration
    2. Select Test Notification
    3. Check that the test message appears in your Slack channel

  </Step>

</Steps>

Slack Message Format

Each Slack notification includes:

- Service name - Clear identification (e.g., "🔴 GitHub")
- Status level - Current status with emoji indicator
  - 🟢 Operational
  - 🟡 Degraded
  - 🟠 Partial Outage
  - 🔴 Major Outage
  - 🔵 Maintenance
- Affected components - List of impacted components
- Timestamp - When the incident started
- Link - Button linking to full incident details on Statusfield

Managing OAuth Connections

View Connected Workspace

In the Slack integrations drawer, you'll see:

- Connected workspace name (e.g., "Connected to Acme Corp workspace")

Disconnect Workspace

To disconnect your Slack workspace:

1. Open statusfield.com/integrations > Slack
2. Click Disconnect next to the connected workspace
3. Confirm the action

<Callout variant='warning' title='Warning'>
  Disconnecting removes all OAuth channels and their notification rules.
  Everything is deleted. Webhooks are not affected.
</Callout>

Reconnect After Disconnection

If you disconnected or revoked access:

1. Click Connect Slack again
2. Authorize the workspace
3. Re-add your channels

Your previous notification configuration won't be restored automatically.

Troubleshooting

<Callout variant="warning" title="Not Receiving Slack Notifications?">
  Common issues and solutions:

1. OAuth Connection Expired

- Go to statusfield.com/integrations > Slack
- Click Connect Slack button
- Reauthorize the workspace

</Callout>

Security & Privacy

Permissions

Statusfield's Slack app requests minimal permissions:

- channels:read - View public channel names
- groups:read - View private channel names (if invited)
- chat:write - Post messages to selected channels
- chat:write.public - Post to public channels without invitation

We never access:

- Message history or content
- Direct messages
- User information
- Files or attachments

Data Protection

- OAuth tokens are encrypted in our database
- Tokens are only used to post notifications, nothing else
- Webhook URLs are stored securely
- All Slack API calls use HTTPS

<Callout variant='info' title='Need Help?'>
  Contact our support team at
  support@statusfield.com
</Callout>

Receive service status notifications in your Slack workspace

Slack

Webhooks let you send HTTP requests to any endpoint when a monitored service changes status. Use them to trigger automations, update dashboards, create tickets, or integrate with any tool that accepts HTTP requests.

<Callout variant='info' title='Paid Plan Required'>
  Webhooks are available on the Hobby, Startup, and Pro plans. Upgrade your
  plan to get started.
</Callout>

Quick Start

<Steps>
  <Step title="Add a Webhook">
    1. Go to statusfield.com/integrations
    2. Click the Webhooks card
    3. Click Add Webhook
    4. Enter a name (e.g., "PagerDuty", "Jira Automation")
    5. Enter the webhook URL (must be HTTPS)
    6. Select the HTTP method (POST, GET, PUT, PATCH, or DELETE)
    7. Optionally configure authentication and custom headers
    8. Click Add Webhook

    <Callout variant="warning" title="HTTPS Required">
    Webhook URLs must use HTTPS. HTTP URLs are not accepted for security reasons.
    </Callout>

  </Step>

  <Step title="Configure Authentication (Optional)">
    If your endpoint requires authentication, select one:

    - None — No authentication header sent
    - Bearer Token — Sends Authorization: Bearer <your-token> header
    - Basic Auth — Sends Authorization: Basic <your-credentials> header

    Your authentication credentials are encrypted and stored securely.

  </Step>

  <Step title="Add Custom Headers (Optional)">
    You can add custom HTTP headers in JSON format:

    

  </Step>

  <Step title="Test It Out">
    1. Click the menu (⋮) next to your webhook integration
    2. Select Test Webhook
    3. Verify that your endpoint received the test request

  </Step>

  <Step title="Configure Notifications">
    When adding a monitor for a service:
    1. Go to statusfield.com/notifications
    2. Find the service in the list
    3. Configure when you want to receive notifications (status by column)
      - On any status change
      - On maintenance status
      - On degraded status
      - On major outage status
      - On partial outage status

    All statuses will notify you when the component went back to operational status.

  </Step>

</Steps>

Webhook Payload

When a status change occurs, Statusfield sends a JSON payload to your endpoint. Here's the full structure:

Payload Fields

| Field                    | Description                                                            |
| ------------------------ | ---------------------------------------------------------------------- |
| id                     | Unique delivery identifier                                             |
| event                  | Always "statuschange"                                               |
| level                  | "service" for top-level changes, "component" for component changes |
| service                | Service name, slug, and last check time                                |
| component              | Affected component with current and previous status                    |
| affectedComponents     | Array of child components that changed                                 |
| statusChange.direction | "worsening", "improving", or "unchanged"                         |
| statusChange.timestamp | ISO 8601 timestamp of the change                                       |
| url                    | Link to the service page on Statusfield                                |

Status Codes

| Status Code      | Human-Readable |
| ---------------- | -------------- |
| OPERATIONAL    | Operational    |
| DEGRADED       | Degraded       |
| PARTIALOUTAGE | Partial Outage |
| MAJOR_OUTAGE   | Major Outage   |
| MAINTENANCE    | Maintenance    |
| UNKNOWN        | Unknown        |

HTTP Methods

Choose the HTTP method that matches your endpoint:

- POST (default) — Standard for webhook receivers. Payload sent as JSON body.
- PUT — Payload sent as JSON body.
- PATCH — Payload sent as JSON body.
- GET — No request body sent. Use for simple ping-style endpoints.
- DELETE — No request body sent.

<Callout variant='info' title='Content-Type'>
  For POST, PUT, and PATCH requests, the payload is sent as application/json.
</Callout>

Delivery & Retries

- Notifications are sent within seconds of a status change
- Failed deliveries are retried up to 3 times with increasing delays
- Your endpoint should respond with a 2xx status code to confirm receipt
- Requests time out after 10 seconds
- HTTP redirects are not followed for security reasons

Use Cases

Webhooks are flexible enough for many integrations:

- Incident management — Create tickets in PagerDuty, Opsgenie, or ServiceNow
- Project management — Post to Jira, Linear, or Asana when services go down
- Custom dashboards — Feed status data into Grafana or Datadog
- Automation — Trigger Zapier, Make, or n8n workflows
- Internal tools — Update your own systems with real-time status data
- Chat tools — Send to Microsoft Teams, Telegram, or any chat with an incoming webhook

Managing Webhooks

Edit or Remove

1. Open statusfield.com/integrations > Webhooks
2. Click the menu (⋮) next to the integration
3. Select Edit to update the URL, method, authentication, or headers
4. Select Delete to remove the integration

<Callout variant='warning' title='Warning'>
  Deleting a webhook integration removes all associated notification rules. This
  cannot be undone.
</Callout>

Troubleshooting

<Callout variant="warning" title="Not Receiving Webhook Notifications?">
Common issues and solutions:

1. Endpoint Returns Non-2xx Status

- Your endpoint must return a 2xx status code (e.g., 200, 201, 204)
- Check your server logs for errors
- Verify the endpoint is accessible from the internet

2. HTTPS Certificate Issues

- Ensure your SSL certificate is valid and not expired
- Self-signed certificates may cause delivery failures

3. Authentication Errors

- Verify your Bearer token or Basic Auth credentials are correct
- Check that the authentication method matches what your endpoint expects

4. Timeout

- Webhook requests time out after 10 seconds
- Make sure your endpoint responds quickly — process the payload asynchronously if needed

5. Firewall or IP Restrictions

- Ensure your endpoint accepts requests from external sources
- Webhook requests originate from Cloudflare's IP ranges

</Callout>

Security

- All webhook URLs must use HTTPS
- Authentication credentials are encrypted in our database
- Custom headers are encrypted in our database
- HTTP redirects are rejected to prevent URL hijacking
- Each delivery has a unique id for deduplication

<Callout variant='info' title='Need Help?'>
  Contact our support team at
  support@statusfield.com
</Callout>

Send custom HTTP requests when service status changes

Webhooks

Get up and running with Statusfield in under 5 minutes. This guide will walk you through creating your account, adding your first monitor, and setting up notifications.

Prerequisites

All you need is an email address or a GitHub/Google account to get started.

<Steps>
  <Step title="Create Your Account">
    Visit statusfield.com/sign-up and sign up using one of the following methods:
    - Email (magic link)
    - GitHub OAuth
    - Google OAuth

    No credit card required.

  </Step>

  <Step title="Add Your First Monitor">
    Once logged in:
    1. Visit statusfield.com/services
    2. Search for a service (e.g., "GitHub", "AWS")
    3. Select the service you want to monitor
    4. Click "Monitor" in the top right corner of the service page
  </Step>
</Steps>

- You'll now receive alerts when the service is experiencing issues to the email address you used to sign up.
- You can also add additional email addresses to your account to share alerts with your team or use other notification methods like Slack or Webhooks.
- You can add more integrations in the statusfield.com/integrations page and manage how you receive alerts in statusfield.com/notifications.

<Callout variant='success' title="You're All Set!">
  You're now monitoring critical services. Statusfield will notify you
  immediately when issues are detected.
</Callout>

Understanding Status Levels

Statusfield tracks five status levels:

- Operational - Service is working normally
- Degraded - Service is slow or experiencing minor issues
- Partial Outage - Some components are down
- Major Outage - Significant service disruption
- Maintenance - Scheduled maintenance

Upgrading Your Plan

Ready for more monitors? Check out our plans:

<PlansInfo />

Visit your account page to upgrade your plan.

Get started with Statusfield in just a few minutes