| name | evernote-webhooks-events |
| description | Implement Evernote webhook notifications and sync events.
Use when handling note changes, implementing real-time sync,
or processing Evernote notifications.
Trigger with phrases like "evernote webhook", "evernote events",
"evernote sync", "evernote notifications".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","evernote","webhooks"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Evernote Webhooks & Events
Overview
Implement Evernote webhook notifications for real-time change detection. Evernote webhooks notify your endpoint that changes occurred, but you must use the sync API to retrieve the actual changed data.
Prerequisites
- Evernote API key with webhook permissions
- HTTPS endpoint accessible from the internet
- Understanding of Evernote sync API
Instructions
Step 1: Webhook Endpoint
Create an Express endpoint that receives webhook POST requests. Evernote sends userId, guid (notebook GUID), and reason (create, update, notebook) as query parameters. Respond with HTTP 200 immediately, then process asynchronously.
app.post('/evernote/webhook', (req, res) => {
const { userId, guid, reason } = req.query;
res.sendStatus(200);
processWebhook({ userId, notebookGuid: guid, reason })
.catch(err => console.error('Webhook processing failed:', err));
});
Step 2: Webhook Reasons
Handle three webhook reasons: create (new note created), update (note modified), and notebook (notebook-level change). Each triggers a sync of the affected notebook.
Step 3: Sync State Management
Store the last sync USN per user. On webhook receipt, call getSyncState() to get the current server USN, then getFilteredSyncChunk() to fetch only the changes since your last sync.
const syncState = await noteStore.getSyncState();
const chunk = noteStore.(
lastUSN,
,
..({
: ,
: ,
:
})
);