Skip to main content
Answered

How to block outbound webhooks if conversation did not originate from our application?

  • September 13, 2021
  • 3 replies
  • 20 views
M

Our webhooks is receiving requests from any conversation that originates from anywhere, even outside our messaging app. Our application keeps getting requests that we don't want. Is there a way to configure this to only get hits based on a particular service?

 

To clarify, we have a messaging application that talks to agents on Intercom. Turns out, even if agents on Intercom are talking to users that do not originate from our app, we get pinged. We just want to isolate the webhook to only receive messages to our application.

Best answer by Eric Fitz

Thanks for clarifying that for me @murali k​. While there is no direct way to attribute webhooks to either mobile or web, a workaround may be to use the "URL" attribute in the webhook data. This populates with a value for web, but remains blank for all other sources.

View original
Did this topic help you find an answer to your question?

Eric Fitz
Employee
Forum|alt.badge.img+5
  • Eric FitzEmployee
  • Employee
  • September 17, 2021

Hey @murali k​, just to confirm, you only want to listen for webhooks that come from your mobile app, and not your web platform?

M
  • Murali K
  • New Participant
  • September 20, 2021

yes

Eric Fitz
Employee
Forum|alt.badge.img+5
  • Eric FitzEmployee
  • Employee
  • September 21, 2021

Thanks for clarifying that for me @murali k​. While there is no direct way to attribute webhooks to either mobile or web, a workaround may be to use the "URL" attribute in the webhook data. This populates with a value for web, but remains blank for all other sources.

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings