Skip to Content
TutorialsIntegration PlaybooksGet Feedback

Get Feedback Integration

Collect user feedback from your app

What is Get Feedback?

Get Feedback is a feedback collection platform. You embed a small widget in your app — a floating “Feedback” button — and your users submit bug reports, feature requests, ratings, and general feedback without leaving the page. Submissions land in the Get Feedback dashboard, where your team triages them: statuses, assignment, and comments.

Perfect for:

  • A “Report a bug” button on every page, with optional screenshots
  • Collecting feature requests from real users
  • Star ratings and general “how are we doing?” feedback
  • Any app where you want a feedback channel without building forms, storage, and a triage UI yourself

Unlike most connectors, there’s almost nothing to build: the widget is a single script tag. Your coding assistant adds it to your layout and you’re done.

What You’ll Need

Get Feedback, connected

Auto-provisioned automatically, or bring your own key — see Step 1.

Nothing else

No IDs to copy, no SDK to install. The widget configures itself from the connection.

Step 1: Connect Get Feedback

  1. Open your project → Connectors in the sidebar (or check the Get Feedback card during project creation).
  2. Click Connect.
  3. Choose a mode:
    • Auto-provision (default) — Buildpad creates a dedicated Get Feedback tenant for this project (named {your org name}-{your project name}), containing a feedback project called Buildpad, and stores its widget API key. You are registered as that tenant’s admin, so you can log into the Get Feedback dashboard right away. The card shows Auto-configuring while this is in flight, then Connected.
    • Bring your own key — paste an existing Get Feedback widget API key (a 64-character hex string, from a feedback project you already manage). Use this if your team already runs its own Get Feedback tenant.
  4. Click Connect.

This stores two things for your project: GET_FEEDBACK_API_KEY and GET_FEEDBACK_BASE_URL. The base URL isn’t a field you fill in when connecting — Buildpad sets it to the Get Feedback deployment automatically, and the connect form can’t be tricked into overriding it.

Step 2: Tell the Agent What You Want

Once Get Feedback is connected, your coding assistant already knows how to embed the widget — you don’t need to paste API keys or URLs into a prompt, just describe what you want.

Example 1: Feedback button on every page

Add the Get Feedback widget to this app.

I want the feedback button to:
- Appear on every page
- Not overlap my existing bottom-right chat bubble

Button position is a dashboard setting, not something the script tag or a JS API controls. If you’re not already a tenant admin (only auto-provisioning grants that automatically), ask whichever teammate has dashboard access to change it under Widget settings.

Example 2: Feedback from your own menu

I don't want the floating feedback button. Instead, add a
"Give feedback" item to my app's user menu that opens the
Get Feedback form when clicked.

Please set this up using the widget's programmatic API.

Example 3: Custom feedback form

Build a custom feedback form at /feedback instead of using the
pre-built widget.

I want:
- My own form styling matching the rest of the app
- Type selector (bug / feature request / general)
- An optional 1-5 star rating
- Submissions to go to my connected Get Feedback project

Please implement this against the Get Feedback HTTP API.

Under the hood: your assistant reads a bundled reference doc covering the widget script, its programmatic API, and the raw HTTP endpoints. The widget API key is publishable (it only identifies your feedback project — it can’t read collected feedback), so it’s safe in page markup.

Step 3: Test the Connection

Start the app

Run pnpm dev and open any page.

Confirm the button appears

The floating feedback button (or your custom trigger) should render — no console errors about a missing API key.

Submit test feedback

Open the widget, pick a type, write a message, and submit. You should see a success state.

Check the dashboard

Log into the Get Feedback dashboard (the Platform link on the connector card), select your tenant, and confirm the test submission is there.

Repeat after deploying

Env vars connected here don’t automatically reach your deployed app — ask your assistant to push them (see Troubleshooting) and re-test on the live URL.

Triage Your Feedback

