Runscope API Monitoring    Learn More →

Posts filtered by tag: webhooks

Customizing Slack Notifications from Runscope using AWS Lambda

By Sam Aybar on .

Runscope gives you many options in terms of how you can be notified when your APIs are down. Whether you use email, Slack, PagerDuty, Microsoft Teams, or want to build your own solution using Webhook notifications, Runscope can ensure your team is notified quickly using your channel (or channels!)

We’ve had some customers ask about how they could customize their Slack notifications. We’ve tried to make these notifications as helpful as we can, but we recognize that every team has their own unique needs.

Using advanced webhook notifications, you can build your own customizable Slack alerts. whether you want to include a custom message, a link to another resource, or some other useful information from your team, a custom alert allows you to tailor Runscope to your team's needs.  To help you do this, we created a walkthrough video which you can find here […]

Read More →

Categories: tutorial, integrations, howto

How Trustpilot Leverages Runscope Webhooks and Custom Slack Notifications

By Heitor Tashiro Sergent on .

Trustpilot is a review platform where people can read, write, and share reviews for all kinds of businesses. They have also been Runscope users since 2015, and we have featured them in other blog posts, such as how they monitor over 600 microservices.

One of the most important parts of API monitoring is getting notified when something breaks. Trustpilot uses Slack as their main communication hub, and so they rely on notifications that are sent from Runscope to Slack in case something breaks.

The default Runscope-Slack integration was enough for the Trustpilot team for a while. They made sure to use the threshold feature to only receive notifications after a test failed 3 times in a row, and again when the test returns passing, to control the overall number of notifications they would get.

But as their architecture evolved, and their Runscope usage grew, the amount of notifications grew as well. Add those up with other 3rd-party services, and they really started to build up. And getting too many alerts can be just as bad as getting zero alerts. The team started suffering from notification fatigue […]

Read More →

Categories: apis, community, customers, debugging, integrations, monitoring

How To Send Runscope Webhook Notifications to Google Hangouts Chat with EventN

By Sam Aybar on .

I’ve written before about how you can use webhooks with Runscope to extend the functionality of Runscope. In case you missed that post, Runscope has a number of built-in integrations, but some users want custom notifications with apps that we may not currently support. Webhook notifications are POST requests that are made at the completion of a test, and include a payload with details about the test run. If you can listen for these notifications, you can write your own code to deliver Runscope notifications anywhere that has an API you can use.

One service we don’t yet have a built-in integration is Google Hangouts Chat, the GSuite tool that facilitates group communication. In this blog post, I am going to describe how you can integrate Runscope with Hangouts Chat so you can get your team notified about Runscope tests in this GSuite tool.

Here is a snippet of what the webhook […]

Read More →

Categories: tutorial, product, integrations

Capturing Webhooks with Google Sheets

Capturing Webhooks with Google Sheets

By Sam Aybar on .

Runscope has a number of different integrations that allow you to leverage other tools in conjunction with your Runscope API monitors. However, for tools that are not included in our list of built-in integrations, we allow you to use Webhook notifications to automate your process. Webhook notifications are POST requests that are made at the completion of a test, and include a payload with details about the test run.

Runscope has two options for webhooks:

  • Basic Webhooks: fired on completion of every test run. They can be activated in your test environment settings -> Webhooks.
  • Custom Webhooks: you can specify failure only for a threshold of consecutive failures (3, for example) before sending the POST request. They can be added by going to Connected Services and setting the required parameters, and then activated in your test environment settings -> Integrations.

Either way, Runscope makes it easy for you to build your own integrations. However, receiving a webhook requires some piece of infrastructure that will receive and process the POST request, and some customers might not have their own infrastructure readily available, or the resources to create custom endpoints.

In this blog post, I’m going to walk through using Google Sheets as a quick alternative to listen for webhook notifications. [...]

Read More →

Categories: tutorial

Announcing Microsoft Teams Integration

By Heitor Tashiro Sergent on .

At the beginning of November, Microsoft joined the chat-based workspace apps with Microsoft Teams to compete with Slack, HipChat, and others. It's fully integrated with Office 365, and has features that users of other apps have come to know and love such as bots and connectors, and some new cool ideas like tabs.

Here at Runscope, we know that regardless of the chat application your company uses, monitoring your APIs and being quickly notified of any errors is important...

Read More →

Categories: announcements, integrations, monitoring

Monitor Your Webhook Workflows with New Incoming Requests for API Tests

By John Sheehan on .

API testing and monitoring has traditionally focused solely on outbound requests that simulate what a client of a particular API or endpoint would experience. But APIs are increasingly becoming a two-way conversation, with data flowing into apps asynchronously based on events happening (e.g. GitHub commits, Twilio text messages received, bots receiving requests, etc.).

The most popular way this occurs is via a pattern known as webhooks. Testing them can be difficult...

Read More →

Categories: announcements, monitoring, testing

Everything is going to be 200 OK®