Tool presets & credentials

Many integrations need an API key or token. Hania stores those secrets securely and makes common setups one click with presets.

Presets

A preset is a ready-made starting point for a tool type: the configuration filled in for a common integration, so you only supply what's unique to you (usually a credential). Browse presets in the tool catalog when you create a tool; pick one and fill in the blanks rather than configuring from scratch.

Credentials are write-only

When a tool needs a secret (an API key, token, or password), you provide it in the tool's configuration when you create or update the tool. Hania encrypts it at rest and never returns it. Reading a tool back shows only secrets_set (the names of the fields that have a secret stored), not the values.

Connecting with a button

Some apps don't need a key from you at all. Their form has a Connect button instead, and there are only three steps:

1. Click Connect. A new tab opens on the app's own sign-in page.
2. Sign in there and approve. You never type that password into Hania.
3. Come back to the tab you started from. It notices the approval and carries on by itself.

WhatsApp, Facebook Page and Instagram connect with a Continue with Facebook button instead. It opens a small pop-up window where you sign in and pick your number, Page or account. Hania saves the connection as soon as the window closes.

When you approve, the app hands Hania a key that lets your agent work on your behalf. Hania stores it encrypted like any other credential, and you can remove the connection from Tools whenever you like.

The same button appears wherever a connection is needed: on the Tools page, on an agent's Tools tab, at the end of the blueprint setup, and in a chat when an agent asks you to connect something. If you would rather type the details yourself, choose Enter the details manually instead. A few accounts can only be connected with the button, and the form tells you when that is the case.

Picking up where you left off

If you start connecting an app and leave before approving, nothing is lost. The connection is saved without a login, and it does not count as connected: an agent that needs the app still lists it as something to connect. When you come back, Connect finishes that same connection instead of creating a second one.

Safety settings

Every tool configuration also carries three safety settings that decide how careful Hania is when an agent uses the tool while nobody is watching. You'll find them under Show advanced at the bottom of the form, and the closed row tells you the current setting, for example Safety: read-only. Most people never need to open it. Safety in autonomous runs explains what each one does.

One credential, many bots

A tool configuration lives at the workspace level, so a single credentialed tool can be assigned to multiple bots. When you assign a credentialed tool to a bot, you reference the tool configuration; the secret stays in one place. See the Tools API for the exact fields.