Skip to main content

Integrations

An integration is a connection to a system where context for your writing already lives: Slack or Google Drive. It is a writing-context connection, not a general assistant plugged into your company.

The integration directory is at rewr.it/account#integrations. Google Workspace and Slack are listed there, but both are coming soon. You cannot connect either account yet. Google Workspace is for Drive documents; it does not include Gmail, and there is no plan to add it.

Connected does not mean read​

Connecting an account does not give the app permission to read it freely. It can only read a source you select for that piece of writing.

Search can show you results, but it cannot read a document because it ranked there. Every read is a source you chose.

What an integration can do​

The permitted operations are all reads:

  • Search for material you ask for
  • Read a document, thread, or message you choose
  • List channel and folder names so you can set the connection's boundary

There is no operation to send, post, edit, label, or delete. Widening that set requires a reviewed code change.

Not every connection gets all three, and a connection shows you what it was actually given.

Google Drive works differently​

Slack lets you search the channels you allow and choose a source from the results. Google Drive does not, and the reason is worth knowing.

The app asks Google only for the ability to read documents you hand it. It cannot search your Drive, list it, or see a file you have not picked. You choose documents in Google's own file picker, and those become readable. Nothing else does.

That is the same rule as everywhere else on this page, except that Google enforces it rather than us. A mistake on our side cannot expose a document you never picked, because the app was never able to see it.

The trade is that you pick files rather than asking the app to find them.

What is kept​

Provider text exists in memory for the length of one request. There is no crawling, background sync, index, or cached copy of your documents. Document titles, document bodies, and search queries are not stored.

Some connection metadata is kept:

  • The account label, so the connection can identify the account
  • The channels or folders you chose, so settings can name them
  • A record that a search or read happened, never what you searched for or what a source said; it is deleted automatically after 90 days

Credentials are encrypted and only ever used by the server.

Voice profiles are separate​

Connecting a source is not consent to learn your voice. Material from an integration can only reach a voice profile through the existing sample-selection flow, with its own confirmation. See Voice profiles.

Disconnecting​

Disconnecting revokes access here immediately. If the provider cannot be reached to revoke access remotely, the app tells you that; it does not imply the remote revocation succeeded.

Where connections work​

Connections work only in a signed-in session where you can select a source. They are not available to hn_ API keys, the MCP server, or scripts. Selecting a source is something a person does, and a key used while nobody is watching cannot do it.

Plan​

Integrations are Pro only. A Pro account can have up to eight connected accounts. See Plans and quota.