Connect Slack, Linear and Jira
Route the right pins to the right place with per-event integrations — Slack alerts, Linear issues, Jira tickets and webhooks.
On this page
Pogpin is the front door for feedback, not a replacement for your engineering tracker. Integrations let each pin flow to wherever the work actually happens — and per-event routing means you’re not spamming a channel with every comment.
Connect an integration
- Open Settings → Integrations.
- Choose a provider and authorize with OAuth.
- Map Pogpin events to actions in the target tool.
No webhook plumbing required for the first-party integrations — the OAuth handshake is the whole setup.
Route by event, not firehose
The key to a quiet, useful integration is mapping specific events:
- New P1 pin → post to
#bugsin Slack. - Pin marked In progress → create a Linear issue in the current cycle.
- Pin resolved by a guest → comment back on the linked Jira ticket.
Everything else stays in Pogpin until someone triages it. That keeps Slack signal high and your tracker free of noise.
Two-way sync
For Linear and Jira, status flows both directions. Close the linked ticket and the Pogpin pin moves to Resolved; reopen it and the pin follows. Reviewers see the resolution without ever touching your tracker.
Build your own with webhooks and the API
Need something custom? Every event is available as a signed webhook, and the REST API exposes pins, issues and comments:
curl https://api.pogpin.com/v1/issues \
-H "Authorization: Bearer $POGPIN_TOKEN"Use it to sync to an internal data warehouse, trigger CI checks, or post to a tool we don’t integrate with natively.
Tip: start with one Slack route and one tracker route. Add more only when you feel a gap — over-wiring integrations on day one is the fastest way to channel fatigue.