integrate a custom (non-Application) channel into Front via the Channels API
domain: front.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a custom channel in Front settings and note its Incoming URL under the channel's API Endpoints section
POST inbound messages to that Incoming URL matching the Receive Custom Messages endpoint's expected payload shape
Handle the response, which returns a status of accepted and a message_uid you can use to fetch the created message or conversation
Configure the channel's outgoing webhook so replies composed in Front are POSTed back to your system
Tag, assign, and route the resulting conversations using Front's standard conversation rules once messages land in the channel
Consider an Application Channel instead if you intend to distribute the integration to other Front customers, since custom channels are single-instance and feature-limited
Known gotchas
Custom channels are explicitly positioned as legacy/maintenance-mode — Application Channels are recommended for anything beyond a single internal integration
The custom channel only synchronizes messages you explicitly POST to it; there is no automatic polling or discovery from your source system
Custom channels are scoped to your own Front instance only and cannot be published for other Front customers to install
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?