Dashboard

Alert webhooks

Receive Mothership alerts in an automation service or your own application. Add or reuse a destination in the monitor’s settings. Email and every selected destination receive alerts separately.

Connect a service

Zapier

  1. Open the Mothership integration in Zapier and choose New alert.
  2. Connect your Mothership account, select a monitor and choose the action to run.
  3. Test and publish your Zap. Zapier manages the connection automatically.
  4. Alternatively, use Webhooks by Zapier → Catch Hook and paste its URL below. This alternative requires a paid Zapier plan.
Service instructions

Make

  1. In Mothership, choose Add recipient → Make → Connect Make to install the app in your organisation.
  2. Create a scenario with Mothership → New alert. Connect your account and select a saved monitor; Make registers the webhook automatically.
  3. Choose Run once, send a test alert from Mothership, then configure your actions and turn on the scenario.
  4. Alternatively, use Webhooks → Custom webhook and paste its URL into Mothership.
Service instructions

n8n

  1. In n8n, add a Webhook node and set HTTP Method to POST.
  2. Publish the workflow.
  3. Copy the Webhook node’s Production URL and paste it into the Webhook URL field below.
Service instructions

Pipedream

  1. For existing Pipedream Workflows accounts only. Workflows closes on 31 March 2027 and no longer accepts new signups.
  2. In your workflow, add an HTTP / Webhook trigger. Copy its endpoint URL and paste it below. Keep this URL private.
  3. Send a test alert from Mothership, map the incoming JSON body to your actions, then deploy the workflow. Use the event id to deduplicate retries.
Service instructions

Microsoft Teams

  1. Use Teams with your work or school account. In your channel, choose More options → Workflows → Send webhook alerts to a channel.
  2. Select your team and channel, and allow requests from Anyone. Save the workflow and paste its webhook link below. Keep this link private. Your organisation may require administrator approval.
  3. Send a test alert and confirm it appears in Teams. Add a co-owner so the workflow can continue if its owner leaves. Custom workflows must post the incoming text field.
Service instructions

Custom webhook format

Use a public HTTPS URL on port 443. Private network addresses, redirects and URLs containing a username or password are rejected. Custom authentication headers and custom payload templates are not supported. Treat a secret webhook URL like a password.

{
  "schema_version": 1,
  "id": "stable-check-event-id",
  "type": "monitor.alert",
  "monitor": {
    "id": "monitor-id",
    "name": "Competitor announcements",
    "url": "https://mothership.io/monitors/monitor-id"
  },
  "check": {
    "id": "check-id",
    "completed_at": "2026-10-16T00:00:00.000Z"
  },
  "alert": {
    "url": "https://mothership.io/alerts/18d01f17-bbee-4163-9b8a-d856ef4cc5c3"
  },
  "summary": "A matching announcement was found.",
  "matches": [
    {
      "fields": {
        "Title": "New product announcement",
        "URL": "https://example.com/announcement"
      },
      "reason": "Matches your alert criteria."
    }
  ]
}

Matching results include only the monitor’s configured output columns, with the reason each result matched. The payload is limited to 1 MB; oversized alerts fail visibly. Test alerts use type monitor.test, have no monitor or check ID, and contain no matching results. Every request includes Content-Type: application/json and an X-Mothership-Event-Id header.

Delivery and retries

Return a 2xx response within 10 seconds to acknowledge a request. Mothership retries temporary failures with increasing delays, up to five attempts within 24 hours. Most 4xx responses stop retries; timeouts and rate limits can retry. An interrupted request can be sent again, so deduplicate using the event id. Acceptance by a webhook does not confirm that downstream actions completed.

Use Send test alert to check the connection. The monitor event log shows accepted, pending, failed and skipped destination counts. Disabling or removing a connection stops subsequent sends. Removing a monitor or account removes its queued webhook deliveries.