TL;DRTo integrate Orbit webhooks with ngrok:
  1. Launch your local webhook. npm start
  2. Launch ngrok. ngrok http 3000
  3. Configure Orbit webhooks with your ngrok URL.
  4. Secure your webhook requests with verification.
This guide covers how to use ngrok to integrate your localhost app with Orbit by using Webhooks. Orbit webhooks can be used to notify an external application whenever specific events occur in your Orbit account. By integrating ngrok with Orbit, you can:
  • Develop and test Orbit 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 Orbit in real-time via the inspection UI and API.
  • Modify and Replay Orbit Webhook requests with a single click and without spending time reproducing events manually in your Orbit account.
  • Secure your app with Orbit 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: 
git clone https://github.com/ngrok/ngrok-webhook-nodejs-sample.git
cd ngrok-webhook-nodejs-sample
npm install
This will get the project installed locally. Now you can launch the app by running the following command: 
npm start
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!
  1. If you’re not an ngrok user yet, just sign up for ngrok for free.
  2. Download the ngrok agent.
  3. 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.
  4. Start ngrok by running the following command: 
    ngrok http 3000
  5. ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with Orbit). ngrok agent running

​
Step 3: Integrate Orbit

To register a webhook on your Orbit account follow the instructions below:
  1. Access the Orbit Home page and sign in using your Orbit account.
  2. On the Home page, click Workspace Settings at the left menu and then click Webhooks.
  3. On the Webhooks page, click + New Webhook.
  4. On the New webhook page, enter a name in the Webhook Name field, select a new activity is added to a member in the Event Subscription field, and then enter the URL provided by the ngrok agent to expose your application to the internet in the Webhook URL field (i.e. https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). orbit URL to Publish
  5. Click Create Webhook.

​
Run Webhooks with Orbit and ngrok

Orbit sends different request body contents depending on the event that is being triggered. You can trigger new calls from Orbit to your application by following the instructions below.
  1. Access the Orbit Home page, sign in, click Members at the left menu, and click one of your members.
  2. On the Member popup, click Actions and then click Add Activity.
  3. On the Add activity popup, select an activity in the Activity Type field, enter Test in the Title field, and then click Submit.
Confirm your localhost app receives an event notification and logs both headers and body in the terminal.

​
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:
  1. Send a test webhook from your service to generate traffic in your Traffic Inspector.
  2. Select the request you want to replay in the traffic inspector.
  3. Choose your replay option:
    • Click Replay to send the exact same request again
    • Select Replay with modifications to edit the request before sending
  4. Modify the request (optional): Edit any part of the original request, such as changing field values in the request body.
  5. 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 Orbit 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.
  1. Access the Orbit Home page, sign in, click Workspace Settings at the left menu, and then click Webhooks.
  2. Click Action (represented by the three dots icon) for your webhook and click Update.
  3. On the Update Webhook page, enter 12345 in the Webhook Secret field and click Save Changes.
  4. Create a traffic policy file named orbit_policy.yml, replacing {your webhook secret} with the value from the previous step: 
    on_http_request:
  - name: "Verify Orbit requests"
    actions:
      - type: verify-webhook
        config:
          provider: "orbit"
          secret: "{your webhook secret}"
  5. Restart your ngrok agent by running the command: 
    ngrok http 3000 --traffic-policy-file orbit_policy.yml
  6. Access Orbit Home page, sign in, and add a new activity to a member.
Verify that your local application receives the request and logs information to the terminal.