---
title: "How do I connect Genesys Cloud?"
description: "TL;DR: Connect Genesys Cloud to Ballet with an OAuth client and an Architect Process Automation Flow HTTP action that posts events to a Ballet webhook."
canonical_url: "https://docs.ballet.dev/articles/how-do-i-connect-genesys-cloud-PuNN7VxX5y"
md_url: "https://docs.ballet.dev/articles/how-do-i-connect-genesys-cloud-PuNN7VxX5y.md"
---
# How do I connect Genesys Cloud?

TL;DR: Connect Genesys Cloud to Ballet with an OAuth client and an Architect Process Automation Flow HTTP action that posts events to a Ballet webhook.

Back to: [How do I connect CRM and support tools?](/articles/how-do-i-connect-crm-and-support-tools-5h3LJzY5x8)

> **Status:** Draft outline for customer handoff.

## Patterns

## Outline: inbound webhook


1. In Ballet, add a **Webhook** trigger and choose the **Genesys Cloud** provider. Copy the trigger URL.
2. Store a bearer token in Ballet [Secrets](/articles/how-do-i-store-credentials-with-secrets-1D8OUcCo0n).
3. In Genesys Cloud, create an OAuth client (Client Credentials) and obtain an access token for the integration.
4. In Architect, build a Process Automation Flow with an HTTP integration action.
5. Send the event to the Ballet URL with Authorization set to `Bearer <token>`.

See: [How do I trigger and react to playbooks with webhooks?](/articles/how-do-i-trigger-and-react-to-playbooks-with-webhooks-DYv9XyeU51)

Genesys docs: [Process Automation](https://developer.genesys.cloud/devapps/process-automation/)

## Outline: API access (optional)


1. Create a dedicated Genesys OAuth client with the minimum scopes required.
2. Store Client ID / Client Secret (or short-lived tokens) in Secrets.
3. Use HTTP or MCP steps in the playbook as needed.