AI AI Workforce OS v1.0.0

Integrations

Connecting Google, Microsoft, Slack, Teams, Jira, GitHub, CSV, and more.

System AdministratorsIT Administrators

Overview#

The Integrations area lets you connect AI Workforce OS to external services using OAuth2 or API keys. It is important to understand exactly what "connected" means today before relying on it operationally.

Purpose#

Set expectations correctly: connecting an integration works; automatic data synchronization with most third-party providers does not exist yet.

Prerequisites#

  • A System/IT Administrator account with permission to manage integrations.
  • Admin access to the third-party service you want to connect (to complete its OAuth consent screen).

Step-by-Step Instructions#

Connecting an OAuth2 integration#

  1. Go to Developer → Integrations and choose a provider — Google Workspace, Microsoft 365, Slack, Microsoft Teams, Zoom, Google Calendar, Outlook Calendar, Jira, or GitHub are all listed as OAuth2 connectors.
  2. Start the connection and complete the provider’s OAuth consent screen.
  3. Confirm the connection shows as connected, and re-authenticate later if the token expires.
⚠
Connect works — sync does not

Authorization-code exchange and credential storage for these OAuth2 connectors are fully functional: connecting and re-authenticating genuinely work. Scheduled data sync into AI Workforce OS records is a documented gap in this release — no provider-specific adapter actually pulls or pushes data yet, for any of the listed providers. The connection’s "test connection" check only confirms the stored token is fresh; it does not call the provider’s real API. Do not promise live data sync with Google/Microsoft/Slack/Teams/Zoom/Jira/GitHub based on a successful connection today.

API-key style integrations (Zapier, Make.com, n8n)#

  1. These are listed in the integration catalogue as API-key connectors, using the same generic REST connector as other providers.
  2. There is no dedicated Zapier app or n8n node published for AI Workforce OS in this release — use the Public API directly with an API key if you need to connect one of these automation tools.

CSV import/export#

  1. Use the CSV connector for import/export where you need to move data in bulk without a live third-party connection.
  2. This is a fully functional, dedicated connector, unlike the OAuth2 providers’ sync gap described above.

Generic REST/Webhook connectors#

  1. For services not in the built-in catalogue, use the generic REST or Webhook connector types, combined with the Public API and Webhooks (see Public API).

Screens Involved#

📷
[Screenshot: Developer → Integrations (list)]
📷
[Screenshot: Integration detail / connection status]

Expected Results#

A connected status for the provider you authorized, and (for CSV) actual data moved in or out. For OAuth2 providers, expect connection/re-authentication to work reliably; do not expect ongoing automatic data sync yet.

Not Available in This Release#

🚫
Not currently available
  • Scheduled/automatic data sync for any OAuth2-connected provider (Google Workspace, Microsoft 365, Slack, Teams, Zoom, Google Calendar, Outlook Calendar, Jira, GitHub) — connect works, sync does not exist yet.
  • A dedicated Zapier app or n8n node — these are catalogued as generic API-key connectors only.
  • Real connection-health testing for OAuth2 providers — the current "test connection" only checks token freshness, not actual provider API reachability.

Common Mistakes#

  • Announcing to end users that "Slack/Teams/Google/Microsoft is now integrated" based on a successful OAuth connection, when no data actually syncs yet.
  • Expecting a Zapier app in the Zapier marketplace — none is published; use the Public API with an API key instead.
  • Relying on "test connection" as proof the provider integration is fully working end to end.

Troubleshooting#

A connected integration is not bringing in any data.#

This is expected in the current release — scheduled data sync is not implemented for OAuth2-connected providers. The connection itself (and re-authentication) works, but no adapter pulls or pushes data automatically yet. Use CSV import/export or the Public API for actual data movement today.

An OAuth connection keeps expiring.#

Re-authenticate from the integration’s detail screen. If this happens frequently, confirm the third-party app registration’s token lifetime/refresh settings on the provider’s side.

Public APISecurityMobile App

FAQ#

Can I sync employees from Microsoft/Google automatically?

Not through this integration catalogue today — connection works, but scheduled sync is a documented gap for every OAuth2 provider listed. For provisioning, look at SCIM under Security instead, which is a real, implemented provisioning protocol.

Is there an official Zapier app?

No dedicated Zapier app or n8n node is published. Zapier/Make.com/n8n are listed as generic API-key connectors; use the Public API directly for these automation tools.

What is the most reliable way to move bulk data in or out today?

CSV import/export, or the Public API directly — both are fully functional, unlike the OAuth2 provider sync gap.

Best Practices#

  • For real provisioning/deprovisioning automation, use SCIM (see Security) rather than the generic integration catalogue.
  • Set expectations with stakeholders explicitly: "connected" does not currently mean "syncing data" for third-party OAuth providers.