Resources · Make integration

Feedier Make integrationAutomate Feedier with Make.

Every new piece of customer feedback can start work on its own. The Feedier Make integration gives you 6 modules, including 2 instant triggers. This guide is for support and CX teams: connect your account, then build a first scenario step by step.

Try the Feedier integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Feedier Make integration do for you?

The Feedier Make integration links your Feedier account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that run one after the other. Feedier can start that chain the moment feedback arrives or an item gets tagged, and Make carries the result wherever it needs to go.

Route tagged items to the right people. Watch New Tagged Item fires when an item receives a tag in Feedier, so a support lead can push only the tagged cases to the tool the team already reads, instead of scanning the whole feed.

Keep a copy of every answer. Watch New Feedback hands each new response to Make, and the next module can write it into a spreadsheet or a CRM record. For a backlog, List Feedback pulls the existing responses in one go.

Start outreach from Feedier. Create an Email and Create an SMS create a new email or SMS in Feedier from data coming from another app, which suits a team that wants a new customer contact to trigger the next message.

Know the limits before you start. Make itself notes that its documentation for Feedier is limited, so the fields of each module are best discovered in the editor. When a listed module falls short, Make an API Call reaches the rest of the Feedier API. Feedier may also exist as an n8n node; the n8n vs Make comparison helps you pick, and the Make training covers the editor from zero.

Connect

How do you connect Feedier to Make?

  1. 01

    Add a Feedier module

    Open a scenario, click the + and search for Feedier. Pick any of its modules, then click Create a connection. A connection is your Feedier account linked to Make once and reused by every Feedier module afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several people or several Feedier accounts share one Make organization. A label such as the team or the workspace makes the right account easy to spot later.

  3. 03

    Authorize and save

    Depending on what Feedier asks for, either approve Make on the Feedier page that opens or paste the key Feedier gives you. Click Save, and the module becomes ready to fill in.

First scenario

Build your first scenario with Feedier

GoalWhen new feedback reaches Feedier, Make creates an email in Feedier with the details of that response.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module, the trigger, goes.

  2. 02

    Add the Feedier trigger

    Search for Feedier, choose Watch New Feedback and pick your connection. It is an instant trigger, marked with a lightning badge: Feedier calls Make as soon as a response comes in.

  3. 03

    Add Create an Email

    Click the + on the right of the trigger and add Create an Email. Fill its fields by mapping values from the trigger: Make lists what the response carries, so you pick rather than type.

  4. 04

    Test with Run once

    Click Run once, then submit a test response in Feedier. Each module shows the bundles it received, a bundle being one item passed along. Check that the email carries the right data.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. From then on, every new response runs it, and each module run counts as one operation on your Make plan.

Triggers

Feedier triggers in Make

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

Feedier1Watch New Feedback

Watch New Feedback

Instant trigger

In Make“Triggers when a new feedback is received.”

Starts your scenario each time a new response lands in Feedier, so nothing sits unread while the team is busy elsewhere. Each response enters the scenario as its own bundle, ready to be copied, routed or answered by the modules that follow.

How it fires
instant; Feedier calls Make through a webhook as soon as the feedback arrives, with no schedule to set.
When to use it
when every single response matters, for example to log all answers in a shared sheet the moment they come in.
Watch out
responses already sitting in Feedier are the job of List Feedback, so pair both modules if you need the history too.
Feedier2Watch New Tagged Item

Watch New Tagged Item

Instant trigger

In Make“Triggers when a new item is tagged.”

Reacts to a tag rather than to a response: the scenario starts when an item gets tagged in Feedier. That lets the team decide what deserves automation simply by tagging it, and leave everything else alone.

How it fires
instant; Feedier calls Make through a webhook as soon as the tag is applied.
When to use it
when only a slice of the feedback should travel, such as items a support agent flags for the product team.
Watch out
the documentation says nothing about which tags are exposed, so run the scenario once on a test item and read the bundle before mapping anything.
Modules

Feedier modules in Make

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

Feedier1

Create an Email

Action

In Make“Creates a new email.”

Creates a new email in Feedier from data that another module hands over, so an outreach message can be prepared without opening Feedier by hand.

When to use it
when a new customer record in your CRM should lead to an email created on the Feedier side.
Watch out
the documentation lists no fields, so open the module after connecting to see what Feedier expects.
Feedier2

Create an SMS

Action

In Make“Creates a new SMS.”

Does the same job as Create an Email for text messages: it creates a new SMS in Feedier, filled with values mapped from earlier modules in the scenario.

When to use it
when a text message suits your audience better than an email, for instance right after an order is marked as delivered in your shop.
Watch out
test it with Run once on your own number before switching the scenario on.
Feedier3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Feedier API to your scenario, using the connection you already created. It covers what the five other modules do not.

When to use it
when a need falls outside the listed modules and the Feedier API documentation shows an endpoint for it.
Watch out
you write the request yourself, so keep the API reference of Feedier open while you set it up.
Feedier4

List Feedback

Search

In Make“Returns a list of feedback.”

Returns existing feedback from Feedier as a list, one bundle per response, so the modules after it process each answer in turn.

When to use it
to catch up on responses received before your scenario existed, or to export them to another tool in a single run.
Watch out
a search can return zero, one or many bundles, and each module after it runs once per bundle, which adds operations.
Need help

Need help automating Feedier with Make?

A person reads every message.

FAQ

Questions about the Feedier Make integration

01Is the Feedier Make integration free?
Yes, Feedier is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 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 minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. Feedier's own subscription is a separate matter.
02What does connecting Feedier to Make require?
A Feedier account and the right to authorize an outside tool on it. Make lists no specific prerequisite for this app. In the editor, you add any Feedier module, click Create a connection, optionally give it a name, then either approve Make on the Feedier page or paste the key Feedier provides, and save. The same connection then serves all 6 Feedier modules, so you only do this once per account.
03Do the Feedier triggers in Make react in real time?
Yes. Both Feedier triggers, Watch New Feedback and Watch New Tagged Item, are instant triggers: Feedier calls Make through a webhook as soon as the event happens, and the module carries a lightning badge in the editor. There is no polling interval to set for them, unlike scheduled triggers that Make checks every 15 minutes by default. To pull responses that already exist, add List Feedback to a separate scenario.
04What if a Feedier module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Feedier API with the connection already in place, so you are not limited to the 5 other modules. Be aware that Make states its documentation for Feedier is limited, because little public information exists about the app. Expect to discover fields in the editor and to check the Feedier API reference when you build a custom request.
05Should Feedier be automated with Make or n8n?
It depends on how you prefer to work. Make gives Feedier 2 instant triggers, 3 actions, a search module and a generic API call, all set up in a visual editor with a free entry plan. Feedier may also exist as an n8n node, in which case the choice comes down to the tool your team already uses and knows. Compare the modules each side offers for Feedier before you commit, then test your real case on one of them.
Same platform

Other docs you might need on this stack.

Browse all integrations