Integrations Directory
Connect your release workflow to operational evidence
ShipTale integrates read-only with developer infrastructure to construct automated release stories. Use Vercel or GitHub to establish production release timing and change context, then correlate Sentry error spikes, PostHog conversion measurements, and Stripe revenue changes.
Supported Integrations
Every integration uses read-only access, encrypts credentials at rest, and adheres strictly to explicit retention boundaries.
GitHub
Trigger release stories from GitHub production deployments or Actions workflows, enriched with commit messages, SHAs, and merged PR context.
- Role
- Release Anchor & Commit Context
- Credentials
- Fine-grained Personal Access Token (Read-only)
- Sync
- Webhooks + 15m reconciliation
Vercel
Anchor releases to production Vercel deployments, isolating preview builds and mapping environments cleanly to your projects.
- Role
- Release Anchor
- Credentials
- Read-only Access Token
- Sync
- Webhooks + 15m reconciliation
Sentry
Correlate issue regressions and error frequency spikes after releases with transparent, evidence-based confidence ratings.
- Role
- Error & Quality Tracking
- Credentials
- Internal Integration Auth Token (Read-only)
- Sync
- 15m polling
PostHog
Measure trend and funnel conversion shifts with aggregate snapshots taken 1 hour and 24 hours post-release for up to 3 saved insights.
- Role
- Post-Release Measurement
- Credentials
- Personal API Key (Read-only)
- Sync
- +1h and +24h checkpoints
Stripe
Observe supported dispute, payment, and subscription events beside your releases with restricted read keys.
- Role
- Customer Context
- Credentials
- Restricted API Key (Read-only)
- Sync
- 15m polling
Security & Permission Principles
| Provider | Supported Read Scope | Strictly Excluded / Forbidden |
|---|---|---|
| GitHub | Deployments, workflow runs, commits, and merged PR metadata | Writing code, pushing branches, merging PRs, triggering workflows |
| PostHog | Aggregate trend & funnel snapshots for up to 3 saved insights | Raw events, person profiles, distinct IDs, session recordings |
| Vercel | Production deployments, commit SHAs, project identity | Triggering deployments, modifying environment variables |
| Sentry | Normalized issue regressions, occurrence counts, severity | Stack traces, breadcrumbs, resolving issues in Sentry |
| Stripe | Restricted read access to charges, refunds, disputes, and subscriptions | Secret keys, modifying customer billing, initiating charges |
Frequently asked questions
- Does ShipTale require write permissions to my repositories or analytics?
- No. ShipTale strictly operates with read-only permissions across all providers. We never push code, merge pull requests, trigger workflows, modify dashboards, or resolve errors in external tools.
- Can I connect both GitHub and Vercel in the same project?
- Yes. You can configure GitHub as your release anchor for commit and pull request context, or use Vercel for deployment events, while linking other quality and analytics providers to the resulting release Tales.
- Does ShipTale store raw user event data or customer identities from PostHog?
- No. ShipTale records aggregate numeric snapshots (counts and percentages) for up to 3 saved insights at 1-hour and 24-hour intervals. It never stores raw event payloads, user distinct IDs, or session recordings.
- How does correlation differ from causation in ShipTale?
- ShipTale organizes events and measurements that occur in defined time windows immediately following a production deployment. This provides essential operational visibility, but reflects correlation, not definitive proof that a release caused the change.
- What happens when an integration is disconnected?
- Disconnecting immediately purges encrypted credentials from the vault and halts future data synchronization. Existing historical Tales remain intact in your workspace.
Start your first Tale
Connect GitHub, Vercel, Sentry, and PostHog for free.