inbound Webhook Endpoint Provisioning (Delivery)
A sequence with 8 steps: Verify the client domain in the inbound dashboard by adding the MX records the vendor supplies.
By InnovaAI ResearchPublished
What are the steps?
inbound Webhook Endpoint Provisioning (Delivery)
- 01
Verify the client domain in the inbound dashboard by adding the MX records the vendor supplies
Domain verification must complete before any address on that domain can receive mail. Confirm the plan tier covers the domain count: Pro allows 50 domains, Growth allows 300, and Scale lists unlimited domains.
- 02
Generate a scoped API key for the client build
Keep one key per client so a revoked credential never touches another retainer. The REST API and TypeScript SDK both authenticate with this key.
- 03
Create the webhook endpoint and register its URL
Inbound delivers each inbound message as structured JSON containing headers, text, HTML, and attachments. Point the endpoint at the client's application or automation layer, not a shared agency listener.
- 04
Configure guard rules for address routing
Route named addresses such as support@ or billing@ to dedicated endpoints, and decide whether unmatched addresses fall through to catch-all. Higher plans add AI-evaluated rules for classification before routing.
- 05
Confirm threaded reply handling
Check that In-Reply-To and References headers survive parsing so replies land inside the original thread rather than spawning new conversations in the client's inbox.
- 06
Send test messages to every configured address
Fire one message per route plus one to an unmatched address to prove catch-all behaves as documented. Inspect the JSON payload for header, body, and attachment fidelity.
- 07
Hand the endpoint contract to the client's developer
Document the webhook URL, expected payload shape, and the API key rotation path. Inbound has no no-code UI for end clients, so the receiving side needs someone who can read the JSON and maintain the endpoint.
- 08
Record the mailbox and domain counts against the plan ceiling
Log current usage beside the tier limit so the next retainer renewal flags an upgrade before inbound starts rejecting mail. The entry tier covers 5,000 emails per month at $4 monthly.
More on inbound
- StrategyWhy inbound Turns Email Into Agency Retainer Infrastructure
- Evaluation RuleWhen to Adopt inbound: Client Inboxes Exceed 5,000 Emails a Month
- Decision Frameworkinbound: Buy vs Skip (Email-Integrated Agency Delivery)
- Failure PatternThe inbound Catch-All Trap: Why Agencies Fail With inbound When Routing Rules Never Get Scoped
- Implementation Blueprintinbound Email Intake Sprint (5-7 days)