Connector library

Implemented source CX & Support APIs

Guru connector.

Find Guru knowledge cards, read their verification metadata or bounded content, and discover accessible collections.

Connector download

Download Guru

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Basic auth
Connection settings
API Base URL
Package size
9 KB
SHA-256
3c8beaeda80c1955316d3d7bb5fd1bc6263110adf531c42d60a125dc8dd46661

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Find Guru knowledge cards, read their verification metadata or bounded content, and discover accessible collections.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get card metadata

Read selected card identity and verification metadata.

Get card content

Read bounded vendor HTML or Markdown content as text.

Search cards

Read one non-archived knowledge-card metadata page.

List collections

Read one page of accessible collection summaries.

Vendor API

API and access

Implementation considerations
  • Confirm delegated versus application permissions, tenant or workspace scope, file-size limits, and sharing restrictions.
  • For broad document APIs, start with get/list/create/update/upload/download before deeper document-specific operations.
  • Keep source paths, file IDs, version IDs, and target folder IDs in the workflow payload.

Support

Need help with Guru?

Tell us what you need to connect or change.