Collected feedback lives in the Get Feedback dashboard, not in your app:

  • Statuses — new → in review → resolved / dismissed
  • Assignment — hand a submission to a teammate
  • Comments — discuss a submission with your team
  • Widget settings — button position, color, label, enabled feedback types, and screenshot capture are all configured here too

If you auto-provisioned, the user who connected the project is already the tenant’s admin. Teammates can be added from the dashboard.

Don’t ask your coding assistant to build feedback-triage screens or widget-settings UI inside your app — the dashboard already does this, and the widget API key deliberately has no read access to collected feedback.

Common Questions

Is the widget API key a secret?

No — it’s publishable, like a Stripe publishable key or a Google Maps key. It identifies your feedback project so the widget knows where to send submissions; the service stores only a hash of it and rate-limits submissions per IP. It cannot read any collected feedback. It’s fine for it to appear in your page’s HTML.

Can my app read the feedback back, e.g. to show it in my own admin page?

Not with the widget key — collection and triage are deliberately separate. Feedback is read and managed in the Get Feedback dashboard. If you need feedback data inside your own app, that’s a feature request for your Get Feedback administrator, not something the connector provides today.

Where exactly does my feedback go?

Auto-provisioning creates a tenant on the Get Feedback service just for this Buildpad project. Every submission from your app lands in that tenant — isolated from every other project’s feedback.

Can users attach screenshots?

Yes — the widget has built-in screenshot capture (with region selection). It’s off by default; enable it in the widget settings on the Get Feedback dashboard.

Widget or custom form — which should I use?

Start with the widget — it’s a single script tag and covers types, ratings, screenshots, validation, and rate limiting. Build a custom form (Example 3 above) only if the widget’s look and feel genuinely can’t fit your design.

Something Not Working?

Button Doesn’t Appear

Tell the agent:

Added the Get Feedback widget but no feedback button shows up.

Can you check the browser console for errors, confirm the script tag
is rendered in the layout with a data-api-key attribute, and that
GET_FEEDBACK_BASE_URL and GET_FEEDBACK_API_KEY are set in .env.local?

Submissions Fail

Tell the agent:

The Get Feedback widget opens, but submitting returns an error.

Can you check the network tab for the /api/widget/v1/submit call —
if it's a 401 the API key is wrong, if it's a 403 the feedback
project was deactivated, and if it's a 429 I'm hitting the
10-submissions-per-minute rate limit from my IP.

Works Locally, Not After Deploying

Tell the agent:

The Get Feedback widget works with `pnpm dev` but not on the
deployed app.

Can you check whether GET_FEEDBACK_API_KEY and GET_FEEDBACK_BASE_URL
are set in the Amplify environment, and redeploy if you add or
change them?

Connector Shows “Error”

If auto-provisioning failed, the connector card shows Error. Open your project → Connectors → Get Feedback and click auto-provision again — provisioning is safe to retry. If it keeps failing, the Get Feedback deployment itself may be unreachable; contact your platform administrator.

Quick Checklist

Before going live:

  • Connector shows Connected on the Connectors page
  • Feedback button appears with pnpm dev locally
  • A test submission shows up in the Get Feedback dashboard
  • Env vars pushed to the Amplify deployment and redeployed
  • Tested on the live URL, not just locally
  • Widget position/color/label configured to match your app (on the dashboard)
  • Teammates who triage feedback have dashboard access

Remember

One script tag — the widget is self-contained; there’s no SDK to install and no proxy route to build.

The key is publishable — it can only submit feedback, never read it.

Triage lives in the dashboard — statuses, assignment, comments, and widget settings are managed there, not in your app.

Deploying is a separate step — connecting Get Feedback doesn’t push env vars to your live app automatically.

One tenant per project — your feedback is isolated from every other Buildpad project’s.

Stuck? Tell your coding assistant: “I need help with the Get Feedback integration” and describe the issue.

Last updated on
ObservabilityMy Apps