Telegram (OpenConnector)
Send messages, photos and documents, and read updates and chats, as a Telegram bot connected centrally in FloMorphic → Connect (OpenConnector / oomol). Holds no Telegram bot token; proxies each action over the flomorphic.svc.oc.* NATS subjects.
- SDK
- Go
- Protocol
inflowv1- Actions
- 5
- Version
- v0.1.0
- Author
- mehdi-shokohi
- Runs on
- flomorphic — needs Connect / OpenConnector proxy
- Categories
- Communication
Reach for it when
A flow that needs to reach a person in seconds, on the thing in their pocket.
The use people don't expect
Pair it with a Human in the Loop node and the approval arrives as a message. The flow is parked on disk the whole time it waits — no process held open, no node sitting at 40%.
A flow that uses it
Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.
Approval from a phone, at 2am
Starts withAny branch that needs a decision a rule can't make.
- Contract
Decides this one needs a person.
- Telegram (OpenConnector)
Sends the case, with whatever a decision needs attached.
- Human in the Loop
Parks. Could be two minutes, could be Monday.
- Telegram (OpenConnector)
Confirms what happened, to the same thread.
What you getThe waiting is free, which is what makes it reasonable to put a person in the loop at all.
The reference, not the pitch
This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.