Connectors
Mirror new bug reports and feature requests out to a GitHub repo, a Google Sheet, or a Slack channel as they come in.
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:
Slack→
Connect Slack authorizes the Shipeasy Slack app, then you pick a default channel. Posts a
message per event, with action buttons, a /shipeasy command and an
@Shipeasy assistant. Full Slack page →
GitHub→
Opens an Issue (with labels) in a repository you pick for every selected event. Create the connector with the API, then finish the GitHub App install.
Google Sheets→
Appends a row to a spreadsheet and tab of your choice for every selected event.
Coding agents→
Claude, Cursor and Copilot connectors run an agent on your queue instead of mirroring it. See Scheduled triggers.
These are the only destinations. Anything else is not available.
Events you can forward
Each connector subscribes to one or more lifecycle events:
| Event | Fires when |
|---|---|
bug.created | A bug is reported. |
feature_request.created | A 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.
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.
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.
Inbound alerts
File incidents from Google Cloud Monitoring, Prometheus Alertmanager, Grafana, AWS CloudWatch, Azure Monitor, Datadog — or any tool that can POST JSON — as alert tickets in your ops queue, with no relay to build or keep alive.
Slack
Get alerts, errors, bugs and platform events in Slack on every plan — and on Pro and above, act on them from the card buttons, the /shipeasy command and the @Shipeasy assistant.