Resources · Make integration

BugHerd Make integrationAutomate BugHerd with Make.

What if every bug your clients pin on a website reached the right tool without anyone copying it? The BugHerd Make integration gives you 17 modules, 4 of them instant triggers. This guide is for agencies and product teams: link your account, then build a first working scenario.

Try the BugHerd integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BugHerd Make integration do for you?

The BugHerd Make integration links your BugHerd account to Make so that tasks, comments, attachments and projects move on their own. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search.

Feedback that lands where developers already work. Watch New Task Created fires the moment a reviewer pins a bug on a page, and the next module can push that task into the tool your developers open every morning.

Tickets from outside, filed into the right project. A support form or a client email can become a BugHerd task through Create a Task, so nothing lives only in an inbox. Later, Find a Task by External ID lets another system locate that same task again and Add a Comment to a Task posts the follow-up.

A clean record when work closes. Watch a Task Updated and Watch a Task Deleted tell Make when a task changes or disappears, which keeps a tracking sheet or a client report honest.

What the listed modules do not cover, Make an API Call can reach with the same connection. Before choosing a plan, read the Make review and the Make pricing guide. If you also weigh another tool, the n8n vs Make comparison sets out the criteria.

Connect

How do you connect BugHerd to Make?

  1. 01

    Copy your BugHerd API key

    You need an active BugHerd account. Inside BugHerd, open Settings, click General Settings and copy the API key shown on screen. Keep it at hand, Make asks for it in the next step.

  2. 02

    Add a BugHerd module in Make

    Log in to Make, add any BugHerd module to your scenario and click Create a connection. A connection is your BugHerd account linked to Make once, then reused by every BugHerd module.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several client accounts sit side by side. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Build your first scenario with BugHerd

GoalWhen another app sends an update about a known issue, Make finds the matching task in BugHerd and posts that update as a comment.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Here that first module belongs to the app sending updates, for example your help desk.

  2. 02

    Add Find a Task by External ID

    Click the + on the right, search for BugHerd and pick Find a Task by External ID. Link your account with Create a connection, then map the external ID coming from the first module.

  3. 03

    Post the update as a comment

    Add Add a Comment to a Task after the search. Map the task it found and the text of the update. Each item that flows between modules is called a bundle: here, one task.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received. If the search returned nothing, check the external ID you mapped before going further.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes minimum on the Free plan), then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

Which BugHerd events can start a scenario?

4 modules start a scenario when something happens in BugHerd. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BugHerd as soon as it happens.

BugHerd1Watch a Task Deleted

Watch a Task Deleted

Instant trigger

In Make“Triggers when a task is deleted.”

This trigger tells Make that a task has just been removed from BugHerd, so records kept elsewhere never point to feedback that no longer exists. It hands the deleted task to the next module as a bundle.

How it fires
instant, BugHerd calls Make through a webhook as soon as the task is deleted, with no schedule to wait for.
When to use it
you mirror BugHerd tasks in a spreadsheet or a project tool and want the matching row archived or flagged when someone clears a task.
Watch out
the task is already gone when Make hears about it, so a Get a Task placed after this trigger has nothing left to read.
BugHerd2Watch a Task Updated

Watch a Task Updated

Instant trigger

In Make“Triggers when a task is updated.”

Any edit on an existing task wakes your scenario up here. It is the trigger to pick when progress matters more than creation.

How it fires
instant, BugHerd pings Make through a webhook the moment a task is edited.
When to use it
a client asks to be told when their reported bug moves forward, and you want a message or a report line to follow each change without anyone typing it.
Watch out
an Update a Task in the same scenario edits the task again and, logically, fires this trigger once more, so never pair the two on the same task.
BugHerd3Watch New Comment Added

Watch New Comment Added

Instant trigger

In Make“Triggers when a new comment added.”

Conversations on a task often hold the real decision, and this trigger brings each new comment into Make as soon as it is posted. Use it to keep people outside BugHerd in the loop.

How it fires
instant, the app notifies Make through a webhook right after the comment is saved.
When to use it
a developer answers a client question on a task, and the account manager should see that answer in the team chat instead of logging in to BugHerd.
Watch out
an Add a Comment to a Task in the same scenario creates a new comment and restarts the flow, so keep those two apart.
BugHerd4Watch New Task Created

Watch New Task Created

Instant trigger

In Make“Triggers when a new task created.”

Every new piece of feedback becomes a starting point with this trigger: the moment a task appears in BugHerd, your scenario receives it with its details. Pick it when the arrival of new feedback is what matters.

How it fires
instant, BugHerd sends the new task to Make through a webhook as soon as it exists.
When to use it
a website is in client review and every pinned bug should also reach the developers' board or a triage channel without a manual copy.
Watch out
a Create a Task later in the same scenario would feed this trigger again and loop, so send new tasks to another app instead.
Modules

What can Make do in BugHerd?

BugHerd gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

BugHerd1

Add a Comment to a Task

Action

In Make“Adds a comment to a specific task.”

Posts a message on a chosen task, so whoever works on it reads the latest news right where the bug is pinned. It keeps the thread in BugHerd instead of scattered emails.

When to use it
a support tool or a deploy tool has news about an issue and the developer should see it on the task itself.
Watch out
it needs the task, so place a Get a Task or a Find a Task by External ID before it.
BugHerd2

Create an Attachment on a Task

Action

In Make“Creates an attachment on a specific task.”

Adds a file to an existing task, so the screenshot, log or document that explains a bug stays next to it. Nobody has to hunt for the evidence in a shared drive.

When to use it
a client sends a file by email or form after reporting a bug, and it belongs on that task.
Watch out
on the Free plan Make handles files up to 5 MB, so large recordings may not pass.
BugHerd3

Create a Project

Action

In Make“Creates a new project.”

