cliq
Integrations

A small set of first-class integrations.

cliq ships with direct support for the systems most teams need on day one — and connects to everything else through custom agents, exec stages, and webhooks.

01

Notifications

Send pipeline events — start, review-needed, complete, escalate — to where your team already works.

Slack

Post pipeline events to a channel

Outbound notifications
integrations.slack.webhook_url

Jira

Comment on, transition, or update the originating ticket

Outbound updates on the triggering ticket
integrations.jira.{base_url,email,api_token}
02

Knowledge & content

Read source material into a run, and publish deliverables back out.

Google Drive, Docs & Sheets

OAuth or service-account access to files and folders

Pull context · publish results
integrations.google (oauth or service_account)

Microsoft 365 / SharePoint / OneDrive

Graph API access to files and folders

Pull context · publish results
integrations.microsoft.{tenant_id,client_id,client_secret}

Jira tickets

Resolve a ticket into a run brief

Inbound context
cliq req jira:PROJ-123

URLs & web pages

Fetch any HTTP(S) URL as context

Inbound context
cliq req https://example.com/article
03

Source control

For software delivery pipelines. Optional — every non-engineering use case works without this.

GitHub

Create PRs, check for existing PRs, branch operations

Engineering pipelines only
integrations.github.token

Bitbucket Cloud

Create PRs, check for existing PRs, branch operations

Engineering pipelines only
integrations.bitbucket.api_token
04

Agent runtimes

cliq orchestrates the models you already use. Pick the runtime that fits each role; mix and match across a single pipeline.

Claude Code

Long-context reasoning, review, planning

Cursor CLI

Editor-native, strong for coding roles

Gemini

Large-context scans

Codex

Focused coding loops

Custom A2A agents

Wrap any model or service via the SDK

You bring your own API keys. cliq never sees, stores, or marks up model spend.

05

Everything else

Not on the list above? There are four escape hatches — and teams use them every day to connect cliq to CRMs, warehouses, internal APIs, and tools built in-house.

Exec stages

Any script, CLI, binary, or curl command can run as a stage. If your tool has a command-line or HTTP interface, it runs in cliq today.

Custom agents

Build an agent with @cliqhub/cliq-sdk that wraps any API, database, or internal service. Ten lines of code and it plugs into a pipeline like any built-in role.

A2A protocol

cliq speaks A2A. Call other agents, or expose cliq itself as an A2A endpoint for external orchestrators.

Webhooks

Trigger pipelines from any event source — schedulers, CI, upstream workflow tools — by posting to the cliq server.

Ready to ship with a team?

Need an integration we don't ship yet?

Custom agents are a few lines of code. Talk to us about your stack — we prioritize first-class integrations based on what users actually need.