> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/guides/integration-matrix.md).

# Integration Matrix

This guide covers connecting external tools and services to Nerve Protocol via Secure Data Connectors. Each integration runs through a TEE-resident connector — credentials are sealed inside the enclave at authorization and never exposed to the host OS or network.

## Integration Principles

* **Least Privilege Always:** Default scopes are minimal. Elevate only what a mission explicitly needs.
* **Attestation-Gated Tokens:** OAuth tokens are sealed to the enclave. Exfiltration attempts trigger revocation.
* **Policy Capsules:** Each integration carries its own policy capsule describing intent, retention, sharing, and expiration.

## Uber

1. Initiate OAuth from the Integration Grid.
2. Approve the **“Ride History”** scope to enable travel reconciliations.
3. Optional: add the **“Ride Dispatch”** scope to let agents schedule rides for operators or clients.
4. Sample workflow: `AGENT.SEND uber.schedule "Tim's place" 18:00`.

## Amazon

1. Generate an encrypted Amazon API key within the enclave browser.
2. Attach purpose tags such as `logistics`, `procurement`, or `intel`.
3. Enable receipt ingestion to track shipments in the Signal Lattice.
4. Guardrail tip: restrict purchase amounts to prevent runaway agents.

## Slack

* Install the Nerve Slack app from the workspace marketplace.
* Scopes: `channels:history`, `chat:write`, `files:read`. Each scope is enforced via per-channel policies.
* Use channel aliases inside the console to message teams without revealing operator identities.

## Notion

* Connect using the Notion internal integration token generated inside the enclave browser.
* Map vaults to Notion databases using deterministic aliases.
* Agents can draft updates, sync knowledge bases, and archive intel back into Notion without exposing metadata.

## Google Drive

* Configure a Google Cloud service account that’s delegated to specific folders.
* Upload encryption manifests so collaborators can decrypt shared docs locally.
* Enable Enclave Integrity Monitor surveillance to detect unusual file access patterns and flag policy deviations in real time.

## Google Calendar

* Use domain-wide delegation with read/write scope limited to mission calendars.
* Agents can set up board calls or investor updates while policy capsules ensure invites stop at the right people.
* Pair with Uber integration to auto-schedule travel windows.

## Gmail

* Route Gmail access through the **Secure Mail Proxy** agent.
* Content stays inside the enclave; outside clients only see encrypted stubs.
* Automate threads like investor updates while proving compliance with on-chain receipts.

## Google Meet

* Provision ephemeral Meet rooms via the Meet API.
* Publish access links inside the console; participants authenticate via signed tokens instead of exposed URLs.
* Optionally transcribe meetings inside the enclave using speech models audited by the Enclave Integrity Monitor for policy compliance.

## Custom Integrations

* Use the Nerve SDK to wrap bespoke systems—databases, IoT devices, or classified archives.
* Register new connectors with the Integration Registry and receive attestation templates.
* Submit connectors for Enclave Integrity Monitor evaluation to score reliability, attestation quality, and security posture before production use.

## Monitoring & Alerts

* The Integration Grid streams health metrics, usage patterns, and policy alerts.
* Set up `SENTINEL` rules to notify you when integrations approach rate limits or encounter anomalies.
* Export zero-knowledge integration reports for auditors without exposing payloads.

With integrations connected, agents can retrieve and act on data from these sources within sealed enclave sessions. See [Protocol Capabilities](/product/features.md) for a complete reference of what connected workflows can do.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerve-protocol.com/guides/integration-matrix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.