Opens a brand new BugHerd project from Make, which saves a setup step each time a new website or client arrives. The project is ready for tasks as soon as the module runs.

When to use it
a deal is won in your CRM and the review space for that client site should exist before kickoff.
Watch out
test it with Run once on a dummy name first, then remove the test project from BugHerd.
BugHerd4

Create a Task

Action

In Make“Creates a task on a specific project.”

Files a new task inside a project you pick, turning a request from outside BugHerd into something your team can track. Make lists your projects once the connection exists.

When to use it
a client fills a form or writes to support about a bug, and it should join the BugHerd backlog.
Watch out
never pair it with Watch New Task Created in the same scenario, or each new task restarts the flow.
BugHerd5

Delete an Attachment From a Task

Action

In Make“Deletes a specific attachment from a task specified by ID.”

Removes one file from a task, identified by its ID, which helps when an outdated screenshot or a sensitive document should no longer sit there. It targets one attachment, not the task.

When to use it
a client asks to withdraw a document they uploaded by mistake.
Watch out
a deleted attachment does not come back, so run Get an Attachment from a Task first and check you hold the right ID.
BugHerd6

Delete a Project

Action

In Make“Deletes a project specified by ID.”

Erases a whole BugHerd project by its ID. Your workspace stays tidy once a website ships and its review space serves no purpose anymore.

When to use it
a project is marked closed in your CRM or project tool and the matching BugHerd project should go too.
Watch out
this one cannot be undone, so add a filter or a Get a Project before it and test on a throwaway project.
BugHerd7

Get an Attachment from a Task

Action

In Make“Gets a specific attachment from a task specified by ID.”

Reads one attachment of a task by its ID, so a later module can store, forward or check that file. Nothing changes in BugHerd when it runs.

When to use it
a task is resolved and its screenshots should be archived in the client folder of your drive.
Watch out
it needs both the task and the attachment ID, so map them from an earlier module rather than typing them.
BugHerd8

Get a Project

Action

In Make“Retrieves a project specified by ID.”

Pulls the details of one project from its ID, which gives later modules the project name and context a bare task lacks. It only reads and changes nothing.

When to use it
after Watch New Task Created, to tell the developers which client site the bug belongs to before routing it.
Watch out
the ID must come from a previous module, since this module finds nothing by name.
BugHerd9

Get a Task

Action

In Make“Gets a task specified by ID.”

Fetches the full content of a task from its ID, handy when a trigger or another app only passes the reference. The next modules then work with the complete task.

When to use it
a comment arrives through Watch New Comment Added and your message should quote the task it belongs to.
Watch out
after Watch a Task Deleted there is no task left to read.
BugHerd10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the BugHerd API with the connection you already set up, the way out when none of the ready modules does what you need.

When to use it
you need a BugHerd action missing from this page and the API documentation of BugHerd describes it.
Watch out
you write the request yourself, so it asks for more care than a ready module, and a test with Run once first.
BugHerd11

Update a Project

Action

In Make“Updates a project specified by ID.”

Changes an existing project, picked by its ID, so BugHerd reflects what your other tools already know about that client site.

When to use it
a project is renamed or handed to another team in your project tool and BugHerd should follow.
Watch out
map the ID from Get a Project or a trigger so the wrong project is never edited.
BugHerd12

Update a Task

Action

In Make“Updates a task specified by ID.”

Edits a task you point to by ID, letting another system move a bug forward in BugHerd without anyone clicking through it. Your board stays in step with the real work.

When to use it
a fix is deployed or a ticket closes elsewhere and the matching BugHerd task should change status.
Watch out
placed in a scenario that starts with Watch a Task Updated, it fires that trigger again and loops.
BugHerd13

Find a Task by External ID

Search

In Make“Finds a task by the external ID.”

Looks up a task through the external ID another system gave it, so an outside tool can find its BugHerd twin without storing BugHerd IDs. It is the one search module of the app.

When to use it
your help desk or issue tracker sends an update and must reach the matching task.
Watch out
a search can return no task, one or several, so test with Run once before chaining an update.
Need help

Need help automating BugHerd with Make?

A person reads every message.

FAQ

BugHerd and Make: common questions

01Is the BugHerd Make integration free?
Yes, on the Make side. BugHerd is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, or operations, each month. BugHerd itself needs its own active account, billed on its side.
02What do you need to connect BugHerd to Make?
An active BugHerd account and its API key. In BugHerd, go to Settings, then General Settings, and copy the key shown on screen. In Make, add a BugHerd module, click Create a connection, give it a name if you like, and paste the key. For the four triggers, which are instant, click Create a webhook first and then Create a connection. The connection is saved once and every BugHerd module in your scenarios reuses it.
03Do BugHerd triggers in Make fire instantly?
Yes. All four BugHerd triggers are instant: Watch New Task Created, Watch a Task Updated, Watch New Comment Added and Watch a Task Deleted. BugHerd calls Make through a webhook as soon as the event happens, so the scenario does not wait for a schedule. That is the lightning badge on the module in the editor. The 15 minute default schedule only applies to scenarios that start with a scheduled module, such as one from another app.
04What if a BugHerd module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the BugHerd API with the connection you already have, so you are not limited to the ready modules. You write the request yourself from the BugHerd API documentation, then test it with Run once. The Make documentation for this app is marked as AI generated from the official BugHerd documentation, so verify important details with BugHerd before relying on them.
05Should you use Make or n8n for BugHerd?
It depends on the tool you already run. On Make, BugHerd comes with 17 ready modules: 4 instant triggers for tasks and comments, 12 actions on tasks, projects and attachments, and 1 search by external ID, plus Make an API Call for the rest. The same app often has an n8n node too, so check whether it covers the events you need before choosing. Compare them on the events and actions your process uses, not on the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations