Webhooks

If your tool can POST, it can feed your memory.

What it changes

Not every tool has a connector, and some never will. The in-house business tool, the homemade CRM, the script that runs on Friday night: they produce useful information that goes nowhere.

A webhook endpoint connects all of them at once, without waiting for someone to write a dedicated integration.

What enters the memory

Whatever you send. Raw text, JSON, the body of a forwarded email. Verbasil looks for content in the usual fields rather than imposing a format.

What Verbasil does with it

The same treatment as any other source: decisions and reasoning, commitments and deadlines, learnings, recurrences. Every item stays tied to what produced it, with its date.

And as everywhere, nothing enters without human approval.

How to connect it

1. Open Integrations in Verbasil, then Webhooks.
2. Copy the receiving address, which belongs to your memory.
3. POST to it from your tool, with your text in the body.
4. Review what arrives in Sources, then approve.

What it does not do

The endpoint only receives: Verbasil never calls your system back and pushes nothing to it.

Treat the address as a secret: it amounts to permission to write into your memory.

FAQ

How do I authenticate my calls?

The address itself carries the secret. You can regenerate it if you think it leaked.

Is there a size limit?

A drop is a drop: a few hundred thousand characters, far beyond any meeting report.

Can I send several topics at once?

Yes. Verbasil splits them and handles each part separately.