HTTP and Slack: Synthetic Login Flow Monitor Template
A scheduled synthetic check that walks a multi-step login flow and posts a Slack alert the moment any step returns an unexpected status.
What It Builds
A Schedule trigger fires on a fixed cadence and the http connector replays each step of your login flow in order: load the sign-in page, submit credentials, and fetch a page that only an authenticated session can reach. After every request a Condition node checks the returned status code, and if anything is off the slack connector posts the failing step, the URL, and the status to your on-call channel. When every step passes, the run stays silent.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every 5 minutes and walks our login flow step by step using HTTP requests: GET the sign-in page, POST the test credentials to the auth endpoint, then GET a page that requires a logged-in session. Check the status code after each request, and if any step returns an unexpected status, post a Slack message to #on-call naming which step failed, the URL, and the status code. Stay silent when all steps pass.Connectors Used
- Schedule trigger - runs the synthetic check on a fixed cron cadence.
- http - replays each login step and returns the status code for the Condition checks.
- slack - posts the failing step and status to your on-call channel.
Customize It
Change the interval (every 5 minutes), the Slack channel (#on-call), and the list of steps and their expected status codes. Add a step for any protected page, or have Spojit include response time so you also catch slow logins, not just failures.
Tips
- Use a dedicated test account so a flaky check never locks out real users.
- Keep each http step in Direct mode so requests run exactly as written, with no AI cost.
- If your auth endpoint returns a token, capture it from the POST response and pass it as a header on the protected-page request.