Zapier

Trigger Zaps from Nemu events and read run history. Wire Nemu into 8,000+ apps without code.

3scopes, and you approve each one
Read onlynemu never writes back to Zapier
Two placesthe chat, and the indexing API

What a thread can reach, and nothing else.

You grant scopes once in the console. Everything inside them becomes searchable, citable context. Everything outside them stays where it is.

zapier · granted scopesread only
  • Zap metadatagranted
  • Run historygranted
  • Connected app namesgranted

Anything you did not grant is invisible to the model. Revoke a scope and the content it covered stops being reachable on the next request, with nothing left behind in a thread.

a thread, using zapier
▸ searching zapier
▸ 3 matches in zap metadata
▸ citations attached to the answer
▸ nothing outside your scopes was read

Three steps, then it is just context.

01

Authorize from the console

OAuth in a couple of clicks. Tokens are stored encrypted and nemu never sees a password.

02

Pick the scopes

Each one is a separate grant. Approve the ones you want and leave the rest untouched.

03

Ask, search, index

Granted content answers questions in the chat and is available to the indexing API on your credits.

More in Automation

Get started now

Start with your keys, keep the whole bill.

The gateway, the chat and the computer on one account. Free is enough to evaluate the gateway and the chat on your own keys, and your provider keeps billing the tokens exactly as it does today.

No token markup. Credits only pay for what nemu runs