Praxis Agents OS
View on GitHubRead the docs

10 integrations. 70 tools. Your rules on every one.

Integrations are how agents put what you know to work, inside the systems where your data already lives. Each one is a set of typed tools, with a declared effect and a policy that says whether it may run on its own.

Read the integration architectureSee how it works

Each provider is switched on per deployment. One you have not enabled adds no tools and no UI.

70
tools across ten integrations
38
of them write to a real system
31
writes nobody can set to Auto

What each one lets an agent do.

Reads run on their own unless you say otherwise. Writes wait for a person. Locked writes cannot be made automatic by any setting.

  • Read, Auto by default
  • Write, Approval by default
  • Write, locked to Approval

  • Gmail

    3 tools
    Reads
    Search and read messages in the connected mailbox.
    Writes
    Send a message. Waits for approval by default, with recipients, subject and body open for editing.

    gmail_send_message· OAuth, per user

  • Outlook Mail

    New
    12 tools
    Reads
    Search and read messages, folders, attachments and people.
    Writes
    Send, reply, forward and draft are locked to Approval. Moving and updating messages default to Approval.

    outlook_mail_reply_to_message· Microsoft Graph OAuth

  • SharePoint

    New
    9 tools
    Reads
    List folders, search files, read and search inside documents, open shared links.
    Writes
    Creating folders and writing or updating files are locked to Approval. Copying a file into Praxis runs on Auto.

    sharepoint_write_file· Microsoft Graph OAuth

  • Google Ads

    22 tools
    Reads
    Bounded, read-only reports across the accounts you select.
    Writes
    Keywords, negatives, lists, budgets, recommendations, campaign status and device bids. Every write is locked to Approval.

    google_ads_add_campaign_negative_keywords· OAuth or service account

  • Meta Ads

    New
    1 tools
    Reads
    Insights reporting across the ad accounts you select.
    Writes
    None yet. Write tools are planned.

    meta_ads_run_insights· System User access token

  • Google Analytics

    5 tools
    Reads
    Standard and realtime GA4 reports, field discovery and compatibility checks, linked Ads accounts.
    Writes
    None. Read-only.

    google_analytics_run_report· OAuth or service account

  • Search Console

    New
    5 tools
    Reads
    Search analytics, sitemaps and URL inspection.
    Writes
    Submitting a sitemap defaults to Approval. Requesting indexing is locked to Approval.

    google_search_console_request_indexing· OAuth

  • BigQuery

    3 tools
    Reads
    List tables, read schemas, run queries. Row filters are enforced before a query is allowed to run.
    Writes
    None. Read-only.

    bigquery_run_query· Service account

  • Airtable

    4 tools
    Reads
    List and get records in the bases you select.
    Writes
    Create and update records. Approval by default.

    airtable_update_record· API key

  • Notion

    6 tools
    Reads
    Search and read pages and data sources. Pages can also feed the knowledge base.
    Writes
    Create pages and update content or properties. Every write is locked to Approval.

    notion_create_page· OAuth, per user

And the model is your choice, per agent.

  • OpenAI
  • Anthropic
  • Google Gemini
  • Azure OpenAI
  • Open-source models

Choose the accounts each run can see.

Connect a Google Ads manager account and Praxis lists every account under it. Connect Analytics and it lists the properties. For each conversation or schedule you pick what is in scope, or reuse a saved context group.

Every integration is built from the same five parts.

So a new one behaves like the others from the day it ships.

  1. 01ConnectionOAuth, an API key reference, or a service account. Raw secrets never live in the app. The API takes references to your secret manager.
  2. 02ResourcesPraxis finds what is inside a connection: ad accounts, properties, sites, bases, datasets, mailboxes, drives. You choose which ones agents may use.
  3. 03ToolsTyped tools that declare whether they read or write, where data goes, and which policies they allow.
  4. 04Active contextFor every conversation and schedule, you pick the resources in scope. The agent sees only those.
  5. 05AuditEvery call is recorded with the actor, the requester, the tool, the provider and the outcome. Kept for 400 days.

Next on the list.

Planned work is written up as a public plan before any code lands. None of these is available today.

  • Planned

    Outlook Calendar tools

    The connection exists today. Agent tools for reading and booking are planned.

  • Planned

    SharePoint as a knowledge source

    Index SharePoint documents into the knowledge base, next to Notion.

  • Planned

    Meta Ads writes

    Campaign and budget changes, locked to Approval like Google Ads.

  • Planned

    Microsoft Teams

    Teams support, on the same Microsoft Graph foundation as Outlook and SharePoint.

Useful connectors go upstream. Yours stay yours.

A generally useful provider can be contributed to the open-source project. A connector to your internal system, and the agents and rules around it, stay in your private implementation.

Open source, upstream

The platform improves in public

  • The runtime, the workspace and the tool registry
  • Approvals, audit and the rest of the governance layer
  • Fixes and improvements that help everyone
  • Integrations with products other people also use
Private, yours

What is built for you stays with you

  • Your agents, their instructions and your business rules
  • Views and dashboards built for your team
  • Connectors to your internal systems
  • Your configuration, credentials, data and history

Need one that is not here?

Public providers are planned in the open on GitHub. Private ones, for your internal systems, are built in an implementation.

Discuss a private integrationView the plans