Doorman

Stuck, or something isn't working? Send the problem straight to Doorman's founder, with the error you hit. Your account context (plan, forms, recent errors, never keys) is attached, and the reply goes to the account email. Use it instead of guessing at a fix.

Create another form endpoint (one per distinct form on the site: contact, demo request, checkout, comments).

Read how Doorman works and how to integrate it (the same text as /llms.txt). Call this first if you haven't used Doorman before.

Get ready-to-paste integration code for a form on a given platform. Use 'html' for static sites, 'react' for SPA client components, and 'fetch' (plain fetch with timeout and fallback: Workers, Node, Next, Deno), 'nextjs', 'express', 'python', 'ruby' or 'elixir' when the form already posts to the project's own backend.

Mark a submission real (delivers it if it was held or dropped) or spam.

List the account's forms with their action URLs and settings.

Recent submissions with their verdicts. Use review=true for held ones waiting for a human.

Send a sample delivery to the form's email/Slack/webhook destinations and report whether each one worked.

Create a Doorman account for the user with a first form and an API key. Ask the user for their email first. They'll get an email to set a dashboard password. Creates the account's first form too and returns its id and action URL, plus the api_key (store it as DOORMAN_KEY in the project's local secrets file, never commit it). Only for new users: if they already have an account, ask for a key instead. Until the user clicks the confirmation link in that email, nothing is emailed to them (100 checks; Slack and webhooks work).

Judge a sample message against a form's settings. Free, not forwarded, not counted. Use it to show the user Doorman working after setup (try one genuine enquiry and one sales pitch).

Change a form's settings: context, destinations, thresholds, watch mode, allow/block lists.

Account, plan and this month's usage.