Integrations

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Integrations help Custory keep customer context connected. They reduce copy-pasting and make it easier to see why product work matters.

​

Common integration types

​

Team conversations

Connect tools where customer problems are discussed. Examples:

• Slack
• Discord

Use these to turn team discussions into durable insights or follow-up work.

​

Product work

Connect tools where the team plans and ships. Examples:

• Linear
• Jira
• GitHub

Use these to keep issues and tasks linked back to the customer journey.

​

Customer and product signals

Connect tools that show what customers are doing or saying. Examples:

• PostHog
• Stripe
• Intercom

Use these to understand behavior, revenue signals, support pressure, and churn risk.

​

Knowledge and design

Connect tools where research, notes, and designs live. Examples:

• Notion
• Figma
• Miro
• Google Drive

Use these to keep supporting context close to the journey.

​

Before connecting a tool

Ask:

• What useful signal lives there?
• Which journey should it support?
• Who should see or own the follow-up?
• What should happen when new context appears?

This helps integrations stay useful instead of becoming noise.