What problem would this solve?
Push supports iMessage, Telegram, and Slack, but teams that work in Missive cannot use a private Missive conversation as a Push assistant channel without operating a separate webhook relay. A webhook-first adapter would also conflict with the current outbound-connections-only architecture.
What would you like Push to do?
Add a focused built-in Missive channel that uses the official REST API only:
- poll comments from explicitly configured conversation IDs
- accept only explicitly allowlisted stable Missive user IDs
- persist provider event IDs in a local inbox before advancing the channel cursor
- send assistant replies back to the originating conversation as Markdown posts
- use MISSIVE_API_TOKEN or a private missive.api_token setting
- support channel routing, scheduled primary delivery, doctor checks, documentation, and regression tests
The first phase should remain text-only and conversation-scoped. It should not send email, create drafts, accept arbitrary inbox traffic, open an inbound port, or depend on Missive webhooks.
Official API surfaces:
What have you tried?
A separate Cloudflare webhook bridge works for application ingestion, but it is a larger operational surface and is not a good fit for Push, whose value is being one small outbound-only gateway.
What problem would this solve?
Push supports iMessage, Telegram, and Slack, but teams that work in Missive cannot use a private Missive conversation as a Push assistant channel without operating a separate webhook relay. A webhook-first adapter would also conflict with the current outbound-connections-only architecture.
What would you like Push to do?
Add a focused built-in Missive channel that uses the official REST API only:
The first phase should remain text-only and conversation-scoped. It should not send email, create drafts, accept arbitrary inbox traffic, open an inbound port, or depend on Missive webhooks.
Official API surfaces:
What have you tried?
A separate Cloudflare webhook bridge works for application ingestion, but it is a larger operational surface and is not a good fit for Push, whose value is being one small outbound-only gateway.