Make

A Make scenario can send just about anything. It still has to land somewhere useful.

What it changes

Make already talks to your tools. What was missing was somewhere for what passes through to leave a usable trace: not a log, a memory that connects things and comes back to you.

What enters the memory

Whatever your scenario sends: a piece of text, a report, an email body, a form response, an updated record. Verbasil accepts raw text or JSON, and finds the content wherever it sits.

What Verbasil does with it

Exactly what it does with a manual import. It pulls out decisions and their reasoning, commitments and their deadlines, learnings, and topics that keep coming back. Every item keeps a link to what produced it.

The part that matters: nothing enters without approval. An automation writing straight into the memory would fill it with noise within a week. What arrives waits in Sources.

How to connect it

1. Open Integrations in Verbasil, then Make.
2. Copy the receiving address shown.
3. Add an HTTP step in your Make scenario, POSTing to that address.
4. Send your text in the request body, then approve what lands in Sources.

What it does not do

Verbasil reads nothing from Make and triggers no scenario. The link runs one way: Make sends, Verbasil receives.

There is no official Make module: an HTTP step is enough, and it depends on no update from us.

FAQ

Is there a required format?

No. Raw text or JSON, Verbasil finds the content. A title helps, it becomes the name of the source.

What if my scenario sends the same thing twice?

Verbasil recognises duplicates and will not create the same item twice.

Does this fill my memory without me seeing it?

No. Everything that arrives waits in Sources until you have reviewed it.