Docyrus Integrations & Connectors

Use third-party integrations from the terminal with docyrus connect. A connector (a.k.a. data provider) is a platform-defined external integration (identified by a slug, e.g. msgraph, twilio, meta) that bundles managed auth + a set of callable actions + data sources. You discover connectors and their actions, then run actions or make raw authenticated requests through the connector's provider auth — without handling tokens yourself.

Concepts (read first)

• Connector / data provider — the integration definition (core_data_provider), addressed by slug. Holds the auth type, base URL, and the actions it exposes.
• Action — a callable operation a connector exposes (core_action), addressed by provider slug + action key (e.g. msgraph + sendEmailWithOutlook). Has inputJsonSchema / outputJsonSchema.
• Connection — a tenant's stored credentials for a connector (tenant_connection), or a per-user OAuth2 connection (tenant_connection_user). Connections hold the tokens/keys.
• Connection account — an optional sub-account within a connection (e.g. one of several ad accounts / mailboxes), addressed by --connectionAccountId.

⚠️ Connections are NOT created by this CLI. There is no create-connection command. Credentials/OAuth connections are set up in the Docyrus UI (OAuth flow) or via the raw API. This skill discovers and uses connectors; if no connection exists for a provider, the user must connect it first.

Workflow

1. Confirm auth. Every command needs an active session.

   docyrus auth who --json        # or: docyrus auth login