build a Canvas Kit app for the Intercom Messenger or Inbox
domain: intercom.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register the app and choose Messenger Home, Conversation, Workflows, or Inbox conversation details as the surface
Implement an initialize endpoint that returns a Canvas response object containing the components to render
Choose between a static canvas (next request only on user action) and a live canvas (content_url refreshed whenever viewed)
Handle the submit/component-action webhook Intercom POSTs on user interaction, returning an updated Canvas object
Respect the Messenger- and Inbox-specific component and sizing best practices, since the two surfaces differ
Test the app inside a live workspace conversation before publishing it to the App Store
Known gotchas
Messenger and Inbox use different request/response shapes for canvases — a canvas built for Inbox won't render correctly in Messenger without adjustment
Live canvases re-fetch content_url on every view, which can add latency if the backend is slow; static canvases avoid this but need explicit action-triggered updates
Canvas Kit apps installed inside Workflows have additional restrictions on which components accept end-user input
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?