All documentation
Core ResourcesDashboard workflow

Email Processing

Connect an inbox and turn inbound customer messages into structured operational work.

1

How ingestion works

Email processing is configured as an authenticated workspace integration. Connected messages are normalized, classified, and linked to relevant work records before automation rules run.

  • Connect a supported mailbox from Dashboard → Integrations.
  • Choose which inbound messages Fortifiers should process.
  • Review extracted request context before downstream quote or task actions.
  • Use audit logs to trace automated processing.
2

Public API boundary

The inbound provider webhook is infrastructure-facing and is not a general-purpose public v1 endpoint. Do not post customer mail directly to internal email routes.

A dedicated, tenant-safe email ingestion API will be documented here if it becomes part of the public v1 contract.
3

Recommended custom integration

For custom intake today, send normalized request text to the quote-generation endpoint and retain the source message ID in your own system for traceability.

json
{
  "text": "Email from customer@example.com: Need an urgent repair to the loading dock door...",
  "industry": "commercial doors"
}
4

Privacy

Only forward the content required to scope the work. Avoid sending credentials, payment-card data, or unrelated message history.