Shipeasy
Bugs & Requests

Connectors

Mirror new bug reports and feature requests out to a GitHub repo, a Google Sheet, or a Slack channel as they come in.

Production readyOn this page · 4 min readWorks with · Dashboard · Admin API

Connectors push every new bug report and feature request out to an external tool, so triage doesn't have to start in Shipeasy. Tickets themselves live on Home, the project's ops queue; a connector only mirrors them outward.

Where each one is set up

There is no single Connectors screen in the dashboard. Each destination has the surface that fits it:

These are the only destinations. Anything else is not available.

Events you can forward

Each connector subscribes to one or more lifecycle events:

EventFires when
bug.createdA bug is reported.
feature_request.createdA feature request is submitted.

By default both are selected.

Setting up a GitHub or Google Sheets connector

Both are created through the connector API, which returns the connector switched off; the provider's OAuth flow then attaches credentials and enables it.

Create the connector

POST /api/admin/connectors with { "provider": "github", "name": "Bugs → acme/app", "events": ["bug.created"] }. Use "google_sheets" for a sheet.

Authorize the provider

Complete the GitHub App install (pick which repos it can access) or the Google consent screen.

Pick the target

Update the connector with the repository and optional bug labels and feature labels, or the spreadsheet and tab, and set enabled: true.

Check it

Send a test — it opens a throwaway issue or appends a throwaway row, so you can confirm the wiring.

Setting up Slack

Connect

Open Settings → Notifications and click Connect Slack.

Add to Slack

Authorize the Shipeasy Slack app in your workspace. After consent you land back on the Notifications tab.

Pick a channel

Choose the default channel for Slack notifications. Individual events can override it in the events table below.

Slack does more than mirror

On every plan Slack receives bug, request, alert and platform-event cards with a coloured status border. On Pro and above those cards also carry resolve / ready-for-QA buttons, and you get a /shipeasy slash command and an @Shipeasy assistant that runs your flags and configs by chat. See the dedicated Slack page for what each plan includes.

Status & health

List the connectors to see each one's status — Needs OAuth, Needs repo / Needs sheet / Needs channel (target not picked yet), Active, Disabled, or Failing (last dispatch errored). The last error and last successful delivery time come back with it, so you can tell at a glance whether mirroring is healthy.

Connectors forward out — and Slack actions flow back

The GitHub and Sheets connectors are one-way: new bugs/requests flow out, and status changes you make there don't sync back. The Slack connector is the exception on Pro and above — its message buttons (resolve / ready-for-QA, resolve / dismiss alert) write straight back into Shipeasy.

Was this page helpful?
Updated November 20, 2026✎ Edit this page

On this page