Intercom Connector

Who can do this: Owners, Admins, and Editors can add and manage project connectors. See Roles and Permissions for details.

Connect your Intercom account and build tools around your customer conversations. Custom support inboxes, churn risk boards, segment message launchers, and customer success dashboards that turn support data into team workflows.

What you can do

Access your customer data:

• View conversations with status and wait times
• Browse contact profiles and account details
• Read help center articles and engagement
• See segments, tags, and customer attributes

Build support tools:

• Shared inboxes sorted by priority or wait time
• Churn risk boards flagging at-risk accounts
• Segment message launchers for targeted campaigns
• Customer context dashboards for success teams

Take action:

• Reply to conversations from custom interfaces
• Send messages to specific segments
• Update contact attributes and tags
• Assign conversations to teammates

Two ways to connect

Intercom works with Sticklight at two levels, depending on what you’re building.

Connector (for building)

The Intercom connector lets Sticklight access your customer data while you build. Connect once and Sticklight can read your conversations, contacts, and segments to show you live data in the editor.

Use this for: Dashboards, churn boards, customer views, anything that displays your Intercom data.

API key (for live updates and messaging)

When you build something that needs fresh data after publishing or sends messages, like a segment launcher or reply interface, Sticklight needs your Intercom API key. This lets your published app read current data and take actions in Intercom.

Use this for: Live inboxes, message senders, reply interfaces, anything where your app writes to Intercom.

Sticklight prompts you for the API key when it’s needed. You don’t have to set it up in advance.

Available data

Once connected, your project can access:

Data	What you get
Conversations	Messages, status, wait time, assignee, tags
Contacts	Names, emails, company, plan, custom attributes
Segments	Segment names, filters, contact counts
Help center	Articles, collections, view counts
Teams	Team members, assignments, availability

Common use cases

Shared support inbox

A custom inbox built for your team’s workflow. Sort by wait time, show plan badges so you know who’s VIP, and let teammates claim conversations. Reply inline without switching to Intercom.

“Build a shared support inbox sorted by wait time. Show customer name, plan tier as a badge, and conversation preview. Add a claim button and an inline reply panel.”

Connection needed: Connector + API key

Churn risk board

A dashboard surfacing accounts that need attention. Flag customers with no recent login, open support tickets, or dropping usage. Sort by risk level and track follow-up status.

“Create a churn risk board showing accounts with no activity in 30 days, any open conversations, and usage below threshold. Make it sortable with a follow-up status column.”

Connection needed: Connector only

Segment message launcher

A focused tool for sending targeted messages. Choose from your real Intercom segments, see the live recipient count, compose your message, and send with confidence.

“Build a message launcher where I select an Intercom segment, see how many contacts will receive it, write my message, preview it, and send.”

Connection needed: Connector + API key

Customer context dashboard

A single view of everything you know about a customer. Conversation history, account details, plan information, and support tickets in one place. Perfect for success calls or escalations.

“Create a customer dashboard where I search by email and see their full profile, conversation history, current plan, and any open issues.”

Connection needed: Connector + API key

Connecting Intercom

Step 1: Connect the connector

You can connect from chat or from your project settings.

From chat:

“Connect my Intercom account”

From project settings: Open Settings, go to Connectors, and select Intercom.

When you start the connection:

1. Click Connect Account.
2. Log in to Intercom when the authorization window opens.
3. Select the workspace you want to connect.
4. Review the permissions Sticklight is requesting.
5. Click Authorize to complete the connection.

Once connected, Sticklight can access your Intercom data while you build.

Step 2: Add your API key (when needed)

If you’re building something that sends messages or needs live data after publishing, Sticklight enables Cloud Backend automatically. This provides the backend function needed to securely connect to Intercom. Then it prompts you for your Intercom API key.

To create an API key:

1. In Intercom, go to Settings → Integrations → Developer Hub
2. Create a new app or select an existing one
3. Go to Authentication and find your Access Token
4. Copy the token
5. Paste it into Sticklight when prompted

The key is stored securely and only used by your published app to read from and write to Intercom.

Message sending and privacy

Intercom data includes customer conversations, which can be sensitive. When building tools that display or act on this data:

• Limit access to team members who need it
• Preview before sending when building message launchers
• Consider read-only mode for dashboards that shouldn’t send messages
• Protect customer data by keeping support tools internal

Message-sending features should include confirmation steps so nothing goes out by accident.

What visitors see

When you publish your app, consider who will use it:

• Support team tools: Agents see conversations, customer details, and reply interfaces
• Success dashboards: CS teams see account health and risk indicators
• Internal operations: Managers see queue metrics and team performance

Customer conversations contain personal information. Keep Intercom tools internal to your team and restrict access appropriately.

Limitations

• Workspace-level access. The connector accesses one Intercom workspace per connection. For multiple workspaces, create separate projects.
• Permission-based. You can only access data your Intercom account has permission to view.
• API rate limits. Intercom limits API requests. High-frequency updates may be throttled.
• Message review. Sending messages to customers should include preview and confirmation steps.

FAQ

Does connecting Intercom cost anything?

No. Connecting is free. You only spend credits when you build something.

Will this change anything in my Intercom account?

Read-only dashboards don’t modify your data. If you build features that send messages or update contacts, those changes write to Intercom. You control whether messaging features are included.

What’s the difference between the connector and the API key?

The connector lets Sticklight read your Intercom data while you build. The API key lets your published app read fresh data and send messages. Dashboards only need the connector. Inboxes and message launchers need both.

Do I need to know how to code?

No. Describe what you want in plain language and Sticklight builds it. If you do write code, the files are there to open and edit.

Can I accidentally send messages to customers?

Message-sending features should include preview and confirmation steps. If you’re building read-only dashboards, use read-only mode to ensure no messages can be sent.

Is customer data private?

Customer conversations and contact details are sensitive. Keep your Intercom tools internal to your team and limit access to people who need it for their work.

Can I build tools for specific segments?

Yes. You can filter dashboards and tools to specific Intercom segments, showing only the customers relevant to each workflow.

Can I connect multiple Intercom workspaces?

Each project connects to one Intercom workspace. For multiple workspaces, create separate projects.