Report website issues directly from your browser

Updated 2 years ago by Andrew White

Report website issues, or bugs, without ever leaving your browser. Using Push by Zapier, you can capture the exact URL where the issue was found, as well as comments from the user who experienced it.

This Zap can be completed on Zapier's free plan

Set up

To begin: Navigate to the Chrome store and download the Zapier Chrome extension. Once you have downloaded the chrome extension, you are ready to start!

Click on the Chrome extension and select the orange "Make a Push Zap!" button. 

Choose "New Push with fields" as the trigger. Each time the button is pushed, these fields will be used to create the zap. Connect your atSpoke account to Zapier, and click continue.

Make sure to choose "Push with fields" so that fields can be mapped in the next step.

Create the fields that need to be completed each time the button is pushed.

  • Use the arrows on the right to reorder the fields.
  • Use the "+" and "-" to add or remove fields.

When you have added all the required fields, press "Continue"

When a user selects the Zapier extension from their browser, a dropdown with these fields will show.

Pull in samples and test to confirm your trigger is working.


Choose "+ Add a step" and search for atSpoke. From the available actions choose "New request".

Choosing "New request" means that each time the Zapier button is pushed, a new request will be created from this template.

Press "Continue" and connect your atSpoke instance to Zapier.

Request template

Create a Template using the information from step 1.

  1. Add a subject
  2. Format the Request body as needed.
  3. Choose which team handles these requests
  4. When you're finished, choose "Continue"
Select the button to use attributes from step 1.


Press continue, and send a test zap to atSpoke. You should expect to see a request created in atSpoke. Make sure to review your template for any errors, or updates that need to be made.

Once your Zap works the first time, make sure the toggle turned on so this triggers going forward.

How did we do?

Powered by HelpDocs (opens in a new tab)