Resources · Zapier integration

Palzin Feedback Zapier integrationAutomate Palzin Feedback with Zapier.

Palzin Feedback Zapier integration in short: 5 triggers, 1 action, 0 searches. All five triggers are instant, so a new post or vote starts the Zap right away on any plan, and Create Post brings feedback from other tools into your boards.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Palzin Feedback Zapier integration does

Palzin Feedback is a tool for collecting customer feedback on boards, where people post ideas, vote and comment. Connected to Zapier, a no-code tool that chains apps together, it can report five kinds of activity to other apps and receive new posts from them. Feedback stops living only inside Palzin.

Three outcomes product teams get from it. A product channel that hears customers. New Post and New Comment push fresh feedback into the chat tool where the team already talks, so nobody has to refresh a board. A roadmap that closes the loop. Status Change tells another app when a post moves forward, which is the moment to warn support or update a tracking sheet. One inbox for every source. Create Post turns a support ticket, a form answer or a sales note from another app into a feedback post on the right board, with a title and a description.

New Vote and New Author round it off: one tracks demand as it grows, the other spots a new contributor joining the conversation.

What Zapier does not do here: there is no search, so a Zap cannot check whether a similar post already exists before creating one. Spotting a duplicate stays a human job, done in Palzin. And the single action only creates posts; it does not edit, move or close them.

Still choosing a tool? See n8n vs Zapier and Zapier alternatives.

Vocabulary

Zapier vocabulary, in one minute

Seven terms carry the rest of this page. Each one gets a single plain-English line here, and is used as is afterwards.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Palzin Feedback offers five, all instant.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like Create Post.
Task
The unit Zapier bills. One task is one action completed successfully; your plan's count is a count of those.
Polling or 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 what arrived meets your condition, and quietly stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What Palzin Feedback Zaps cost

Palzin Feedback is not reserved for paid plans: it works on the free plan. You pay in tasks, and only for actions that go through.

  • Free plan100 tasks a month
  • Free plan Zap size2 steps: 1 trigger, 1 action
  • Palzin Feedback on the free planYes, not a paid-only app
  • Cost of a Palzin trigger0 tasks

A Palzin trigger never costs a task. Each successful action does, whether it is Create Post or a message sent in another app; a failed one is not counted. The free plan gives 100 tasks a month and two-step Zaps only. A filter, for instance to keep only some boards, or a second action makes the Zap multi-step, which needs a paid plan. The grid below concerns polling triggers; the five Palzin triggers are instant, so it only matters when another app starts a Zap that ends in Create Post.

Connect

Connect Palzin Feedback to Zapier in three steps

  1. 01

    Start from the Apps page

    In your Zapier account, open the Apps page and click + Add connection. A connection is your Palzin Feedback account linked once, then reused by every Zap that touches it.

  2. 02

    Select Palzin Feedback

    Search for Palzin Feedback in the dialog, pick it, then click Add connection. You need a Palzin Feedback account first; Zapier connects to it and does not create one.

  3. 03

    Sign in and allow access

    Sign in to Palzin Feedback in the tab that opens and grant Zapier access. If the Zap will post on boards you do not own, make sure your account is allowed to write there.

First Zap

Your first Palzin Feedback Zap

GoalLog every new feedback post in a sheet, then alert the product team in its channel.

  1. 01

    Choose the trigger

    Create a Zap, pick Palzin Feedback as the starting app and New Post as the event, then select the Palzin connection you added earlier.

  2. 02

    Test with real posts

    Run the test. Zapier brings back the three most recent items of the connected account, so the next steps are mapped on actual feedback, not invented text.

  3. 03

    Add the log row

    Add a Google Sheets step that creates a row, and map what Palzin sent about the post into the columns of your feedback log.

  4. 04

    Add the team alert

    Add a Slack step for the channel message. Two actions make this a multi-step Zap, so it needs a paid plan; on the free plan keep one of them.

  5. 05

    Test, then publish

    Test each step once and check what came back before moving on. Then publish the Zap to switch it on; the lightning bolt in the editor marks the instant trigger.

Triggers

The five Palzin Feedback triggers

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

1

New Author

Instant trigger

In Zapier“Triggers when a new author is created.”

Starts the Zap when a new author is created in Palzin Feedback. It is the hook for welcoming a new voice or adding that person to a list you keep elsewhere.

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 manager wants each new contributor added to a spreadsheet of engaged users for the next interview round.
Watch out
authors created before the Zap was published never come through, so build the starting list separately.
2

New Comment

Instant trigger

In Zapier“Triggers when a new comment is created.”

Fires whenever someone comments on feedback in Palzin. Discussions under a post often carry the detail that matters, and this trigger moves them to where the team reads.

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 manager follows heated threads and wants each new comment copied into the channel dedicated to that product area.
Watch out
on a busy board every comment is an event, so a Zap with two actions behind it can eat tasks faster than the posts themselves.
3

New Post

Instant trigger

In Zapier“Triggers when a new post is created.”

Runs each time a new feedback post is created. It is the trigger most teams start with, since a post is the raw request: an idea, a complaint, a missing feature.

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 wants every new request posted in its product channel so the founders read feedback the day it arrives.
Watch out
never pair it with Create Post on the same account, or each created post starts the Zap again and loops.
4

