Automation recipes for the MELEK ecosystem: WHEN a tag appears, a tag trends, or a campaign fires — THEN notify, webhook, reward, or post. The differentiator the other Steem clones never had, wired to our tag engines. Read-only: this surface holds no key and plans actions; a downstream executor behind the Signer does the real work.
| Name | When | Then | ID |
|---|---|---|---|
| Ping me on #melek | WHEN tag #melek |
THEN notify @hathor |
ex-melek-notify |
| Webhook when a tag trends | WHEN velocity #prana ≥ 25 |
THEN webhook https://example.invalid/hook |
ex-trend-webhook |
| Reward the launch campaign | WHEN campaign #launch |
THEN reward 10 MELEK |
ex-campaign-reward |
The recipe JSON appears here. This preview is client-side only — nothing is stored or executed.
GET /api/ifttt/recipes lists recipes as JSON ·
POST /api/ifttt/evaluate with { event, recipes? } returns the fired recipes' planned actions
(or GET /api/ifttt/evaluate?type=tag&tag=melek offline). Nothing is signed or broadcast.