Beyond ready-made channels like app stores, email, and communities, Loopback also lets you bring in feedback from your own systems and integrate programmatically through the API.

Generic Webhook: push your own feedback

If feedback comes from your own systems — an in-app feedback form, internal tickets, the feedback entry point of a custom app — you can push it to Loopback through a generic Webhook, with no email or third-party channel in between.

Feedback pushed in is treated just like any other channel: on arrival it's understood by AI (sentiment, priority, category, owning module), clustered into issues, and lands on the unified board. Add a Webhook channel on the Channels page (/channels) to get the push URL and format spec.

API access

The API lets you plug Loopback into your own toolchain — pull issue, feedback, and report data programmatically, or sync processing status back to your systems.

API access is a Max and above capability (not included in Pro). For a plan comparison, see Understanding Plans and Tokens and the pricing page.

When to use Webhook / API

  • You have a custom feedback entry point → a Webhook funnels it into one place.
  • You want to sync issues to internal systems / BI → use the API to pull data.
  • You want to trigger Loopback actions from your own flows → the API paired with workflows.

One bottom line never changes

Whichever integration path you take, outbound sending always requires human confirmation — the API is no exception. There is no automated outbound-reply channel that bypasses confirmation. This is Loopback's hard safety boundary.

What to do when a connection fails

Every channel on the Channels page (Webhook included) shows a health status and recent errors. A failed Webhook push is usually a format or auth issue — check it against the format spec on the Channels page.