New Vote

Instant trigger

In Zapier“Triggers when a new vote is created.”

Kicks in when someone votes on a post. Votes measure demand, so passing them on lets you watch which requests are picking up support without opening the board.

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 owner keeps a sheet of the most requested ideas and wants each vote added as a line to count later.
Watch out
one popular post can collect many votes, and each one starts the Zap, so check that your monthly task count can absorb them before you publish.
5

Status Change

Instant trigger

In Zapier“Triggers when a post status is changed.”

Triggers when the status of a post changes in Palzin. This is the trigger that closes the loop with customers: the request moved, now someone can tell them.

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 support lead wants an alert each time a post changes status, so agents can answer the customers who asked for it.
Watch out
every status move counts, including a back-and-forth by mistake, so expect the occasional extra alert.
Actions

The Palzin Feedback action

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

1

Create Post

Action

In Zapier“Create a new Post”

Adds a new feedback post to one of your Palzin boards, with a title and a description taken from an earlier step.

When to use it
support receives feature requests in its help desk and wants each tagged ticket to become a post the product team can see and others can vote on.
Watch out
Title, Description and Board Name are all required, so the step before it must provide text for the first two.
When it breaks

When a Palzin Feedback Zap breaks

Zapier attaches no help article to Palzin Feedback and no limit specific to the app is documented. What can go wrong is what goes wrong on any Zap, plus one trap this app makes easy.

Three cases worth knowing before you publish. If one hits you anyway, Zapier troubleshooting is a good starting point.

  • New Post plus Create Post loops

    A Zap that writes where its own trigger watches sets itself off again and again. Create Post feeding a Zap started by New Post does exactly that, and burns tasks fast.

  • Old feedback is never replayed

    A Zap only reacts to events after it is switched on. Existing posts, votes and comments stay where they are; moving that backlog is a separate job.

  • A bulk import gets held back

    Import a large batch of feedback at once, after a migration from another tool, and Zapier's flood protection can hold the batch back instead of passing it all on.
Need help

Need help automating Palzin Feedback with Zapier?

A person reads every message.

FAQ

Palzin Feedback Zapier integration: questions

01Is the Palzin Feedback Zapier integration free?
Yes. Palzin Feedback is not reserved for paid plans, so its five triggers and its action work on the free Zapier plan. That plan gives 100 tasks a month and two-step Zaps: one trigger and one action. It covers simple flows such as posting each new feedback in a chat channel. Once you want to log and alert in the same Zap, or add a filter to keep some boards only, the Zap becomes multi-step, and multi-step Zaps need a paid plan.
02How many tasks does a Palzin Feedback Zap use?
One task per successful action, nothing for the trigger. A Zap that sends each new post to a channel uses one task per post. A Zap that creates a post from a support ticket uses one task per ticket. Failed actions are not counted. Keep an eye on busy triggers: New Vote and New Comment can fire many times for a single post, so a Zap built on them can consume more. A few apps and actions take more than one task when they complete.
03Are Palzin Feedback triggers real time?
Yes, all five triggers are instant. Palzin Feedback reports the event to Zapier itself instead of waiting for Zapier to check, so the plan interval grid does not apply, even on the free plan where polling triggers wait 15 minutes. The editor shows a lightning bolt on a Zap built on an instant trigger. Note that the reverse direction depends on the other app: a Zap that ends in Create Post starts as fast as that other app's trigger allows.
04What does connecting Palzin Feedback to Zapier take?
A Palzin Feedback account, since Zapier links to an existing one. Open the Apps page of your Zapier account, click + Add connection, search for Palzin Feedback and confirm with Add connection. Sign in to Palzin in the tab that opens and grant Zapier access. If you plan to use Create Post, the board you want to post on must already exist, because Board Name is picked from a list, and your account needs the right to write there.
05How do you avoid a loop between New Post and Create Post?
Never let one Zap create posts on the account that starts it. A Zap that writes into the place its own trigger watches sets itself off again and again, and burns through the task count fast. With Palzin Feedback the trap is obvious once you see it: New Post starts the Zap, Create Post makes a new post, which starts the Zap again. Keep the two in separate flows, and make sure the Zap built on New Post sends feedback out of Palzin, not back into it.
06What if the Palzin Feedback operation you need is missing?
Then Zapier cannot do it with Palzin Feedback today. The integration offers five triggers and one action, Create Post, with no search. A Zap can react to new authors, comments, posts, votes and status changes, and it can create posts. It cannot update a post, change its status or look up an existing one to avoid duplicates. Anything beyond that has to be done in Palzin Feedback directly. List what your flow needs before building it.
07Zapier, Make or n8n for Palzin Feedback?
Pick on criteria rather than a ranking. On Zapier, Palzin Feedback offers five instant triggers and one action on the free plan, which fits flows that broadcast feedback activity or collect posts from other tools. Check three things for any option: does it offer the Palzin events and the action your flow needs, can it look up existing posts if duplicates worry you, and what does each extra step cost on your plan. The answers to those settle it for your case.
Same platform

Other docs you might need on this stack.

Browse all integrations