Campaign probe for message quality and launch readiness

Probe campaign quality with dedicated inbox workflows

Use MailSlurp campaign probe workflows to detect broken links, missing assets, template drift, and sender-readiness issues with repeatable inbox checks instead of manual spot reviews.

Start free Probe docs

Trusted by top companies worldwide

Product features

Campaign probe capabilities built for recurring message QA

Use seeded probe mailboxes, scheduled analysis, durable health state, and run history to keep campaign quality visible over time.

Dedicated probe addresses for each campaign or stream

Give every campaign, lifecycle sequence, or sender its own probe mailbox identity so copies land in a controlled destination instead of scattered spot-check inboxes.

Explore

Scheduled probe runs with latest health state

Keep recurring checks active and review the last known score and run status for each monitored campaign without re-creating one-shot audits.

Explore

Structural checks across links, images, HTML, compatibility, and reputation

Every probe run can score the message for broken links, missing images, HTML issues, client-compatibility warnings, and stored reputation verdict failures.

Explore

Run comparisons and trend history for regression review

Compare the latest run against an earlier healthy baseline and use trend views to see when message quality started to slip.

Explore

MailSlurp product workspace showing email, phone, dashboard activity, and developer automation

Probe links, assets, and content continuously

Keep dedicated inboxes watching campaign and notification quality before or after launch instead of depending on one-time review.

Explore email audit

Push probe results into teams and systems automatically

Send failures and quality signals into webhooks, queues, or internal dashboards so fixes reach owners faster.

Explore webhooks

Pair launch probes with sender health monitoring

Combine content evidence with domain and authentication checks for a tighter release-readiness workflow.

Explore reliability

TSserver.ts

// example express server that you control
const app = express();
app.use(bodyParser.json());
// receive new email webhook payload via post
app.post('/new-email-endpoint', async (request, response) => {
  // can use typescript types
  const payload = request.body as WebhookNewEmailPayload;

  // do something with with email id
  expect(payload.emailId).toBeTruthy();

  // return a 2xx status code so MailSlurp knows you received it
  return response.sendStatus(200);
});
const server = app.listen(port);

Automate domain checks, alerts, and message signals with APIs

Move sender posture checks and reliability events into scheduled jobs, dashboards, or alert pipelines with the same API.

Open docs

TSserver.ts

// example express server that you control
const app = express();
app.use(bodyParser.json());
// receive new email webhook payload via post
app.post('/new-email-endpoint', async (request, response) => {
  // can use typescript types
  const payload = request.body as WebhookNewEmailPayload;

  // do something with with email id
  expect(payload.emailId).toBeTruthy();

  // return a 2xx status code so MailSlurp knows you received it
  return response.sendStatus(200);
});
const server = app.listen(port);