[{"data":1,"prerenderedAt":12},["ShallowReactive",2],{"$f05sKliUl-X07RZjhM18SWq2D0ZtnYkY3bEpyVzrAVOw":3},{"title":4,"slug":5,"excerpt":6,"category":7,"order":8,"screens":9,"html":11},"Testing webhooks with WebhookTest","webhooktest-integration","Test your email-to-webhook flows instantly with integrated WebhookTest.eu","integrations",2,[10],"webhooks","\u003Cp>WebhookTest is seamlessly integrated into EmailConnect, making it incredibly easy to test your email-to-webhook flows without switching between services or setting up external endpoints.\u003C\u002Fp>\n\u003Ch2>What is WebhookTest?\u003C\u002Fh2>\n\u003Cp>WebhookTest (webhooktest.eu) is a free service that provides instant webhook endpoints for testing. When integrated with EmailConnect, it allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>See webhook payloads in real-time\u003C\u002Fli>\n\u003Cli>Test different response scenarios\u003C\u002Fli>\n\u003Cli>Debug your email processing logic\u003C\u002Fli>\n\u003Cli>Validate data before connecting to production systems\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Quick start\u003C\u002Fh2>\n\u003Ch3>Step 1: Create a test webhook\u003C\u002Fh3>\n\u003Col>\n\u003Cli>In your EmailConnect dashboard, go to any alias\u003C\u002Fli>\n\u003Cli>Click "Add webhook"\u003C\u002Fli>\n\u003Cli>Click the "Use WebhookTest" button\u003C\u002Fli>\n\u003Cli>A unique test endpoint is automatically generated (e.g., \u003Ccode>https:\u002F\u002Fwebhooktest.eu\u002Fu\u002Fabc123\u003C\u002Fcode>)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 2: Send a test email\u003C\u002Fh3>\n\u003Cp>Send an email to your configured alias. Within seconds, you'll see:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The complete JSON payload in WebhookTest\u003C\u002Fli>\n\u003Cli>Response status and headers\u003C\u002Fli>\n\u003Cli>Processing time and metadata\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Step 3: Iterate and refine\u003C\u002Fh3>\n\u003Cp>Make adjustments to your webhook configuration and test again instantly. No deployment needed!\u003C\u002Fp>\n\u003Ch2>Advanced testing scenarios\u003C\u002Fh2>\n\u003Ch3>Testing error handling\u003C\u002Fh3>\n\u003Cp>Use custom headers to simulate different response codes:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Header: X-Mock-Status\nValue: 500\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will make WebhookTest return a 500 error, allowing you to test your retry logic.\u003C\u002Fp>\n\u003Ch3>Testing timeouts\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>Header: X-Mock-Delay\nValue: 5000\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Delays the response by 5 seconds to test timeout handling.\u003C\u002Fp>\n\u003Ch3>Testing different content types\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>Header: X-Mock-Content-Type\nValue: application\u002Fxml\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Tests how your system handles non-JSON responses.\u003C\u002Fp>\n\u003Ch2>Real-world workflow\u003C\u002Fh2>\n\u003Ch3>Development phase\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Create alias with WebhookTest endpoint\u003C\u002Fli>\n\u003Cli>Send test emails with various formats\u003C\u002Fli>\n\u003Cli>Verify the JSON structure matches your expectations\u003C\u002Fli>\n\u003Cli>Test edge cases (large attachments, special characters, etc.)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Integration phase\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Keep WebhookTest as a secondary webhook\u003C\u002Fli>\n\u003Cli>Add your production endpoint as primary\u003C\u002Fli>\n\u003Cli>Compare responses between test and production\u003C\u002Fli>\n\u003Cli>Remove WebhookTest when confident\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Debugging production issues\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Temporarily add WebhookTest alongside your production webhook\u003C\u002Fli>\n\u003Cli>Capture real-world payloads\u003C\u002Fli>\n\u003Cli>Diagnose issues without affecting production\u003C\u002Fli>\n\u003Cli>Remove when resolved\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Ch3>Use descriptive webhook names\u003C\u002Fh3>\n\u003Cp>When creating webhooks, use names like:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>"WebhookTest - Development"\u003C\u002Fli>\n\u003Cli>"WebhookTest - Debugging Production Issue #123"\u003C\u002Fli>\n\u003Cli>"WebhookTest - Testing Attachments"\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Leverage webhook groups\u003C\u002Fh3>\n\u003Cp>Create separate webhook configurations for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Development (WebhookTest only)\u003C\u002Fli>\n\u003Cli>Staging (WebhookTest + staging endpoint)\u003C\u002Fli>\n\u003Cli>Production (production endpoint only)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Document test scenarios\u003C\u002Fh3>\n\u003Cp>Keep track of test emails and expected outcomes:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Test: Large attachment handling\nEmail: test-attachment@in.myapp.com\nAttachment: 10MB PDF\nExpected: Base64 encoded in payload\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>Tips and tricks\u003C\u002Fh2>\n\u003Ch3>1. Bookmark your test endpoints\u003C\u002Fh3>\n\u003Cp>WebhookTest URLs are permanent. Bookmark them for quick access.\u003C\u002Fp>\n\u003Ch3>2. Use the WebhookTest dashboard\u003C\u002Fh3>\n\u003Cp>Visit your WebhookTest URL in a browser to see a full history of requests.\u003C\u002Fp>\n\u003Ch3>3. Test webhook signatures\u003C\u002Fh3>\n\u003Cp>If using webhook signatures, WebhookTest shows the exact headers received, making it easy to verify your Standard Webhooks signature calculations.\u003C\u002Fp>\n\u003Ch3>4. Mobile testing\u003C\u002Fh3>\n\u003Cp>WebhookTest works great on mobile devices. Test your email flows from anywhere.\u003C\u002Fp>\n\u003Ch2>Common testing patterns\u003C\u002Fh2>\n\u003Ch3>Testing email parsing\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>Subject: Order #12345\nBody: Please process this order urgently\n\nExpected webhook payload:\n{\n  "message": {\n    "date": "2026-02-12T10:30:00.000Z",\n    "sender": {\n      "name": "Test Sender",\n      "email": "test@webhooktest.com"\n    },\n    "content": {\n      "text": "This is a test email sent via WebhookTest.",\n      "html": "<p>This is a test email sent via WebhookTest.<\u002Fp>",\n      "links": []\n    },\n    "subject": "WebhookTest - Test Email",\n    "recipient": {\n      "name": null,\n      "email": "test@yourdomain.com"\n    },\n    "attachments": []\n  },\n  "classification": {\n    "type": "normal"\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Depending on your plan, webhook payloads may also include additional fields: \u003Ccode>spam\u003C\u002Fcode> analysis (Maker+), \u003Ccode>security\u003C\u002Fcode> virus scanning (Business+), \u003Ccode>integrity\u003C\u002Fcode> hashes (Maker+), \u003Ccode>classification\u003C\u002Fcode> signals and confidence (Maker+), and \u003Ccode>markdown\u003C\u002Fcode> content conversion (Maker+). See the \u003Ca href=\"\u002Fhelp\u002Fwebhook-payload-reference\u002F\">Webhook payload reference\u003C\u002Fa> for full details.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Tip:\u003C\u002Fstrong> Business+ users can send the \u003Ca href=\"https:\u002F\u002Fwww.eicar.org\u002F\">EICAR test file\u003C\u002Fa> as an attachment to test how their endpoint handles virus-detected attachments. The attachment will be flagged with \u003Ccode>excluded: true\u003C\u002Fcode> and \u003Ccode>excludeReason: "virus-detected"\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Testing attachment handling\u003C\u002Fh3>\n\u003Cp>Send emails with various attachment types and verify they appear correctly in the webhook payload.\u003C\u002Fp>\n\u003Ch3>Testing retry logic\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Set X-Mock-Status: 500\u003C\u002Fli>\n\u003Cli>Verify EmailConnect retries the webhook\u003C\u002Fli>\n\u003Cli>Change to X-Mock-Status: 200\u003C\u002Fli>\n\u003Cli>Confirm successful delivery\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Retries are capped by your data retention policy. Free and Maker plans (1-hour retention) get up to 4 attempts before the email is abandoned. Use a Business or Platform plan with longer retention to test the full 6-attempt backoff sequence.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2>Replaying and retrying deliveries\u003C\u002Fh2>\n\u003Cp>Paid plans can replay successful webhook deliveries or retry failed ones directly from the \u003Cstrong>Logs\u003C\u002Fstrong> view in the dashboard.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Replay\u003C\u002Fstrong>: Re-delivers a previously successful webhook payload to your endpoint. Useful for re-testing after code changes without resending the original email.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retry\u003C\u002Fstrong>: Re-attempts delivery for failed webhooks. Helpful when your endpoint was temporarily down.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This eliminates the need to resend test emails when debugging endpoint changes.\u003C\u002Fp>\n\u003Cp>WebhookTest integration removes the friction from testing email automation flows, letting you focus on building great features instead of debugging infrastructure.\u003C\u002Fp>\n",1781207682109]