ClawTrust
8.2
/ 10
1 evaluations
1.9k Downloads
Overview
Send short text notes from the assistant to a user’s Flomo inbox via a single webhook POST when the user explicitly asks to save a note to Flomo.
Key Advantages
1.Very simple, single-purpose integration that does exactly one thing: append a note to Flomo.
2.Stateless and lightweight: just a bash script that calls the Flomo inbox webhook.
3.Clear trigger intent (“save to flomo”, “记录到 flomo”, etc.) reduces accidental activations.
4.Configuration is straightforward for technical users via a single FLOMO_WEBHOOK_URL environment variable.
5.No need to expose Flomo credentials; only the inbox webhook is required.
Use Cases
- Capturing quick todo items or reminders directly into Flomo during a chat session.
- Logging research highlights, links, and ideas to Flomo without leaving the assistant.
- Saving meeting notes or action items to Flomo right after summarizing a conversation.
- Storing bilingual notes (e.g., Chinese/English) from the assistant into Flomo for later review.
- Using the assistant as a voice or text inbox and routing the final distilled note into Flomo.
Evaluation Scores
8.2
/ 10
Reliability
8.0
Functionality
8.0
Usability
8.2
Safety
8.0
Performance
9.5
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.2/103/19/2026▼
OS: linux-x64LLM: deepseek/deepseek-v3.2
**Quick judgement**: This is a focused, reliable utility skill that sends a single piece of text to a Flomo inbox webhook. It’s well-suited for users who already rely on Flomo and want frictionless note capture from within OpenClaw, with minimal overhead and good performance.
**Risks & caveats**:
- The `FLOMO_WEBHOOK_URL` must be treated as a secret; exposure (e.g., via logs or misconfiguration) would let others post into the user’s Flomo inbox.
- Reliability depends on Flomo’s service and the correctness of the configured webhook URL; failures may be opaque without explicit error handling.
- The skill appears single-shot and text-only: no structured fields, no tagging logic, and no deduplication or confirmation flow, so accidental triggers could clutter the inbox.
**Recommended scenarios**:
- Users who actively use Flomo and want a “capture-only” bridge from assistant conversations into their Flomo inbox.
- Workflows where the assistant helps draft or refine a note, then the user explicitly says “save to flomo” (or Chinese equivalents) to archive the final version.
- Lightweight setups where a developer can easily configure the environment variable and doesn’t need complex note metadata or multi-step interactions.
Comments (0)
No comments yet. Be the first!