Resources · Zapier integration

Acute Zapier integrationAutomate Acute with Zapier.

The Acute Zapier integration gives you 6 triggers, 1 action and 1 search. All six triggers are instant, so a new post, vote, comment or status move reaches your automation the moment it happens, even on the free plan you start with.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Acute Zapier integration actually does

Connecting Acute to Zapier turns your feedback board into something that reports on its own. Zapier, an online automation service, listens for events in Acute (a new post, a vote, a tag, a comment) and runs steps in your other tools. It can also write back, but only one thing: a post's status.

A release board that sorts itself. A product manager starts on Tag Added to Feedback Post, lets a filter pass only one release tag, then calls Change Feedback Status so tagged posts move forward without anyone dragging cards around.

A help desk that hears the board. A support lead pipes every New Conversation Added to a Feedback Post into the team's ticket tool. Customers who chime in on an idea get an answer from the people who own the relationship, not from whoever happened to open Acute.

A demand sheet for the founder. New Vote appends a row per upvote to a spreadsheet. Interest per idea then sits next to the numbers the founder already reads, and roadmap debates start from data rather than memory.

Now the limits. Zapier cannot create a post in Acute, add a comment, add a tag or delete anything. The single write is a status change, plus one lookup with Find Feedback. Everything else flows out of Acute, not into it. If those missing writes matter, weigh the tools first: n8n vs Zapier and Make vs Zapier lay out the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it quietly otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can use what it found.
Cost

What Acute on Zapier really costs

Acute is not a premium app, so it works from the free plan. The bill counts actions, never triggers.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, Acute works on the free plan
  • Acute triggers6 of 6 instant, no interval

None of the six triggers costs a task, and neither does Zapier listening for them. Each Change Feedback Status that goes through counts as one task; one that fails counts for nothing. The free plan gives 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter or Find Feedback and the Zap becomes multi-step, which needs a paid plan. The interval grid below only applies to polling triggers, and Acute has none.

Connect

Connect your Acute account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Acute account linked to Zapier once, then reused by every step that touches Acute.

  2. 02

    Find Acute and confirm

    Type Acute in the search box of the dialog, pick it, then click Add connection. A new browser tab opens on the Acute side. You need an Acute account before going further.

  3. 03

    Sign in and grant access

    Log into Acute in that tab and allow Zapier to reach the account. If the Zap will touch feedback boards you do not own, make sure that account has read or write access on them first.

First Zap

Your first Zap: tagged posts move forward on their own

GoalWhen a post receives one specific tag, move it to the next status on the board.

  1. 01

    Pick the trigger

    Create a Zap, choose Acute as the app and Tag Added to Feedback Post as the event, then select the Acute connection you created a moment ago.

  2. 02

    Test with a real post

    Tag a post in Acute, then run the test. Zapier brings back the three most recent items from your account, so you build the rest on genuine data.

  3. 03

    Add the filter

    From the plus icon, add Filter. Pick the tag field, a text rule, and the exact tag name. Only matching posts go further. This makes the Zap multi-step.

  4. 04

    Set the status change

    Add Change Feedback Status. Map Feedback Id from the trigger step, then choose the target Feedback Status. Run Configure & test and check the post moved in Acute.

  5. 05

    Publish

    Click Publish to switch the Zap on. From that point, each new tag that passes the filter moves its post. Older tagged posts stay where they are.

Triggers

The 6 Acute triggers

6 events start a Zap when something happens in Acute, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Comment

Instant trigger

In Zapier“Triggers when a new comment has been added to a feedback post.”

Every time someone writes under a feedback post, this trigger starts your Zap with that comment in hand. It is the event to watch when the discussion around an idea matters as much as the idea itself.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a product designer wants every remark on a mockup request copied into the design team's chat so nobody has to refresh the board.
Watch out
busy posts produce many comments, and each action that follows costs a task.
2

New Conversation Added to a Feedback Post

Instant trigger

In Zapier“Triggers when a new conversation has been added to a feedback post.”

A conversation added to a feedback post kicks off the Zap here. It gives you a second way into a request, next to comments and votes, when someone wants to talk it through.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an account manager opens a ticket in the help desk each time a customer starts talking about a post, so the reply comes from the right person.
Watch out
the Zap only sees conversations added after it is published, never the ones already on the board.
3

New Feedback

Instant trigger

In Zapier“Triggers when there is a new feedback post.”

Zapier highlights this one, and for good reason: it fires on each brand new post on your board. That makes it the entry point for most Acute automations, from alerts to logs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a startup founder wants a spreadsheet row per idea submitted, to review requests alongside sales notes before planning.
Watch out
posts created before the Zap was published are never picked up, so export the backlog separately if you need it.
4

Feedback Status Change

Instant trigger

In Zapier“Triggers when a new status has been assigned to a feedback post.”

As soon as a post is moved to a different status, this trigger runs. It is how the people who asked for a feature learn that their idea moved, without anyone writing to them by hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer success team sends a changelog note to the CRM whenever an idea it championed advances.
Watch out
a Zap that also runs Change Feedback Status can set itself off again and again.
5

Tag Added to Feedback Post

Instant trigger

In Zapier“Triggers when a new tag has been added to a feedback post.”

Tags are how a board gets sorted, and this trigger fires whenever one lands on a post. Pair it with a filter and a single tag becomes a switch that routes posts wherever you want.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a QA engineer receives a task in the bug tracker only when a post is tagged as a defect.
Watch out
without a filter, every tag starts the Zap, and adding a filter needs a paid plan.
6

