Connections

Every tool has
a way in.

Invice is not built around an integrations list — it is built on open standards. Which wire a tool rides depends on what the tool supports; how far it reaches depends on what you allow. Seven ways in, one agent at the end of all of them.

It signs you inGmail, Outlook, Google Calendar
Your agent sends, reads, and schedules as you — from your own address, revocable any time.
It gives you a keyClaude, ChatGPT, Gemini, Mistral, Calendly
Paste the key once. It is encrypted before storage and never shown to any AI model.
It publishes its actionsGitHub, Linear, Stripe, Airtable, Fireflies, Supabase…
Every action the app publishes is discovered automatically and becomes a tool your agent can call.
It documents an APIDocumented JSON endpoints
You declare the endpoints and auth; each becomes a tool only after a real test passes.
It pushes events outYour CRM, form tools, internal systems
The app sends contacts and events to a signed Invice address. No key ever leaves your side.
It runs an agent tooAnother professional on Invice
Your agents exchange asks and answers with consent on both sides. Neither reads the other’s data.
It has none of theseLegacy tools, spreadsheets, exports
CSV and Excel import with column mapping, or a Zapier bridge that reaches 8,000+ apps.
Seven wires, one destinationyour Invice agent
Who decides what

The app picks the wire.
You pick the reach.

A connection is a negotiation between what the tool supports and what you permit. Invice handles the first part with open standards and honest testing; the second part never leaves your hands.

The app decides the wire
Every tool arrives by the strongest path it supports.

A token-ready MCP tool hands your agent its action catalog in one connect. One with only a REST API gets exactly the JSON endpoints you declare and test. One with neither can still enter through import or a bridge. The question is which path is honest for that tool.

You decide the reach
Every discovered action is yours to allow.

The connect test lists every action the app exposes. You switch each one on or off. Connected-tool triggers wait for your approval before a call runs.

You decide the trust
Keys are secrets. They stay secrets.

Credentials are AES-256 encrypted before storage, decrypted only for the moment of a live call, never logged, and never placed in any AI model’s context.

You decide when it ends
Disconnect is one click, and it is absolute.

Revoke a connection and its tools are gone from the agent’s hands at the very next step. OAuth grants can be revoked from the provider’s side too — you always hold both ends of the wire.

01 · Pick or name it

Choose from the directory, or name any app.

The Connections page lists verified paths for the tools professionals use most — documents, finance, CRMs, meetings, databases. If yours is not listed, every layer ends with an add-your-own card: name the app, point at its server or API.

02 · Grant access

Sign in, or paste one key.

OAuth apps ask through their own consent screen. MCP and API tools take one pasted key, encrypted server-side the moment it arrives. Account-specific URLs are flagged before you test, and nothing sensitive ever travels in a link.

03 · Watch the live test

The connection proves itself before it saves.

Invice runs a real handshake and pulls the app’s live action list — you see every tool it found before anything is stored. A connection that cannot pass a real test does not get to call itself connected.

04 · Set the rules

Choose which actions are available.

Per action: on or off. Connected-tool triggers wait for your approval before execution. Change availability any time; the setting applies to the very next call.

05 · Put it to work

Missions use whatever you connected.

Brief a mission in plain language and the agent works across every wire you granted: reading the transcript from your recorder, updating the contact in your CRM, adapting the template document, sending it from your own inbox.

Tested, not listed

If it has an API,
it has a seat.

Every named connection in the product carries the vendor's real endpoint, verified against their own documentation — and nothing calls itself connected until a live test proves it. Bring your stack and see which wire each tool rides.