Skip to main content

Import GetFeedback and Usabilla feedback

Quick start​

Connect GetFeedback and Usabilla in NEXT, enable the Teamspace subscription for this import, and let the scheduled sync pull GetFeedback or Usabilla feedback items into NEXT as Highlights.

Why integrate with GetFeedback and Usabilla?​

Digital feedback tools capture moments when users react in context: while using a page, completing a flow, or responding to a targeted prompt. That kind of signal is often fast, specific, and highly actionable. Importing it into NEXT helps teams connect in-product feedback with the rest of the customer story.

  • It brings contextual product feedback into the same workflow as calls, tickets, and reviews.
  • It helps teams analyze both explicit comments and lightweight ratings in one place.
  • It reduces the risk that web and app feedback stays siloed in a specialist tool.

What gets imported​

  • Object in NEXT: Highlights
  • Source objects: GetFeedback or Usabilla feedback items
  • Included fields: Feedback text, ratings, tags, context metadata, timestamps, and source identifiers.

Authentication​

Provider API credentials configured in the integration.

Connection notes​

  • Configure the credentials issued by your GetFeedback Digital or Usabilla account.
  • Enable the Teamspace subscription that should receive the imported feedback stream.

Configuration notes​

  • Use Teamspace subscription settings to keep the import targeted to the source feedback stream you care about.
  • Subscriptions also support LiquidJS text templates that prepend extra context before the comment text. For syntax guidance, see Use LiquidJS templates.
  • Imports run incrementally from the previous successful sync timestamp.

Limitations​

  • Available metadata depends on the response payload exposed by your GetFeedback or Usabilla account.
  • Only feedback visible to the configured credentials can be imported.

Troubleshooting​

  • If feedback stops importing, confirm the API credentials are still active and scoped to the right account.
  • If screenshots or metadata are missing, verify that the source platform actually stores those fields for the item.

FAQ​

What does NEXT create from each response?​

Each imported item becomes a Highlight so digital feedback can be analyzed with your other customer signals.

Does this support both GetFeedback and Usabilla?​

Yes. The integration covers the shared feedback API family used across those products.

Can I prepend metadata such as rating, NPS, or device to the comment text?​

Yes. In the subscription settings, you can define a LiquidJS template that NEXT renders before the imported free-text comment. This is useful when you want NEXT AI to see context fields directly in the text it analyzes.

For example:

Rating: {{ data.rating }} | NPS: {{ data.nps }} | Device: {{ deviceName }} ({{ osName }} {{ osVersion }})

If the original comment is:

I logged in via Google, and the app keeps failing.

NEXT imports it like this:

Rating: 2 | NPS: 80 | Device: iPhone 15 (iOS 17.5)

I logged in via Google, and the app keeps failing.

Which Usabilla or GetFeedback fields can I use in the template?​

The template is evaluated against the raw feedback item received from the provider. For Usabilla and GetFeedback, that means you can reference root-level fields such as {{ deviceName }}, nested response data such as {{ data.rating }}, and custom fields such as {{ customData.userAgent }} when they exist in that payload.

The exact field shape depends on the feedback type. For example:

  • Website forms and email feedback may expose nps at the root level, so you would use {{ nps }}.
  • App feedback may expose nps under data, so you would use {{ data.nps }}.

This inconsistency comes from the provider payload, not from NEXT. Check the feedback type you are importing and build the template against that payload shape.