New Vote

Instant trigger

In Zapier“Triggers when a new upvote has been added to a feedback post.”

Each upvote on a feedback post starts the Zap. It is the most frequent event on an active board, which makes it the best raw signal of demand and the quickest way to spend tasks.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a growth marketer logs each vote in a spreadsheet to see which ideas gather support fastest.
Watch out
on the free plan, 100 tasks go fast if every vote triggers an action.
Actions

The Acute action

Acute gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Change Feedback Status

Action

In Zapier“Changes a feedback post's status.”

This moves an existing post to another status on your Acute board, which is the only write Zapier can perform in Acute. You give it the post's Feedback Id and the Feedback Status you want, both required.

When to use it
close a request automatically once the matching ticket is resolved in your help desk.
Watch out
without a Feedback Id from an earlier step, add Find Feedback before it.
Searches

The Acute search, and what happens when it finds nothing

1 search step looks for data that already exists in Acute, so a later step can use it.

A search step looks up a post that already exists and hands it to the next steps. In the editor, Acute's search sits at the bottom of the Action event list, under SEARCH. Three settings decide what happens next.

1

Find Feedback

Search

In Zapier“Searches for one or more feedback posts”

Looks up one or more existing posts on your board and passes them to the next step. That is how a Zap starting outside Acute gets the Feedback Id that Change Feedback Status needs.

When to use it
a ticket closes in your help desk and you want the linked idea updated in Acute.
Watch out
adding it makes the Zap multi-step, so it needs a paid plan.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps after it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Acute offers no such variant, so Find Feedback only ever looks, it never creates a post.
  3. If multiple search results are found?
    When several posts match, keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When an Acute Zap breaks

Zapier attaches no help article to Acute and no rate limit is documented for it. What breaks is general Zapier behaviour, and one combination specific to this app.

The four cases below are the ones to check first. For anything else, the Zapier troubleshooting page is the place to go next.

  • The status loop

    A Zap on Feedback Status Change that also runs Change Feedback Status writes where its own trigger watches. It fires itself again and again and burns through tasks.

  • Old posts never show up

    A Zap only reacts to what happens after it is published. Posts, votes and tags that already existed are ignored; moving the backlog is a separate job.

  • A bulk import gets held back

    If a large batch of posts arrives at once, after a migration for example, Zapier's flood protection can hold the trigger back instead of running everything.

  • Find Feedback comes back empty

    By default, a search that finds no post stops the Zap, and Change Feedback Status never runs. Switch on the no-results setting if the Zap must carry on.
Need help

Need help automating Acute with Zapier?

A person reads every message.

FAQ

Acute Zapier integration: frequent questions

01Is the Acute Zapier integration free?
Yes, as long as each Zap stays at two steps. Acute is not a premium app, so the free plan accepts it, with 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: one trigger and one action, nothing more. A product team that wants a filter on tags, or a Find Feedback lookup before changing a status, has built a multi-step Zap, and that needs a paid plan. Test the two-step version first, then decide whether the extra step is worth upgrading for.
02How many tasks does an Acute Zap use?
One per successful action, and none for the trigger. A Zap that sends each new vote to a spreadsheet costs one task per vote. A Zap that sends the vote to the spreadsheet and also posts it in a chat costs two per vote, because each action is counted on its own. An action that fails is not counted. On a busy board, New Vote is the trigger to watch, since it fires far more often than New Feedback.
03Is Acute on Zapier real time?
Yes, for all six triggers. Each one is instant, which means Acute itself tells Zapier the moment a post, vote, tag, comment, conversation or status change happens. The Zap starts straight away, and the plan interval grid does not apply. A support manager on the free plan gets the same speed as a team on Enterprise. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is the quickest way to confirm it.
04What does it take to connect Acute to Zapier?
An Acute account and a Zapier account. The connection is made once from the Apps page with + Add connection, then reused by every Zap. If the Zap will act on boards someone else owns, the Acute account you connect needs read or write access to them. For Change Feedback Status, that account must be allowed to edit the posts, since the action needs a Feedback Id and a Feedback Status to work.
05Why does an Acute Zap keep firing on its own?
Most likely it changes a status while listening to status changes. A Zap built on Feedback Status Change that ends with Change Feedback Status writes exactly where its own trigger is watching, so every run sets off the next one. Tasks drain fast. Break the loop with a filter that only lets through statuses the Zap does not set itself, or split the work across two Zaps with different triggers, such as Tag Added to Feedback Post.
06What if the Acute operation you need is missing?
Then Zapier cannot do it for Acute today. The app offers six triggers, one action and one search: there is no way to create a post, add a comment, tag a post or delete anything from a Zap. A useful workaround is to let Acute push events out and handle the rest elsewhere. For instance, a sales team can log each new conversation in its CRM and keep the follow-up there, rather than waiting for a write Acute does not expose.
07Zapier, Make or n8n for Acute?
Decide on three criteria rather than on a ranking. First, coverage: on Zapier, Acute sends six instant events but accepts only a status change, so check whether another tool exposes the writes you are missing. Second, cost model: Zapier bills each successful action, which suits low-volume flows like new posts better than high-volume ones like votes. Third, who maintains it: a team already running Zaps keeps everything in one place by staying on Zapier.
Same platform

Other docs you might need on this stack.

Browse all integrations