Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
fieldy-ai-webhook 0.1.2 - Transcripts without the wake word are now logged to JSONL files under `<workspace>/fieldy/transcripts/`. - Updated documentation to clarify transcript logging behavior.
What This Skill Does
Configures a Moltbot Gateway webhook endpoint so incoming Fieldy app transcripts are processed by a transform script before reaching an agent. Transcripts containing the wake word "Hey, Fieldy" (or "Fieldy") trigger an agent run with the following text; all others are logged to JSONL files. Wake word behavior and logging can be customized by editing fieldy-webhook.js.
The transform layer filters transcripts by wake word before agent invocation, so the agent only runs on relevant input rather than every transcript the app sends.
When to use it
- Trigger an AI agent from a Fieldy voice transcript using a wake word
- Log all incoming transcripts to JSONL without invoking the agent
- Filter meeting transcripts so only voice commands reach automation
- Customize wake word detection or parsing for a specific workflow
- Route Fieldy webhook events to a self-hosted Moltbot gateway
Example Workflow
Here's how your AI assistant might use this skill in practice.
User sends: POST /hooks/fieldy with body {"transcript":"Hey Fieldy summarize this: hello world"}
- 1Gateway receives the POST request and routes it through fieldy-webhook.js
- 2Transform script checks the transcript for the wake word "Hey, Fieldy" or "Fieldy"
- 3Wake word is detected, so the script extracts the text after it: "summarize this: hello world"
- 4Transform passes the extracted message to the agent via the configured messageTemplate
- 5Agent runs with the input "summarize this: hello world"
Agent executes with the post-wake-word text as its prompt
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.