Integrations
WebPinch connects to Jira, GitHub and Slack. Feedback still gets captured the same way — a pin becomes a task on your board — but the task can then be pushed into the tracker your engineers already live in, without anyone re-typing it.
How connecting works
There are two steps, and they happen in different places:
- Authorize the service once, for your account —
Dashboard → Settings → Integrations. This is the OAuth handshake with Jira, GitHub or Slack. - Link each project to one destination — in that project’s settings. A WebPinch project maps to exactly one Jira project, one GitHub repository, or one Slack channel.
The split exists because your account may have access to many repos, Jira projects and channels, but a given WebPinch project should push to exactly one of each. Authorize once; link per project.
Jira
Connects to Jira Cloud via Atlassian OAuth 2.0 (3LO).
Once your account is connected, pick which Jira project a WebPinch project maps to. WebPinch stores the project key (e.g. WEB) and the issue type to create, which defaults to Task.
Pushing a task to Jira. From a task, create a Jira issue. It’s idempotent — pushing the same task twice won’t create a duplicate. The issue description carries the context that was captured automatically:
- The task description
- Priority (mapped onto Jira’s priority scale)
- The page URL the feedback was pinned on
- Browser and OS
- Who reported it
- A link to the screenshot
- A link back to the WebPinch task
Coming back the other way. WebPinch registers a webhook on your Jira site so issue changes flow back to the task. Jira’s dynamic webhooks expire after 30 days and are refreshed automatically.
GitHub
Authorize GitHub for your account, then link a project to a single repository.
Pushing a task to GitHub creates an issue in the linked repo, with the same captured context as above.
Syncing back. WebPinch registers a webhook on the repo (if automatic registration fails, you’ll be shown the webhook secret to add it manually). Inbound events are verified against that secret, and:
- Closing or reopening a linked issue updates the WebPinch task
- Comments on a linked issue come back to the task
- Newly opened issues and pull requests feed repository context to the AI features
Slack
Authorize Slack for your account, then link a project to one channel.
Notifications — each is a toggle, so you can keep the channel as noisy or as quiet as you want:
| Event | Default |
|---|---|
| A task is created | On |
| A task is completed | On |
| A task is assigned | On |
| Scheduled standup summary | Off |
The /webpinch slash command works in any channel the app is in:
| Command | Does |
|---|---|
/webpinch status | Current state of the linked project |
/webpinch standup | Generate a standup summary on demand |
/webpinch create | Create a task without leaving Slack |
Which one should I use?
| You want | Use |
|---|---|
| Client feedback to become engineering tickets | Jira or GitHub |
| Your team to hear about feedback where they already talk | Slack |
| To build something custom | Webhooks or the REST API |
| Your AI assistant to read and manage tasks | MCP server |
Each integration links one destination per project — one Jira project, one repo, one channel. To push to two places, use webhooks alongside the integration.
Troubleshooting
“Connect” does nothing / returns an error. The integration has to be configured on the WebPinch instance with the provider’s client credentials. On self-hosted installs, check that the relevant client ID and secret are set.
Issues aren’t syncing back. Sync-back depends on the webhook. For GitHub, confirm the webhook exists on the repo and its secret matches. For Jira, reconnect — dynamic webhooks expire after 30 days.
Slack notifications stopped. Re-authorize Slack from Dashboard → Settings → Integrations; the workspace token may have been revoked.