Genesys Cloud CI/CD with CircleCI.
Trigger InProd changeset validation and deployment from CircleCI — with approval-gated workflow promotion, Simulate Run before every environment, and deployment evidence stored as CircleCI artifacts at every stage of your Genesys Cloud CircleCI pipeline.
How It Works
Three steps from a reviewed change to a recorded production deployment.
Define changes as an InProd changeset
Package your Genesys Cloud configuration changes — routing flows, queue definitions, skill mappings, data actions — into governed deployment units managed in InProd and triggered from your CircleCI workflow.
Validate on every branch
Automatically trigger a validate-only job on every non-main branch. InProd runs Simulate Run against the target environment and reports exactly what would change — before anything merges.
Promote through Dev, UAT, and Production with approval gates
Use CircleCI's type: approval jobs to require explicit sign-off between environments. InProd handles environment-aware variable mapping and deployment execution; CircleCI governs who triggers each promotion.
What You Get
Automatic validation on every push
Every Genesys Cloud configuration change is automatically verified against the live target environment as part of your CircleCI workflow — not after it reaches production.
Approval-gated environment promotion
CircleCI's type: approval jobs act as manual gates between environments. No stage runs until the right person approves — enforced at the workflow level.
Simulate Run before each environment
InProd executes a pre-deployment simulation showing exactly what will be created, updated, or deleted — including environment-specific differences invisible to a standard diff.
CircleCI artifacts for deployment evidence
inprod-result.json is stored as a named artifact after every run, accessible from the CircleCI UI and providing an immutable deployment record for compliance review.
Rollback from pipeline or InProd UI
Revert to a previous state using InProd's point-in-time restore — without manual reconstruction of what the configuration was before the change.
Works With Your Existing CircleCI Setup
No custom infrastructure required. InProd runs via npx @inprod.io/run-changesets in any CircleCI job using a Node.js Docker image. Your existing contexts, project environment variables, branch filters, and workflow structure all apply — InProd adds Genesys Cloud-specific validation and deployment governance on top of the pipeline you already run.
This makes it straightforward to add CX as Code deployments to a CircleCI workflow your team already understands.
Frequently Asked Questions
Why use CircleCI for Genesys Cloud deployments instead of manual promotion?
Manual promotion relies on engineers replicating the same steps correctly across Dev, UAT, and Production every time. CircleCI enforces the same process on every release — validation runs automatically, approval jobs require explicit sign-off before production, and every deployment stores an artifact record. The pipeline removes the process variability that causes most configuration-related incidents.
How do CircleCI approval gates work with InProd?
CircleCI's type: approval jobs pause the workflow until an authorized user approves from the CircleCI dashboard. The downstream deployment job only runs after approval. InProd then runs Simulate Run and executes the changeset within that approved job — so every promotion is explicit and recorded.
What is the difference between CircleCI and GitHub Actions for Genesys Cloud?
Both platforms run the same InProd changeset execution and produce the same Dev to UAT to Production promotion flow. CircleCI is often preferred by teams that need fine-grained Docker executor control, resource class tuning, or centralized org-level credential contexts. GitHub Actions is the right choice for teams already standardized on GitHub. The InProd deployment behaviour is identical across both.
Does this work with CX as Code and Terraform?
Yes. InProd sits alongside your CX as Code and Genesys Cloud Terraform workflows. Terraform manages desired-state definitions; InProd governs the deployment lifecycle — Simulate Run, promotion gates, drift detection, and the audit trail. CircleCI can trigger both Terraform applies and InProd changeset deployments within the same workflow.
Need the full pipeline picture? Genesys Cloud CI/CD Pipeline →
Your Genesys Cloud CircleCI Pipeline, Governed.
Every configuration change validated automatically, promoted through approval gates, and recorded as a CircleCI artifact — before the next incident forces the issue.
Book a Consultation