Integrate with Zapier

In short, Zapier is the place to go, if you need to integrate two or more online systems. In this article we use an integration point provided by and Zapier called a trigger. A trigger is (as the name suggest) something that triggers an action in Zapier. In case of, the trigger available is when new messages are logged to your log. Actions exists on the other side of the integration and tells Zapier what to do every time a trigger is fired. Hundreds of actions exist, in this example we use the GitHub action to create a new issue every time a new message is logged.

Create a new account on Then click the Make a New Zap button. The create new Zap page is shown:

Choose a trigger and action

Select in the Choose a Trigger app… dropdown and then select New Error in the Choose a Trigger… dropdown. In the Choose an Action app… select GitHub and select Create Issue in the Choose an Action… dropdown.

Choose a trigger and action

This configuration tells Zapier to create a new issue at GitHub, every time a new error is logged in The action could be one of the hundreds of other integrations available at Zapier. Click Continue.

In Section 2 select the Connect a different Account and input a name and the log id of the log you want to integrate:

Connect your account

Authorize your GitHub account (or whatever integration you’ve selected in the action step) and click Continue. Step 4 isn’t mandatory, but here you will be able to setup additional constraints to the Zap. If you’re using for other than errors, you can tell Zapier only to create a new GitHub issue when the message is an actual error:

Setup filter

In Step 5 you specify how the new issue should create created. In this example I’ve chosen the GitHub project for our open source client. For the title, I use two of the variables available from the action. For a complete list of variables, click the Insert button next to each textbox. The variable will look something like this “MyApp: An error occurred”. The issue body contains the detail of the error (typically a stacktrace). Finally, I’ve selected bug as a label.

Match up Error to GitHub issue

Test the Zap and hit Continue:

Test this Zap

Finally, name your Zap and click the Turn Zap on button:

Name and turn this Zap on

When future errors are logged in your log, a GitHub issue is automatically created. How awesome is that!

This article was brought to you by the team. is the best error management system for .NET web applications. We monitor your website, alert you when errors start happening and help you fix errors fast.

See how we can help you monitor your website for crashes Monitor your website