Automate The Mercure protocol
HumDay reads The Mercure protocol’s own published API description and derives 5 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What The Mercure protocol is
[Mercure](https://mercure.rocks) is a protocol allowing to push data updates to web browsers and other HTTP clients in a convenient, fast, reliable and battery-efficient way.
API host: mercure.local
What HumDay can do in The Mercure protocol
1 documented operations change something in The Mercure protocol.
- POSTPublish an update
/.well-known/mercure
What HumDay can read from The Mercure protocol
These are the operations a schedule or a trigger can watch.
- GETSubscribe to updates
/.well-known/mercure - GETActive subscriptions
/.well-known/mercure/subscriptions - GETActive subscription for the given topic and subscriber
/.well-known/mercure/subscriptions/{topic}/{subscriber} - GETActive subscriptions for the given topic
/.well-known/mercure/subscriptions/{topic}
How automating The Mercure protocol works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live The Mercure protocol account.
- Grant access, then go live. You approve the specific The Mercure protocol operations it may use — and only those.
Automate The Mercure protocol with these
- Zendesk636 operations
- Discord242 operations
- Twilio199 operations
- Slack174 operations
- Twilio Preview147 operations
- Circuitsandbox 2123 operations
- Intercom108 operations
- SIGNL4101 operations
- Twilio Conversations101 operations
- Telegram Bot74 operations
- Twilio Taskrouter60 operations
- WhatsApp Business55 operations
Categories
Questions about The Mercure protocol automation
- Can HumDay connect to The Mercure protocol?
- Yes. HumDay reads The Mercure protocol's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 5 operations are documented.
- Do I need to write code to automate The Mercure protocol?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your The Mercure protocol account.
- What can HumDay do in The Mercure protocol?
- 1 of the 5 documented operations change something in The Mercure protocol, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my The Mercure protocol account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to The Mercure protocol is held behind that approval.
Where this came from
The operations above are read from a published API description for The Mercure protocol at raw.githubusercontent.com/dunglas/mercure/main/spec/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.