Diffy and Zapier: Turn Visual Bugs into Jira, Trello or Asana Tickets

Diffy shows you what changed between two sets of screenshots. When one of those changes is a real bug, the next step is usually a ticket for whoever will fix it. With the Zapier integration, you mark the change as a bug in Diffy and the ticket appears in Jira, Trello, Asana, Basecamp or whichever tracker your team uses, with a link back to the change.

There is no copying screenshots into a ticket by hand, and the link works for people who don’t have a Diffy account.

How it works

1. You connect Diffy to Zapier once, with a Zap whose trigger is Diffy → New Ticket and whose action creates an issue, card or task in your tracker.
2. In a Diffy comparison, you review the changes as usual. On a change that is a bug, you choose BUG & create ticket.
3. Diffy marks the change as a bug and opens a Create ticket form, filled in with the comparison name and a share link to that change. You can edit both.
4. When you send it, Diffy passes the name and description to your Zap, and Zapier creates the ticket in your tracker.

Once every change in a comparison has been reviewed, a Create ticket link also appears at the top of the comparison, so you can file one ticket that covers the whole comparison instead of one per change.

What you need

• A Diffy project with the pages and environments you compare. If you’re new to Diffy, see what visual regression testing covers first.
• A Diffy API key from the Keys page. API access comes with every paid plan, and only the team’s primary owner can see the Keys page.
• A Zapier account. A two-step Zap like this works on Zapier’s free plan, unless your tracker is one of Zapier’s premium apps.
• Access to your tracker from Zapier, so it can create issues in the right project or board.

Step 1: Create the Zap and choose the Diffy trigger

In Zapier, create a new Zap and search for Diffy as the trigger app. If it doesn’t show up, open the Diffy invite link first, then search again. Choose the New Ticket trigger event.

If you’d rather start from a template, Zapier has ready-made Zaps for Diffy with Jira Software Cloud, Trello and Basecamp.

Step 2: Connect your Diffy account

When Zapier asks for an account, paste your Diffy API key. Zapier uses it to register the Zap with your Diffy project, so Diffy knows where to send tickets.

Step 3: Pick the Diffy project

In the trigger settings, choose the Diffy project that should send tickets. Each Zap is linked to one project, so create one Zap per project you want to connect.

Step 4: Add the action in your tracker

Add your tracker as the action, for example Jira Software Cloud → Create Issue, Trello → Create Card or Asana → Create Task, and choose the project, board or list the tickets should go to. Then map the two fields Diffy sends:

• Name → the issue summary or card title
• Description → the issue description or card description

Add anything else your tracker needs, such as an issue type, a label like visual-regression or an assignee.

Step 5: Publish the Zap

Test the step if you like, then publish the Zap. Back in Diffy, open any comparison: the BUG & create ticket option is now available on each change. Before the Zap is connected it shows as disabled, with a pointer to the setup docs.

Creating tickets from a comparison

Open a comparison and go through the changes. For each one, Diffy offers three verdicts: BUG, OK and False positive. The arrow next to BUG opens BUG & create ticket.

The form that opens has two fields:

• Name, filled in with the comparison name. It’s worth adding the page and what’s wrong, such as “Pricing page: plan cards overlap at 768px”.
• Description, filled in with a share link to the change at that page and breakpoint. Add any notes for the developer above or below it.

When you click Create ticket, the ticket appears in your tracker within moments. When the developer opens the link, they see the before and after in Diffy, with the change highlighted, without needing an account.

For a comparison with several related problems, review everything first, then use the Create ticket link at the top of the comparison to file a single ticket with a link to the whole comparison.

FAQ

Which trackers can Diffy create tickets in? Any app Zapier can create a task, card or issue in. Zapier has ready-made templates for Jira Software Cloud, Trello and Basecamp, and the same Zap works with Asana, GitHub issues, Linear, ClickUp and others: only the action step changes.

What goes into the ticket? Diffy sends two fields: a name, which defaults to the comparison name, and a description, which defaults to a share link to the change in Diffy. You can edit both before you send the ticket, and you map them to your tracker’s fields in the Zap.

Can people without a Diffy account open the link in the ticket? Yes. The description contains a Diffy share link, which opens the change without signing in, so a developer or a client can see the before and after straight from the ticket.

Can I connect several Diffy projects? Yes, with one Zap per project. You choose the Diffy project in the Zap’s trigger. Each project sends tickets to one Zap, so turning on a second Zap for the same project replaces the first.

Which Diffy plan do I need? Zapier connects to Diffy with an API key, and API access comes with every paid Diffy plan. On the Zapier side, a two-step Zap like this one works on Zapier’s free plan, as long as your tracker isn’t a premium app on Zapier.

Get started

Create a Diffy account, run a first comparison of staging against production, and connect Zapier when you find your first bug. Want results in your pull requests too? See GitHub Actions and GitLab CI, or browse all Diffy integrations.