Connected platforms.
When a Salesforce symptom has its root cause somewhere else, Speakeasy can trace into the systems you connect — today, GitHub, Railway, and Jira.
Overview
Connected platforms are the agent's outbound connectors — systems it reaches into during an investigation to find a root cause beyond Salesforce. This is separate from the Integration API, which is how external systems submit requests to Speakeasy.
Supported Systems
We'd rather be precise than impressive. Here is exactly what is wired today:
| System | Status | Notes |
|---|---|---|
| Salesforce | Live | Core product. |
| GitHub | Live | Full read plus a gated write/PR surface. |
| Railway | Live | Deployments, logs, and services for runtime tracing. |
| Jira | Live | Read (search/issue/comments/projects) plus approval-gated writes (create/comment/transition). |
| Linear | Not a live connector | Recipe capability descriptor only; no runtime client. |
| Heroku / Vercel / generic | Reserved | Placeholder types with no connector yet. |
Only Salesforce, GitHub, Railway, and Jira are wired for live investigation. Linear and the reserved types are not tracing targets today.
How Connections Work
Connections are stored per organization, not globally. Each connection records the platform, an auth method (OAuth, token, or SSH key), encrypted tokens at rest, and a status (active, expired, revoked, error). Only active connections are exposed to the agent, and each is unique per org, platform, and external id.
GitHub
The GitHub connector covers four tool groups:
- Repository - read repo contents, files, commits, branches
- Collaboration - issues, pull requests, reviews
- Actions - workflow runs and CI status
- Mutations - a write surface (e.g. creating or updating content and PRs)
Writes are gated
GitHub mutations are high-risk write operations and follow the same human-approval posture as Salesforce deploys — they are not auto-applied.
Railway
The Railway connector exposes deployments, build/runtime logs, and service inventory. This is what lets the agent follow a Salesforce-surfaced error into the runtime service that actually threw it.
Jira
The Jira connector covers two tool groups:
- Issues - search by JQL, read an issue, read its comments, and list projects
- Mutations - a write surface: create an issue, add a comment, transition an issue's status
Connections authenticate with a Jira Cloud API token (the account email and site URL are stored alongside it; only the token is encrypted). Comment and description text is sent in Atlassian Document Format.
Writes are gated
Creating issues, commenting, and transitioning all follow the same human-approval posture as GitHub and Salesforce writes — they are not auto-applied.