Workflow automation
Memory that
triggers itself.
n8n calls Korely from any node. A new Stripe charge can write a memory about the customer. A calendar event can pull what past calls settled. An incoming email can search the sender's memory before drafting a reply.
Setup preview
On a self-hosted n8n, install the Korely community node, n8n-nodes-korely, from Settings, Community Nodes. On n8n Cloud, which installs only verified community nodes, use the HTTP Request node with your Korely API key. Example, store context from an email received by the Email Trigger (IMAP) node:
Method: POST
URL: https://api.korely.ai/v1/memories
Header: Authorization: Bearer kor_live_...
Body (JSON), one expression, so quotes and line breaks in the email stay valid:
{{ JSON.stringify({
content: $json.textPlain,
user_id: $json.from,
agent_id: "email-workflow"
}) }}
Field names depend on the trigger: the Email Trigger (IMAP) gives the text as textPlain and the sender as from; map yours accordingly.
Core REST operations: POST /v1/memories to store,
POST /v1/memories/search to query,
GET /v1/context to retrieve ranked context,
GET /v1/facts for typed facts.
Step-by-step setup guide.
What n8n gets
- ●
Workflows write to your memory: a Slack message, a calendar event or an email becomes a memory, scoped to a
user_id, with typed facts extracted and indexed for search. - ●
Workflows read your memory, RAG over your stored context inside any n8n flow. Before sending the customer email, look up past tickets. Before scheduling the call, check what the last one settled.
- ●
Works with self-hosted n8n, your self-hosted or cloud n8n calls the Korely REST API. One memory store, reachable from any flow.
Ready to wire it up?
Follow the step-by-step setup guide, or email me, I'll walk you through it.