Cashfree Payments

Overview

Connect Cashfree Payments with Flows360

Cashfree Payments integration for processing payments, refunds, and managing payment links and cashgrams.

Use the Cashfree Payments connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and no declared triggers.

Available actions

• Create Order
• Create Payment Link
• Create Refund
• Cancel Payment Link
• Fetch Payment Link Details
• Create Cashgram
• Get Orders for Payment Link
• Get All Refunds for Order
• Plus 1 additional declared action.

Available triggers

• No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: Cashfree Payments
• Package: @activepieces/piece-cashfree-payments@0.1.8
• Exact artifact digest: sha256:a5277df139070216708c51fb9e395e91ee52f61f16da3ecad70ca9738d40f0eb
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Create Order (create-order), Creates an order in Cashfree Payment Gateway Classification: read.
• Create Payment Link (create-payment-link), Creates a payment link in Cashfree Payment Gateway Classification: read.
• Create Refund (create-refund), Initiate a refund for a Cashfree order. Refunds can only be initiated within six months of the original transaction. Classification: read.
• Cancel Payment Link (cancel-payment-link), Cancel a payment link in Cashfree Payment Gateway. Only links in ACTIVE status can be cancelled. Classification: read.
• Fetch Payment Link Details (fetch-payment-link-details), View all details and status of a payment link in Cashfree Payment Gateway Classification: read.
• Create Cashgram (create-cashgram), Create a Cashgram for instant money transfers using Cashfree Classification: read.
• Get Orders for Payment Link (get-orders-for-payment-link), View all order details for a payment link in Cashfree Payment Gateway Classification: read.
• Get All Refunds for Order (get-all-refunds-for-order), Fetch all refunds processed against an order in Cashfree Payment Gateway Classification: read.
• Deactivate Cashgram (deactivate-cashgram), Deactivate a Cashgram to prevent further redemptions using Cashfree Classification: read.

Trigger contracts

• No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Setup

Setup

1. Add the Cashfree Payments connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• Cashfree Client ID (clientId), optional.
• Cashfree Client Secret (clientSecret), optional; stored as a sensitive connection value.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-cashfree-payments@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 9 actions and 0 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Related documentation