> ## Documentation Index
> Fetch the complete documentation index at: https://www.cashfree.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Relay Skills
> Use pre-built Cashfree Relay Skills to create common payment workflows instantly by describing what you need in plain language in Claude Desktop.
Cashfree Relay Skills are pre-built workflow templates that you invoke from **Claude Desktop** using plain language, after you connect the [Relay MCP server](/tools-ai/relay/relay-mcp-server). Instead of building a workflow manually on the canvas, you describe what you need; Claude collects the required inputs, validates them, and creates the workflow through MCP.
Relay Skills require the Relay MCP server to be connected in **Claude Desktop** (not the Claude web app). For **Customize** > **Connectors**, the MCP URL, and Merchant Dashboard sign-in, see [Relay MCP Server](/tools-ai/relay/relay-mcp-server). Gmail- and Sheets-based skills need existing connections on the Relay **Connections** tab—see [Setting Up Connections](/tools-ai/relay/add-connections).
## Supported clients
Relay Skills are available only when using **Claude** with MCP configured as described on the [Relay MCP Server](/tools-ai/relay/relay-mcp-server) page.
| Client | Notes |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Claude (desktop) | Install **Claude Desktop**, add the Relay connector under **Customize** > **Connectors**, complete sign-in at the Cashfree Merchant Dashboard, then use Skills from a chat. The web app does not support this flow. Connector access may depend on your Claude plan. |
Additional clients may be supported in a future release.
## How to invoke a skill
You can invoke a skill by describing your intent in plain language. You do not need to use an exact command or phrase. Claude matches your message to the most relevant skill and begins collecting any inputs it needs.
You can provide inputs in any of the following ways.
* **All at once**: Include all required details in your first message. Claude creates the workflow without asking follow-up questions.
* **Partial**: Provide some details and let Claude prompt you for the rest.
* **None**: State your general intent and Claude asks for each required input individually.
## Available skills
The following skills are available, grouped by category.
### Monitoring
The following skill monitors payment activity and sends alerts based on configured conditions.
Creates a workflow that triggers on payment success and sends an email alert when a transaction amount exceeds a configured threshold. Use this skill to monitor high-value transactions in real time.
**Required inputs**
| Input | Description | Example |
| ----------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Workflow Name | Name for the workflow. | `transaction-alerts-may2026` |
| Gmail Connection | An existing Gmail connection from your Relay Connections tab. | Select by number, name, or ID. |
| Threshold Amount | The minimum transaction amount that triggers an alert. | `50000` |
| Recipient Email Address | The email address to receive alerts. | `alerts@company.com` |
| Email Subject | The subject line for the alert email. Supports dynamic variables. | {'Transaction Alert - ${node_1.output.data.cfOrderId}'} |
| Email Body | The body of the alert email. Supports dynamic variables. | {'A transaction of ${node_1.output.data.amount} has been processed.'} |
**Optional inputs**
| Input | Description |
| ------------- | ------------------------------------------------------ |
| CC Addresses | Additional email addresses to copy on the alert. |
| BCC Addresses | Additional email addresses to blind copy on the alert. |
**Example prompts**
* Create a workflow named payment-alerts with threshold 50000, recipient [alerts@company.com](mailto:alerts@company.com), with subject {'Transaction Alert - ${node_1.output.data.cfOrderId}'}
* "Set up threshold notifications with amount 100000 and email [support@company.com](mailto:support@company.com)"
* "Create transaction threshold notifications"
Dynamic variables in the email subject and body use the format {'${node_1.output.data.VARIABLE_NAME}'}. Claude fetches an example payload to show you the available variables before creating the workflow.
### Reporting
The following skills run on a schedule and deliver transaction reports to a configured destination.
Creates a workflow that runs every hour and sends an email report summarising failed transactions for that period. Use this skill to keep your team informed about payment failures without manual checks.
**Required inputs**
| Input | Description | Example |
| ----------------------- | ------------------------------------------------------------------- | ----------------------------------- |
| Workflow Name | Name for the workflow. | `failed-transaction-hourly-may2026` |
| Gmail Connection | An existing Gmail connection from your Relay Connections tab. | Select by number, name, or ID. |
| Recipient Email Address | The email address to receive the report. | `alerts@company.com` |
| Schedule Time | The minute mark at which the report runs each hour. | `00` for the top of every hour. |
| Email Subject | The subject line for the report email. | `Hourly Failed Transaction Report` |
| Email Body Template | The body of the report email. Supports aggregated metric variables. | See note below. |
**Optional inputs**
| Input | Description |
| ------------- | ------------------------------------------------------- |
| CC Addresses | Additional email addresses to copy on the report. |
| BCC Addresses | Additional email addresses to blind copy on the report. |
**Example prompts**
* "Create hourly failed transaction reports sent to [alerts@company.com](mailto:alerts@company.com) with subject 'Failed Transactions - Last Hour' at 00 minutes"
* "Set up hourly email reports for failed transactions to [support@company.com](mailto:support@company.com)"
* "Create hourly report for failed transactions"
The email body can include aggregated metrics using variables such as {'${node_1.output.data.failedCount}'} and {'${node_1.output.data.totalFailedAmount}'}. Claude prompts you to define the body template if you do not provide it up front.
Creates a workflow that runs once a day and appends a transaction summary row to a specified Google Sheets spreadsheet. Use this skill to maintain a running log of daily payment activity without manual data entry.
**Required inputs**
| Input | Description | Example |
| ------------------------ | -------------------------------------------------------------------------------- | ------------------------------------------------ |
| Workflow Name | Name for the workflow. | `daily-transaction-summary-may2026` |
| Google Sheets Connection | An existing Google Sheets connection from your Relay Connections tab. | Select by number, name, or ID. |
| Spreadsheet ID or Name | The ID or display name of the target spreadsheet. | `1a2b3c4d5e6f7g8h9i0j` or `Daily Reports` |
| Sheet or Tab Name | The name of the specific tab to append rows to. | `Sheet1` |
| Schedule Time | The time at which the workflow runs each day, in 24-hour format. | `09:00` |
| Column Headers | A comma-separated list of column headers in the order they appear in the sheet. | `Date, Total Transactions, Total Amount, Status` |
| Summary Row Mapping | The aggregated values that map to each column, in the same order as the headers. | Provided interactively by Claude. |
**Example prompts**
* "Create a daily transaction summary workflow to Google Sheets at 09:00 with headers 'Date, Total Transactions, Total Amount' in spreadsheet 'Reports'"
* "Set up daily transaction summaries to sheets at 08:00"
* "Create daily transaction summary to Google Sheets"
The column order in **Column Headers** must match the order of values in **Summary Row Mapping**. Claude validates this before creating the workflow.
## What's next
Connect Claude Desktop to Relay via MCP before using Skills.
Create Gmail, Google Sheets, and other connections that these Skills rely on.
Build a workflow manually using the Relay canvas.