Connect Jira, Shopify, Stripe, HubSpot and other tools | Help centre

Built-in integrations connect ChaosDesk to the tools your team already uses. You connect each one once, and agents see its data in the ticket sidebar.

Kind	Tools	What agents get
Issue trackers	Jira Cloud, Linear, GitHub, GitLab	Create or link issues from a ticket, see their status, get a note when they close
Commerce	Shopify, WooCommerce	The customer’s orders, with refunds, cancellations and address changes
Subscription billing	Stripe, Paddle Billing	Subscriptions, invoices and payments, with refunds
CRM	HubSpot, Salesforce	CRM details in the ticket, contacts and companies in sync, tickets on the CRM timeline
Calendars and contacts	Google Workspace, Microsoft 365	Contacts imported as customers, agents’ out-of-office for workforce planning

Integrations are part of the Starter plan and up. HubSpot and Salesforce need the Growth plan or higher.

Slack has its own app: see Use Slack and Microsoft Teams.

Connect an integration

Open Admin Center, Integrations, Integrations.
Pick the tool and fill in the connection details. Each form says where to find them in the other tool.
Choose Test connection, then Connect.
If the form shows a Webhook URL, copy it into the other tool so changes reach ChaosDesk right away.

Secrets are stored encrypted and never shown again. Leave a secret field empty to keep the saved value. Disconnect removes the connection.

Issue trackers

Tool	You need
Jira Cloud	Your site URL, the account email, an API token, a default project key and, optionally, the issue type
Linear	A personal API key and the default team key
GitHub	A fine-grained access token with read and write access to issues, and the default repository. GitHub Enterprise Server also needs its API URL
GitLab	An access token with the `api` scope and the default project. For self-managed GitLab, also its URL

On a ticket, open the Issues card:

Create issue: the title defaults to the ticket subject. You can pick another project, team or repository.
Link issue: paste an issue key or URL.

When the issue is closed in the tracker, every linked ticket gets an internal note. The note notifies the assignee and can fire triggers. For this, add the webhook from the connection form in the tracker and enter its secret in ChaosDesk.

Commerce: Shopify and WooCommerce

Shopify: the shop domain and the Admin API access token of a custom app with read_orders, write_orders and read_customers. Add the app’s API secret key to verify order webhooks.
WooCommerce: the store URL and a REST API key with read and write permission.

The Orders card on a ticket lists the requester’s latest orders, found by email address. Agents can:

Refund all or part of an order;
Cancel order;
Change address for shipping.

Each action leaves an internal note on the ticket with the reason.

Order data also works in your rules and replies:

trigger and automation conditions on the customer’s latest order status and order count;
placeholders such as {{order.number}}, {{order.status}}, {{order.tracking_url}} in macros and notifications. See Placeholders.

Subscription billing: Stripe and Paddle

Stripe: a restricted API key with read access to customers, subscriptions, invoices and charges, and write access to refunds.
Paddle Billing: an API key with read access to customers, subscriptions and transactions, and write access to adjustments.

The Billing card shows the requester’s subscriptions, invoices and payments. Agents can refund a payment from the card. The refund leaves an internal note on the ticket.

CRM: HubSpot and Salesforce

HubSpot: the access token of a private app with contacts read and write, companies read and deals read.
Salesforce: your My Domain URL, and the consumer key and secret of an app with the client credentials flow and a run-as user.

Once connected:

the CRM card shows the requester’s CRM record and deals;
Sync now imports CRM companies as organizations and contacts as customers. A large CRM is imported over several runs. Existing people and agents are not changed;
new and solved tickets are logged on the contact’s CRM timeline (a note in HubSpot, a task in Salesforce).

Calendars and contacts: Google Workspace and Microsoft 365

Google Workspace: a service account key (JSON) with domain-wide delegation for contacts and calendar read access, and the user whose contacts you want to import.
Microsoft 365: the directory (tenant) ID, an app registration’s client ID and secret with the Contacts.Read and Calendars.Read application permissions (with admin consent), and the mailbox whose contacts you want to import.

Two actions:

Import contacts: the address book’s contacts become customers, and their company an organization.
Sync out-of-office: out-of-office events in each agent’s work calendar show up in workforce management as absences.