Workflows & webhooks

Frontier’s backend relies on a robust system for handling operations that don’t require immediate real-time processing. This includes background jobs, scheduled tasks, and inbound events, all designed to operate reliably and with built-in retry mechanisms, ensuring that critical workflows complete even if transient issues occur. This approach cleanly separates synchronous, latency-critical real-time operations from asynchronous, longer-running tasks.

Workflows (Inngest)

For all asynchronous, durable, and scheduled tasks, Frontier leverages Inngest, a serverless platform integrated directly into the Dashboard (a Next.js application). Inngest acts as the reliable async boundary, ensuring that events are queued, processed, and retried automatically upon failure, preventing data loss and providing fault tolerance for background operations. This is distinct from the synchronous, low-latency processing performed by the Call Server on the Cloudflare edge.

Inngest handles a wide array of durable jobs, including:

Onboarding: Orchestrates the initial setup for new organizations, including website scraping and manifest generation.
Knowledge Base Indexing: Processes uploaded documents, website crawls, and curated FAQs, indexing them into various retrieval backends like Cloudflare AI Search and Supermemory.
Call Summaries and Metrics: Post-call processing to generate summaries and derive metrics.
Calendar Synchronization: Periodically syncs calendar events.
System Upkeep: Various scheduled cleanup and maintenance tasks.
AI Search Reindex/Backfill: Ensures the knowledge base is current and consistent.
FAQ/Script Synchronization: Keeps curated content synchronized across retrieval systems.
User/Organization Lifecycle: Handles events related to user and organization changes.

Many of these Inngest functions are also configured as cron-scheduled jobs, ensuring regular execution for tasks like hourly calendar cleanups, daily bot cleanups, or frequent checks for stale heartbeats. All Inngest functions report to a centralized error-handler, which triggers on function failures to ensure prompt notification and management.

Webhooks

Webhooks serve as entry points for external systems to send event notifications to Frontier.

The most notable historical webhook was the Recall webhook ingress. This was part of a now legacy and deprecated integration where a cloud-based Recall bot would join a meeting and send events, including transcription data, to Frontier’s Dashboard via webhooks. These inbound webhooks were designed to be “hot-path-thin,” meaning they performed minimal validation before immediately forwarding the payload to Inngest for durable, asynchronous processing.