BugHerd Zapier integrationAutomate BugHerd with Zapier.
The BugHerd Zapier integration brings 4 triggers, 5 actions and 1 search, and it runs on the free plan. Three of those triggers are instant. Here is what each operation does for a web team, what it costs in tasks, and where a BugHerd Zap trips up.
Verified Trustpilot reviews · AI, automation & growth agency
What the BugHerd Zapier integration does for you
BugHerd is a visual feedback tool for websites: clients and testers pin notes straight onto the page, and each note becomes a task to track. Connected to Zapier, BugHerd can start an automation as soon as a task or comment appears, and it can receive tasks, comments and files sent from your other tools.
Three outcomes make the setup worth it. Feedback acknowledged right away: Task Created starts the Zap and Add a Comment to a Task tells the client their note was received. Bugs from other channels on the right page: a report from your help desk or a form becomes a BugHerd task through Create a New Task, and Find Task by External Id lets a later step update the same task. Status kept in step: Task Created or Updated tells another tool when a task changes, and Update a Task brings changes back the other way.
Limits worth knowing: no visible action deletes anything in BugHerd, and there is no trigger for a new attachment. Project Created is the one polling trigger, so on the free plan a new project can wait up to 15 minutes before the Zap sees it. The three task and comment triggers, on the other hand, are instant whatever your plan.
The same app exists on Make: the BugHerd Make integration covers it there, and Make vs Zapier is there if you are still choosing a platform.
Zapier words in one minute
Seven terms come back on every Zapier page. Here they are once, in plain English, so the rest reads easily.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event.
- Action
- What the Zap does once it has started: the step that creates, adds or updates something for you.
- Task (Zapier)
- The unit Zapier bills: one action your Zap completed successfully. Not to be confused with a BugHerd task.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so later steps can use what it found.
What a BugHerd Zap really costs
BugHerd is not a premium app, so it works on Zapier's free plan. The free plan only builds two-step Zaps, though: one trigger and one action.
- Free plan100 tasks per month, unlimited Zaps
- Free plan stepsOne trigger and one action
- BugHerd on freeYes, not a premium app
- BilledEach successful action, never the trigger
The trigger never costs a task, and Zapier's checks for new projects cost nothing either. Each action that succeeds counts once; a failed one is not billed. A Zap that adds a comment to every new task uses one task per BugHerd task. Add a filter or Find Task by External Id and it becomes a multi-step Zap, which needs a paid plan. The interval grid below only concerns Project Created; the three other triggers are instant.
Connect your BugHerd account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your BugHerd account linked once, then reused by every step that touches BugHerd.
- 02
Pick BugHerd and confirm
Search for BugHerd in the dialog, select it and click Add connection. You need a BugHerd account at this point, with the projects the Zap will watch already shared with you.
- 03
Sign in and grant access
Log in to BugHerd in the tab that opens and allow Zapier in. If the Zap will add comments, files or tasks to projects you do not own, your user needs write access to them.
Your first Zap: acknowledge every new piece of feedback
GoalEach time a client or tester pins a new task in the chosen BugHerd project, the task gets a comment saying the team has seen it.
- 01
Set the trigger
Create a Zap, choose BugHerd and the Task Created event, select your connection, then pick the Project to watch. This trigger is instant: the editor shows a lightning bolt.
- 02
Test it on real feedback
Run the test: Zapier brings back the three most recent tasks from that project. Pick a real one so the next step is mapped on actual data.
- 03
Add the comment
Add BugHerd with Add a Comment to a Task. Map the Project ID and Task ID from the trigger and write the Comment, for example: Seen, thanks, we are looking into it.
- 04
Test, then publish
Test the action, open the task in BugHerd and check the comment is there. Two steps, no filter: this Zap runs on the free plan. Click Publish to switch it on.
BugHerd triggers: 3 instant, 1 polling
4 events start a Zap when something happens in BugHerd, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
Comment Created
Instant triggerIn Zapier“Triggers when a comment is created”
Starts your Zap whenever someone writes a comment in the BugHerd project you picked. Comments are where clients and developers go back and forth, so this is the trigger for keeping a conversation visible elsewhere.
Project Created
Polling triggerIn Zapier“Triggers when a project is created.”
Runs when a new project appears in BugHerd. A new project usually means a new site or a new client, which makes this trigger a good starting point for setting everything up around it.
Task Created
Instant triggerIn Zapier“Triggers only when a task is created”
Fires only when a new task appears in the chosen project, not when an existing one changes. In BugHerd a task is usually a pinned note from a client or tester, so this trigger catches fresh feedback the moment it lands.
Task Created or Updated
Instant triggerIn Zapier“Triggers when a task is created or updated.”
Reacts to new tasks and to every change on existing ones in the selected project. It is the trigger for keeping status in sync, since it sees a task move along its life and not only its birth.
BugHerd actions: create, add, update
BugHerd gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Add an Attachment to a Task
ActionIn Zapier“Adds an Attachment to a Task”
Attaches a file to a BugHerd task from a link. It requires the Project ID, the Task ID, a File Name and the file's URL.
Add a Comment to a Task
ActionIn Zapier“Adds a Comment to a Task”
Writes a comment on an existing task. It takes the Project ID, the Task ID and the Comment text.
Create a Project
ActionIn Zapier“Creates a Project.”
Opens a new project in BugHerd. It needs a Name and the Feedback url, the address of the site the feedback will be pinned on.
Create a New Task
ActionIn Zapier“Creates a New Task.”
Adds a task to a BugHerd project from outside. Four fields are required: Project ID, Description, Severity and Status.
Update a Task
ActionIn Zapier“Updates a Task.”
Changes an existing BugHerd task. Only the Project Id and the Task Id are required to point at it.
The BugHerd search: Find Task by External Id
1 search step looks for data that already exists in BugHerd, so a later step can use it.
A search step finds something that already exists and hands it to the following steps. Searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.
Find Task by External Id
SearchIn Zapier“Finds a task by the external ID you have set on it”
Looks up a BugHerd task by the external ID you set on it, inside a given project. That ID is how another tool's record and the BugHerd task stay paired.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. BugHerd offers no such variant for its search, so it does not apply here.
- If multiple search results are found?Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a BugHerd Zap breaks
Zapier links no help article to BugHerd and lists no BugHerd-specific limit. What follows comes from how Zapier itself behaves, plus the fields BugHerd requires.
Four cases are worth knowing before you publish. If yours is not here, the Zapier troubleshooting page picks up from there.
Comments that comment on themselves
Comment Created plus Add a Comment to a Task in one Zap: each comment written starts a new run. The loop keeps going and eats your task count.Old feedback is not picked up
A Zap only reacts to what happens after it is published. Tasks and comments that already existed are never sent; moving them is a separate job.A launch-day flood
When a site goes live and testers pin dozens of notes at once, the trigger can deliver a huge batch, and Zapier's flood protection may hold it back.Project Created runs once per project
Zapier remembers what this polling trigger has already seen, so the same project never starts the Zap twice, even if you edit it later.
Need help automating BugHerd with Zapier?
A person reads every message.
