StockLobster

Use this skill to wire StockLobster alerts into OpenClaw through the hooks gateway and deliver them to Telegram or another supported outbound channel.

Confirmed payload shape

Read references/payload-format.md for the confirmed payload schema and examples.

Recommended OpenClaw hook mapping

Use an agent mapping, not wake, when the goal is direct Telegram delivery.

Sanitized example:

CODEBLOCK0

Setup

1. 1. Enable hooks in ~/.openclaw/openclaw.json.
2. Set a dedicated hooks token, not the shared gateway token.
3. Use hook path /hooks and mapping path /stocklobster so the endpoint becomes:

- http://<HOST>:18789/hooks/stocklobster

1. 4. Use messageTemplate, not textTemplate, because this flow should use action: "agent" for channel delivery.
2. Reference incoming webhook fields through payload, for example {{payload.text}}.
3. Set:

- deliver: true - channel: "telegram" - to: "<TELEGRAM_CHAT_ID>"

1. 7. Restart the gateway after config changes:

CODEBLOCK1

Testing with curl

CODEBLOCK2

Expected response:

CODEBLOCK3

If you only want to wake a session and not push to Telegram immediately, use action: "wake" with textTemplate, but that is a different flow.

Troubleshooting

• - INLINECODE17

- For wake, the rendered textTemplate was empty. - For agent, the rendered messageTemplate was empty. - In this OpenClaw build, templates resolve against payload, not json.

• - Hook accepted but no Telegram message arrived

- Check that the mapping uses action: "agent". - Check deliver: true. - Check channel and to are set explicitly. - Restart the gateway after editing config.

• - Hook returns INLINECODE28

- That indicates a wake event, not necessarily an outbound Telegram delivery.

• - Hook returns INLINECODE29

- That indicates an agent run was created for delivery-capable handling.