- Home
- Resources
- Integrations
- Userback
Userback Make integrationAutomate Userback with Make.
What happens to a bug report once a user sends it through Userback? With the Userback Make integration, 1 instant trigger hands each new feedback to Make the moment it lands. This guide is for product and support teams: connect the account, then build a first scenario that routes feedback where your team works.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Userback Make integration do for you?
The Userback Make integration links your Userback account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that belongs to one app. On the Userback side there is a single module, Watch New Feedback, and it starts your scenario whenever someone submits feedback.
A support queue that fills itself. Watch New Feedback starts the flow, and the next module comes from the helpdesk or ticketing app your team already uses. Each feedback travels as a bundle, meaning one item passed from a module to the next, so every report becomes one ticket.
A product log nobody has to copy by hand. Point the same trigger at a spreadsheet or a database app, for example the one described on our Airtable Make integration page, and each report lands as a new row your product manager can sort and tag.
An alert for the people who fix things. Send a message to your team chat as soon as a user reports a problem, so the developer on duty sees it before the next stand-up.
Know the limits before you start. Make offers only this trigger for Userback: no module to create, update or search feedback, and no Make an API Call module to fill the gap. Everything after the trigger happens in other apps. The same app often exists in n8n too; if you are weighing both tools, read our n8n vs Make comparison, and if you would rather learn Make step by step, our Make training starts from zero.
How do you connect Userback to Make?
- 01
Add the Userback module
In a new scenario, click the +, type Userback in the search box and pick Watch New Feedback. Make then asks for a connection, which is your Userback account linked to Make once and reused afterwards.
- 02
Create the connection
Click Create a connection. You can give it a name, which helps later when a teammate or a client account shares the same Make organization and you need to tell two Userback accounts apart.
- 03
Authorize and save
Follow what Make shows you: either an authorization page where you sign in to Userback and accept, or a field where you paste the key Userback gives you. Click Save and the module is ready to configure.
Your first scenario with Userback
GoalWhen a user submits feedback in Userback, Make passes it to the tool your team reads every day.
- 01
Create the scenario
Open the Scenarios page, click to create a new scenario, then click the large + in the middle of the editor to place your first module.
- 02
Add Watch New Feedback
Search for Userback, choose Watch New Feedback and select the connection you created. The lightning badge on the module tells you the trigger is instant.
- 03
Add the destination
Click the + on the right of the Userback module and pick the app that should receive the feedback. Map the data from the Userback bundle into its fields.
- 04
Test with Run once
Click Run once, then submit a test feedback through Userback. Then read the bundles each module received and check that the mapping put every value in the right place.
- 05
Switch it on
When the test looks right, save and turn the scenario on. From then on, each new feedback starts one run, and every module run on it counts as an operation on your plan.
What starts a Userback scenario
1 module starts a scenario when something happens in Userback. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Userback as soon as it happens.
Watch New Feedback
Instant triggerIn Make“Watches for a new feedback.”
Watch New Feedback turns every report your users send through Userback into the starting point of a scenario, so nobody has to open the dashboard to notice it. Each feedback reaches Make as its own bundle, ready for the next module.
Need help automating Userback with Make?
A person reads every message.