Playrunner integrations
Integrations
Explore the integrations currently included in Playrunner builds. Each provider page describes its available user setup and package surfaces.
Jira
Create and sync Jira tickets from Playrunner workflows.
npm install @playrunner/jiraJavaScript
Configure JavaScript workflow nodes; execution support is not yet implemented.
npm install @playrunner/javascriptGitHub
Connect repositories and manage GitHub authentication.
npm install @playrunner/githubGCP
Connect Google Cloud and configure GCP runner infrastructure.
npm install @playrunner/gcpEnvironment
Manage reusable environment variables for workflow nodes.
npm install @playrunner/environmentSchedule
Configure workflows that are started by saved schedules.
npm install @playrunner/scheduleOpenAI
Generate text and structured output with OpenAI models.
npm install @playrunner/openaiHugging Face
Run hosted open-source models through Hugging Face Inference Providers.
npm install @playrunner/huggingfacePlaywright
Run Playwright test workflows with repository-backed configuration.
npm install @playrunner/playwright @playrunner/githubResend
Send email or wait for inbound messages, verification codes, and attachments.
npm install @playrunner/resendSlack
Send notifications and alerts to Slack channels.
npm install @playrunner/slackWebhooks
Receive inbound workflow triggers and send outbound HTTPS requests.
npm install @playrunner/webhooksBuild-time selection and runtime configuration
The install commands above are for the operator or build pipeline assembling a Playrunner artifact. A running Playrunner deployment never installs integration code from the marketplace or scans for new packages.
At runtime, users can connect credentials, add an integration node already bundled into the deployment, choose its action, connect it to other nodes, and edit its fields. Those operations update saved settings and workflow data; they do not change the installed code.
Adding, upgrading, or removing an integration package requires rebuilding every application or runner image that consumes one of its declared surfaces. Cloud deployments must then publish and roll out the rebuilt artifacts.
Building an integration
Package authors should use the Development → Integrations guide. It documents the self-contained package contract and its three optional contribution surfaces:
- Frontend contributions provide integration metadata and package-owned React configuration UI.
- API contributions provide a stable mount path and package-owned Express router.
- Orchestrator contributions provide trusted, versioned workflow executors.
All three surfaces are declared by the package, selected as direct production dependencies of the consuming artifact, and composed into static imports at build time. Package authors do not add their provider to a shared registry or host allowlist.