In chat as a tool
The AI agent calls the connector on its own when your question requires it. "Summarize my last ten Outlook emails" – the AI reads them without you copying anything.
Integrations.
Your tools.
Safely connected.
Connect your tools – sensitive content is anonymized before the AI sees it.
Integrations connect anymize to your external services via OAuth: Microsoft 365, Google Workspace, HubSpot, Notion, Asana, GitHub and more. Once connected, the AI can read and write there – as a tool in chat, as a building block in workflows. The crucial part: data flowing from these apps into the AI can run through anymize anonymization. An Outlook email gets summarized without plain-text PII reaching a US model.
What are connectors?
Your tools become
tools for the AI.
A connector is an OAuth connection to an external service – your inbox, your CRM, your repository, your database. Once connected, anymize can read and write there on your behalf. You never hand over passwords; you authorize access through the provider's official OAuth flow.
Connectors take effect in two places – and that is the decisive point:
Two points of use
In workflows as a building block
In automated flows, connectors become steps: read data from Google Sheets, create a Notion entry, send an email via SMTP – chained, triggered, repeatable.
The effect: anymize does not stay locked in its own window but works where your data already lives. And everything that comes in can run through anonymization before an AI model sees it.
Available connectors
Eight services, instantly connected.
More on request.
The most important office, CRM, project and developer services connect directly – via OAuth in seconds:
Microsoft 365
Microsoft 365
Outlook (email), Calendar, OneDrive, Teams, Microsoft To Do, OneNote
Google Workspace
Google Workspace
Gmail, Google Calendar, Google Sheets, Google Drive, Google Docs
CRM & projects
HubSpot
Contacts, Deals, Companies, Tickets
Asana
Tasks, Projects
Knowledge & documents
Notion
Create pages (Markdown → Notion blocks)
Developers & data
GitHub
Repositories, Issues, Pull Requests, Code
Postgres
SQL query against an external database
Communication
Email / SMTP
Sending (text + HTML, attachments)
More categories on request
Need a service that is not yet on the list? The following categories can be connected on request:
MessagingCRMMarketingDatabasesStoragePaymentsAnalyticsFormsSocialMediaDeveloper
How it works
Connect, then use
in chat and in workflows.
Three steps from click to working AI – no passwords, no API keys by hand.
The path to a connector
Connect via OAuth
Under "Connectors" you pick the service, get redirected to the provider and authorize access. anymize stores no passwords – only the token issued by the provider.
Use in chat
The AI agent accesses the connector on its own when your question requires it. "Which deals are due this week?" – the AI queries HubSpot and answers.
Use in workflows
In the workflow builder you drop the connector into your flow as a building block: read, transform, write – triggered manually, on a schedule or by an event.
Management
All connections in one place
Under "Connectors" you manage all OAuth connections centrally: connect, review permissions, disconnect. A disconnected connection instantly revokes all AI access to that service.
The security leverage
Content runs through anonymization
What comes out of your apps is anonymized before the AI sees it.
A connector often delivers highly sensitive data – client emails, CRM contacts, patient records. Before this content goes to an AI model, it can run through anymize anonymization.
Practical consequence: an Outlook email with plain-text names, addresses and IBANs gets summarized without the PII ever reaching an international frontier model. The connector fetches the data, anonymization protects it, the model sees only placeholders.
Usage patterns
Three typical connector flows
Inbox in chat
Trigger
"Summarize my unread Outlook emails"
Connector works
Outlook connector reads the mails – anonymized before the model
Result
Compact summary, no plain-text PII at the US model
CRM in a workflow
Trigger
Weekly workflow starts automatically
Connector works
HubSpot connector pulls due deals, the AI prioritizes
Result
Triage list lands as an email via SMTP in the team inbox
Report from data
Trigger
"Build the monthly report from the revenue sheet"
Connector works
Sheets connector reads numbers, Postgres adds a detail query
Result
Finished report as an artifact, optionally saved to Notion
Anonymization in integrations
Data from your apps
runs through anonymization.
This is the core difference to any other connector system: content flowing from Outlook, HubSpot, Drive or Postgres into the AI does not go to an international frontier model in plain text. It passes through anymize anonymization first. The model sees placeholders – yet you still get the answer about your real data.
The path of a record
An Outlook email with plain-text names, addresses and IBANs is fetched by the connector, anonymized and only then handed to the model. The answer is translated back automatically – you read "Dr. Maria Schmidt", the model only ever saw [[LASTNAME-7F2]].
Connector fetches
Outlook email with real PII
Anonymization
names, addresses, IBANs → placeholders
Model sees
only [[LASTNAME-7F2]] – no plain-text PII
What this means
Sensitive content stays protected
Client emails, CRM contacts, patient records, database fields – everything a connector delivers can be anonymized before it reaches a model.
Full answer quality
Bidirectional anonymization translates the answer back automatically. You keep working with your real data – the model never saw it in plain text.
Connect your tools – sensitive content is anonymized before the AI sees it. This holds in chat and in workflows, equally for every connector.
Use cases
What connectors
actually deliver.
Five flows born out of real work:
Summarize the inbox
Connector
Outlook · Gmail
Where
Chat
Specifics
Mails anonymized before the model – no plain-text PII at the US model
Enrich CRM data
Connector
HubSpot
Where
Chat · Workflow
Specifics
Query contacts, deals and tickets, let the AI prioritize them
Reports from sheets
Connector
Google Sheets · Postgres
Where
Workflow
Specifics
Read numbers, generate the report, optionally export as an artifact
Triage tickets
Connector
HubSpot · Asana
Where
Workflow
Specifics
Classify incoming tickets, assign, set status
Analyze documents from Drive
Connector
Google Drive · OneDrive
Where
Chat
Specifics
Read and summarize files, sensitive content anonymized
The pattern
Connectors live where your data already is. You no longer fetch it into the AI by hand – the AI fetches it itself, anonymizes it and gives you the result. On request in chat, automatically in workflows.
What you should know about integrations.
Frequently asked questions
An OAuth connection to an external service – such as Microsoft 365, Google Workspace, HubSpot or GitHub. Once connected, anymize can read and write there on your behalf. Connectors take effect in two places: in chat as a tool the AI agent calls on its own, and in workflows as a building block for automated flows.
We stand behind anymize. And we know – when an AI tool touches client, patient or employee data, a demo video isn't enough. That's why we give you 14 days of full access – all models, all features, no credit card. Enough time to be certain, before you trust us.
Your AI workplace awaits.