# Webhook Automation Guide

KEY CONTEXT:
Practical patterns for using Synapse webhooks to automate workflows. Covers logging, summarization, external tool integration, sync to note-taking apps, and monitoring. Events: memory.created, memory.updated, memory.deleted, memory.verified, memory.unverified, task.updated, chat.message_sent.

Webhook Automation Guide
Practical patterns for automating workflows with Synapse webhooks.
Pattern 1: Memory Log
Log every new memory to a file or external service.
Setup
[CODE BLOCK]
Explanation
The handler listens for  events and logs each new memory's key and a content preview to a file. This is useful for auditing, debugging, or creating a secondary backup of important memories.
Pattern 2: Memory Summary
Summarize new memories using an LLM and store the summary.
Setup
[CODE BLOCK]
Explanation
This pattern captures both  and  events, sends the content to an LLM for summarization, and stores the result. Useful for maintaining a condensed knowledge base.
Pattern 3: Sync to Note-Taking App
Forward new memories to Notion, Obsidian, or similar tools.
Setup
[CODE BLOCK]
Explanation
This pattern forwards each new memory to a Notion database, preserving the key as the title, content as a text property, and category as a select field. Adapt the API call for Obsidian, Logseq, or other tools.
Pattern 4: Monitoring & Alerting
Get notified when memories are deleted or when tasks fail.
Setup
[CODE BLOCK]
Explanation
This pattern monitors for  and  events. When a memory is deleted or a task fails, it triggers an alert. Useful for monitoring and ensuring data integrity.
Pattern 5: Chat Message Relay
Forward chat messages to an external system for logging or analysis.
Setup
[CODE BLOCK]
Explanation
This pattern listens for  events and forwards them to an external logging or analysis system. Useful for conversation analytics, compliance logging, or integration with CRM systems.
Conditional Trigger Patterns (v1.18.14)
Register a webhook that fires only when the event payload satisfies a
category/tag/priority combination — e.g. alert only on critical security facts:
[CODE BLOCK]
Filter fields (all optional, but at least one required):
| Field | Meaning |
|---|---|
|  | fire only if  is one of these |
|  | fire only if  contains the given tag(s) |
|  |  (default) = at least one tag matches;  = every listed tag must be present |
|  | fire only if payload priority rank ≥ this () |
Safe defaults: events whose payload has no category/tags (e.g. ,
chat events) never fire filtered webhooks; a corrupt  JSON is treated as
unfiltered (the webhook stays active);  ignores the filter
on purpose. Note: only  /  payloads carry
// — including the GET alternatives
(, ), which fire webhooks since
v1.18.14.