Intercom Webhooks
To integrate Intercom webhooks with ngrok:
This guide covers how to use ngrok to integrate your localhost app with Intercom by using Webhooks. Intercom webhooks can be used to notify an external application whenever specific events occur in your Intercom account.
By integrating ngrok with Intercom, you can:
- Develop and test Intercom webhooks locally, eliminating the time in deploying your development code to a public environment and setting it up in HTTPS.
- Inspect and troubleshoot requests from Intercom in real-time via the inspection UI and API.
- Modify and Replay Intercom Webhook requests with a single click and without spending time reproducing events manually in your Intercom account.
- Secure your app with Intercom validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
Step 1: Start your app
For this tutorial, we'll use the sample NodeJS app available on GitHub.
To install this sample, run the following commands in a terminal:
Loading…
This will get the project installed locally.
Now you can launch the app by running the following command:
Loading…
The app runs by default on port 3000.
You can validate that the app is up and running by visiting http://localhost:3000. The application logs request headers and body in the terminal and responds with a message in the browser.
Step 2: Launch ngrok
Once your app is running successfully on localhost, let's get it on the internet securely using ngrok!
-
If you're not an ngrok user yet, just sign up for ngrok for free.
-
Go to the ngrok dashboard and copy your Authtoken.
Tip: The ngrok agent uses the auth token to log into your account when you start a tunnel. -
Start ngrok by running the following command:
Loading…
-
ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with Intercom).
Step 3: Integrate Intercom
To register a webhook on your Intercom account follow the instructions below:
-
Access the Intercom Home page, and sign in using your Intercom account.
-
On the left menu, click your avatar icon and then click Settings. Tip: The avatar icon is below the What's new bell icon. If your avatar icon doesn't appear, zoom out on the page.
-
In the Settings menu, expand the Apps & Integrations section and then click Developer Hub. Tip: If the Developer Guidelines popup appears, accept the guidelines by clicking Accept and Continue.
-
In the Developer Hub page, click New App.
-
In the New app popup window, provide a name for the app, select the appropriate workspace in which you work, keep Internal integration selected, and then click Create app.
-
In your app page, click Webhooks under the Configure section of the left menu.
-
In the Your request endpoint URL field enter the URL provided by the ngrok agent to expose your application to the internet (i.e.
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app
). -
In the Webhook topics, select contact.user.created and then click Save.
After you add a webhook to your Intercom account, Intercom will submit a test post request to your application through ngrok. Confirm your localhost app receives this test notification in the terminal.
-
Optionally, in the Intercom Webhooks page, you can click Send a test request to resend this test post request to your application.
Run Webhooks with Intercom and ngrok
Because you've selected the contact.user.created event, you can trigger new calls from Intercom to your application by following the instructions below:
-
In the same browser, access Intercom Home page, and then click the Contacts icon.
-
On the left menu, click New, click New users or leads, and then click Create new user.
-
In the Create a new user popup window, provide a Name, an Email, a User UI, and then click Create a user.
Confirm your localhost app receives the create user event notification and logs both headers and body in the terminal.
Tip: Intercom sends different request body contents depending on the event you select during the webhook registration.
Inspecting requests
ngrok's Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Click on any request to view detailed information about both the request and response.
By default, accounts only collect traffic metadata to avoid exposing secrets. You must enable full capture in the Observability section of your account settings to capture complete request and response data.
Use the traffic inspector to:
- Validate webhook payloads and response data
- Debug request headers, methods, and status codes
- Troubleshoot integration issues without adding logging to your app
Replaying requests
Test your webhook handling code without triggering new events from your service using the Traffic Inspector's replay feature:
-
Send a test webhook from your service to generate traffic in your Traffic Inspector.
-
Select the request you want to replay in the traffic inspector.
-
Choose your replay option:
- Click Replay to send the exact same request again
- Select Replay with modifications to edit the request before sending
-
Modify the request (optional): Edit any part of the original request, such as changing field values in the request body.
-
Send the request by clicking Replay.
Your local application will receive the replayed request and log the data to the terminal.
Secure webhook requests
The ngrok signature webhook verification feature allows ngrok to assert that requests from your Intercom webhook are the only traffic allowed to make calls to your localhost app.
Note: This ngrok feature is limited to 500 validations per month on free ngrok accounts. For unlimited, upgrade to Pro or Enterprise.
This is a quick step to add extra protection to your application.
-
Access the Intercom Developer Hub page, click your app name, and then click Basic information on the left menu.
-
In the Basic information page, copy the Client secret value.
-
Create a file named
intercom_policy.yml
, replacing{your client secret}
with the value you copied before:Loading…
-
Restart your ngrok agent by running the command:
Loading…
-
Access the Intercom Home page and create a new contact.
Verify that your local application receives the request and logs information to the terminal.