Skip to main content

Anysphere Organization connector reference

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page provides reference information for the Anysphere Organization connector, including supported tables and their schemas.

Supported source tables

The Anysphere Organization connector supports the following source tables:

Source table

Primary key

Description

Sync mode

organization_groups

id, snapshot_date

Groups in your Anysphere (Cursor) organization, with daily snapshot history via the snapshot_date partition.

Full refresh only

organization_group_members

group_id, userId, snapshot_date

Members of each group in your Anysphere (Cursor) organization, ingested per group, with daily snapshot history via the snapshot_date partition.

Full refresh only

organization_members

id, snapshot_date

Members of your Anysphere (Cursor) organization with daily snapshot history. Each pipeline run creates a new snapshot_date partition (UTC, YYYY-MM-DD format) so daily snapshots are retained.

Full refresh only

Source table

Primary key

Description

Sync mode

organization_groups

id, snapshot_date

Groups in your Anysphere (Cursor) organization, with daily snapshot history via the snapshot_date partition.

Full refresh only

organization_group_members

group_id, userId, snapshot_date

Members of each group in your Anysphere (Cursor) organization, ingested per group, with daily snapshot history via the snapshot_date partition.

Full refresh only

organization_members

id, snapshot_date

Members of your Anysphere (Cursor) organization with daily snapshot history. Each pipeline run creates a new snapshot_date partition (UTC, YYYY-MM-DD format) so daily snapshots are retained.

Full refresh only

Connector options

The Anysphere Organization connector has no additional configuration options beyond the pipeline settings available for all managed connectors. See Ingest data from Anysphere Organization.

Destination table schemas

organization_groups

Primary key: id, snapshot_date Sync mode: Full refresh only with daily history via snapshot_date partition

Field

Data type

id

STRING

name

STRING

createdAt

TIMESTAMP

updatedAt

TIMESTAMP

snapshot_date

DATE

Field

Data type

id

STRING

name

STRING

createdAt

TIMESTAMP

updatedAt

TIMESTAMP

snapshot_date

DATE

organization_group_members

Primary key: group_id, userId, snapshot_date Sync mode: Full refresh only with daily history via snapshot_date partition

Field

Data type

group_id

STRING

userId

BIGINT

name

STRING

email

STRING

joinedAt

TIMESTAMP

snapshot_date

DATE

Field

Data type

group_id

STRING

userId

BIGINT

name

STRING

email

STRING

joinedAt

TIMESTAMP

snapshot_date

DATE

organization_members

Primary key: id, snapshot_date Sync mode: Full refresh only with daily history via snapshot_date partition

Field

Data type

id

BIGINT

name

STRING

email

STRING

organizationRole

STRING

teams

ARRAY<STRUCT<teamId: BIGINT, teamName: STRING, teamSlug: STRING, teamRole: STRING>>

snapshot_date

DATE

Field

Data type

id

BIGINT

name

STRING

email

STRING

organizationRole

STRING

teams

ARRAY<STRUCT<teamId: BIGINT, teamName: STRING, teamSlug: STRING, teamRole: STRING>>

snapshot_date

DATE

The snapshot_date column is stamped at ingestion time (UTC, YYYY-MM-DD format). Each pipeline run creates rows partitioned by the current date, allowing you to retain daily snapshots of organization membership across multiple runs.