ScribeTo API Health Check in n8n: HTTP Config & Sign-In

Get instant visibility into ScribeTo API health—without credentials

This n8n workflow performs an ScribeTo API Health Check by calling ScribeTo’s public configuration endpoint, verifying it’s responding correctly, and returning a simple sign-in/OTP status report—or failing fast with ScribeTo’s own error message.

What this workflow does

• Manual start: The workflow is triggered when you run it manually (you can later swap the manual trigger for a schedule if you want recurring monitoring).
• Checks ScribeTo’s public config endpoint: Sends an HTTP Request to https://scribeto.ai/api/config/public and parses the JSON response.
• Validates health: It considers the API healthy only when the response code equals 0.
• Outputs a health report when healthy: Provides a concise report including:
  • Service name
  • Website
  • Check timestamp
  • Whether email OTP, Google sign-in, and password reset are enabled
• Fails fast when unhealthy: If the response code is not 0, the workflow stops execution and raises an error containing the API’s response message.

Use cases

• Preflight checks for SaaS sign-in flows: Confirm ScribeTo sign-in and password reset features are available before enabling dependent features in your system.
• Operational monitoring for automation engineers: Quickly detect configuration/API issues affecting sign-in options.
• Environment verification: Optionally update the endpoint URL to monitor a different environment or future route changes.

Technical details

• n8n nodes: if, set, code, merge, sticky note, and HTTP Request
• External dependency: ScribeTo public configuration API (https://scribeto.ai/api/config/public)
• Credentials: None required (public endpoint only)
• Health rule: Response code must equal 0