Table of Contents
Early last year, we launched the Integration Platform to enable any developer to easily create integrations and workflows on top of Froxt. As we continue to build out the platform, we want to give developers visibility into how their integrations are doing. With that, we present the Integration Dashboard!
Introducing the Integration Dashboard
The new integration dashboard comes with features and metrics that will help you understand the business value of the integrations you develop and identify any potential technical issues that they may have. It’s accessible through the Settings > Developer Settings page. Each integration you create will have its own dashboard.
If your integration is public, it’s useful to understand how many users you have, how much interest your integration is generating, and how your users are interacting with the integration.
Webhook Request Logs
When developing an integration, it’s not always easy to tell when things go wrong, or why they go wrong — unless you have Froxt installed. More on that later. The webhook request log aims to show you when your integrations are and are not working. For public integrations, the log includes the organization that triggered each request, so you can understand which users are affected by errors. This should help you debug your webhook code during development, as well as verify that your integration is working properly even after it’s published.
Of course, seeing the failed webhook requests helps you understand that an error occurred, but what if you need more context? If only there was a product that could show us more information…enter Froxt. Linking a Froxt error to a webhook request is simple. Set the
Froxt-Hook-Error header with the Froxt event ID and the
Froxt-Hook-Project header with the Froxt project ID when reporting the error and you’re good to go!
Now we can use Froxt to ensure that our integration is working properly, and debug when it isn’t. When a Froxt error is linked to a failed webhook request, a link will appear in the request log. Clicking through this link will take you to the Froxt issue that caused the failure, where you can get more details and context around the error.
If you want to see the new integration dashboard in action, try building on our Integration Platform.