No webhook when a new conversation is created on Intercom Inbox | Community
Skip to main content
Answered

No webhook when a new conversation is created on Intercom Inbox

  • April 29, 2026
  • 2 replies
  • 105 views

Andrii Fedyk
Forum|alt.badge.img+1

Intercom has multiple conversation-related webhooks.

When a new conversation is created in the Intercom Inbox, the `conversation.*` topics are not triggered.

Below the screenshots on how a new conversation is created.

 

 

Thanks for help!

Best answer by Roy

Hello ​@Andrii Fedyk 👋,

 

How are you doing? Roy here from Intercommunity, stepping in to help you out with your webhook integration.
 

When dealing with conversation creation in Intercom, there are actually two distinct webhooks you need to configure in your backend depending on the origin of the message:

conversation.admin.single.created

An Admin/Agent initiates a new outbound message to a user.

conversation.user.created

A new inbound message is received from a user or lead.

 

Based on the screenshots you’ve provided, it appears an Agent or Admin is creating a conversation with a specific user. In this scenario, your webhook endpoint (whether you're routing the POST request through an Express.js server, a Django app, or an AWS Lambda function) needs to be listening for the conversation.admin.single.created event.
 

I suspect your current event listener is monitoring conversation.user.created, which will only fire when the user initiates the chat with your team. Simply updating the topic your API subscribes to in the Intercom Developer Hub should resolve this, ensuring your backend catches the correct JSON payloads for outbound messages.
 

I hope this points you in the right direction! Please let me know if you need any more help - I'm more than happy to assist.


Have a Londonful Day Ahead 💂

 

Cheers,
Roy 🇬🇧

2 replies

Roy
Top Expert ✨
Forum|alt.badge.img+7
  • Top Expert ✨
  • Answer
  • April 30, 2026

Hello ​@Andrii Fedyk 👋,

 

How are you doing? Roy here from Intercommunity, stepping in to help you out with your webhook integration.
 

When dealing with conversation creation in Intercom, there are actually two distinct webhooks you need to configure in your backend depending on the origin of the message:

conversation.admin.single.created

An Admin/Agent initiates a new outbound message to a user.

conversation.user.created

A new inbound message is received from a user or lead.

 

Based on the screenshots you’ve provided, it appears an Agent or Admin is creating a conversation with a specific user. In this scenario, your webhook endpoint (whether you're routing the POST request through an Express.js server, a Django app, or an AWS Lambda function) needs to be listening for the conversation.admin.single.created event.
 

I suspect your current event listener is monitoring conversation.user.created, which will only fire when the user initiates the chat with your team. Simply updating the topic your API subscribes to in the Intercom Developer Hub should resolve this, ensuring your backend catches the correct JSON payloads for outbound messages.
 

I hope this points you in the right direction! Please let me know if you need any more help - I'm more than happy to assist.


Have a Londonful Day Ahead 💂

 

Cheers,
Roy 🇬🇧


Andrii Fedyk
Forum|alt.badge.img+1
  • Author
  • Active User
  • May 7, 2026

Thanks, the webhook `conversation.admin.single.created` precisely covers the case.