A whole messaging channel, offline (echo channel + campaign)
The E26 channel end to end with no messaging account and nothing running but this API. An `echochat` connection is a loopback app: outbound messages go to the API's log, and inbound messages and delivery receipts arrive by curl at the ordinary chat webhook. The number is bound to demo 26's support bot, so anybody who writes in gets that conversation. A draft campaign sends one approved template to three people — one of whom the channel is configured to refuse, so the funnel has a real failed row in it — and whoever writes back lands in this demo's own reply flow rather than the number's usual one, which is E26's reply-attribution rule made visible. Everything above the provider is the real thing: the webhook's verify/dedupe/opt-out ladder, the identity registry, the runtime bridge, the dispatcher and the funnel never learn that the app is a log file.
Connects to
- Messaging channel
- SQLite
Also includes
- Chat flow
- Campaign
- 2 pipelines
How you know it worked
Run the demo's pipeline once to create the replies table.
Try this templateUsed in: Restaurants & food service
Related templates
Email a summary with the data attached
The smallest useful notification: read something, email somebody about it, attach it. The email node is a side channel — the payload passes…
Per-location totals joined to settlement, variances emailedRestaurant nightly close (POS vs card settlement)
What every area manager does by hand after service: take the POS sales for each location, take what the card processor actually settled, and find…
File in, cleansed, joined to a price list, exceptions emailedSupplier invoice against the contract price
A supplier's invoice arrives as a file, the way it actually does. It is written to SFTP, read back, cleansed — quantities and prices arrive from a…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.