[OpenClaw] Persistent ParseError in custom plugin (webhook_receiver)
I'm following up again on my previous posts regarding the HTTP route registration for a local custom plugin (webhook_receiver) in OpenClaw. The ParseError at index.js:67:6 (or 74:6 in previous attempts) persists even after the latest code modifications.
My sincere apologies for the repeated posts, but I'm providing all context for a definitive resolution.
Here's an update on the current situation:
1. OpenClaw Version: 2026.2.15
2. OS: WSL2 (Ubuntu/Linux) on Windows
3. Plugin Files: index.js and openclaw.plugin.json are in ~/.openclaw/extensions/webhook_receiver/.
• openclaw.plugin.json content has been verified to be strict JSON.
• npm install for micro dependency completed successfully.
4. OpenClaw Config (openclaw.json):
• plugins.entries.webhook_receiver.enabled is true.
• plugins.paths was previously removed due to Unrecognized key: "paths" errors.
• plugins.entries.webhook_receiver.config is set with "path": "/api/agent-job", "secret": "CHANGE_THIS_SECRET".
5. Cache/State: OpenClaw cache has been cleared (openclaw gateway clear --all) multiple times.
6. Recovery: I've used openclaw doctor --fix several times to restore the gateway after startup failures.
The persistent error message (from Gateway logs, after openclaw gateway restart):
Error: ParseError: Unexpected token, expected "," /home/user/.openclaw/extensions/webhook_receiver/index.js:67:6
(This error has consistently pointed to either line 67 or 74, column 6, always indicating an unexpected token where a comma was expected, despite the code appearing valid in a standard Node.js environment.)
My sincere apologies for the repeated posts, but I'm providing all context for a definitive resolution.
Here's an update on the current situation:
1. OpenClaw Version: 2026.2.15
2. OS: WSL2 (Ubuntu/Linux) on Windows
3. Plugin Files: index.js and openclaw.plugin.json are in ~/.openclaw/extensions/webhook_receiver/.
• openclaw.plugin.json content has been verified to be strict JSON.
• npm install for micro dependency completed successfully.
4. OpenClaw Config (openclaw.json):
• plugins.entries.webhook_receiver.enabled is true.
• plugins.paths was previously removed due to Unrecognized key: "paths" errors.
• plugins.entries.webhook_receiver.config is set with "path": "/api/agent-job", "secret": "CHANGE_THIS_SECRET".
5. Cache/State: OpenClaw cache has been cleared (openclaw gateway clear --all) multiple times.
6. Recovery: I've used openclaw doctor --fix several times to restore the gateway after startup failures.
The persistent error message (from Gateway logs, after openclaw gateway restart):
Error: ParseError: Unexpected token, expected "," /home/user/.openclaw/extensions/webhook_receiver/index.js:67:6
(This error has consistently pointed to either line 67 or 74, column 6, always indicating an unexpected token where a comma was expected, despite the code appearing valid in a standard Node.js environment.)
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
