Skip to main content

Frame.io Webhooks

TL;DR

To integrate Frame.io webhooks with ngrok:

  1. Launch your local webhook. npm start
  2. Launch ngrok. ngrok http 3000
  3. Configure Frame.io 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 Frame.io by using Webhooks. Frame.io webhooks can be used to notify an external application whenever specific events occur in your Frame.io account.

By integrating ngrok with Frame.io, you can:

  • Develop and test Frame.io 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 Frame.io in real-time via the inspection UI and API.
  • Modify and Replay Frame.io Webhook requests with a single click and without spending time reproducing events manually in your Frame.io account.
  • Secure your app with Frame.io 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!

  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:

    Loading…

  5. ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with Frame.io). ngrok agent running

Step 3: Integrate Frame.io​

To register a webhook on your Frame.io account follow the instructions below:

  1. Access Frame.io and sign in using your Frame.io account.

  2. In the same browser, access Frame.io Developer.

  3. On the top menu of the developer site, click DEVELOPER TOOLS and then click Webhooks.

  4. On the Webhooks page, click Create a Webhook.

  5. On the Create a new webhook page, enter a name in the NAME field, and in the 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). Frameio URL to Publish

  6. Select your team for the TEAM field, click the created checkbox for Projects under the EVENTS section, and then click Submit.

Run Webhooks with Frame.io and ngrok​

Frame.io sends different request body contents depending on the event that is being triggered. You can trigger new calls from Frame.io to your application by following the instructions below.

  1. In the same browser, access Frame.io, and then click + close to your team name on the left menu.

  2. On the New Project popup, enter a project name and then click Create Project.

    Confirm your localhost app receives the create-project event notification and logs both headers and body in the terminal.

Optionally, you can verify the log of the webhook call in Frame.io:

  1. In the same browser, access Frame.io Developer.

  2. On the top menu of the developer site, click DEVELOPER TOOLS and then click Webhooks.

  3. On the Webhooks page, click View logs close to your webhook.

  4. On the Webhook Logs page, click View details and confirm Webhook Logs

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.

info

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 Frame.io 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 Frame.io Developer.

  2. On the top menu of the developer site, click DEVELOPER TOOLS and then click Webhooks.

  3. On the Webhooks page, click Copy to copy the Secret value.

  4. Create a file named frameio_policy.yml, replacing {your webhook secret} with the value you have copied before (See Integrate ngrok and Frame.io.):

    Loading…

  5. Restart your ngrok agent by running the command:

    Loading…

  6. Access Frame.io and create a new project.

Verify that your local application receives the request and logs information to the terminal.