Razorpay

Platform billing webhooks: see API Webhooks. Connector events are separate namespaced emits for your tenant flows.

Note

Namespace convention: events under razorpay.*. Connectors emit only; FlowRunner stays in Qefro.

Installation

1. Deploy or enable the Razorpay connector service (Qefro connectors monorepo / your fork).
2. Configure credentials (below) and QEFRO_API_BASE_URL, QEFRO_TENANT_ID, API token.
3. Point external webhooks at the connector public URL (not directly at FlowRunner).
4. In Qefro, declare flows with trigger.event matching emitted names — Event-Driven Triggers.
5. Sync SDK tools if the connector exposes Backend SDK handlers.

Authentication

Key id/secret; Qefro also consumes billing webhooks for SaaS entitlements.

Store secrets in the connector environment or secret manager — not in flow metadata.

Events

Event name	Notes
razorpay.payment.captured	Emit when source system notifies connector
razorpay.payment.failed	Emit when source system notifies connector

Envelope fields (idempotency, correlation, TTL): Event reference.

Tools

Typical tool surface: payment lookup.

Implement as Backend SDK tools or REST Business Tools. Keep PII minimization and least privilege scopes.

Webhooks

1. Receive provider webhook → verify signature.
2. Normalize payload → EventEmitter.emit({ name: 'razorpay.…', payload, idempotencyKey }).
3. Return 2xx quickly; let Qefro dispatch asynchronously.

Examples

• Abandoned cart pattern: Solutions — Abandoned cart (Shopify-oriented; adapt event names).
• Order tracking: Solutions — Order tracking.

Workflow checklist

Razorpay go-live

1. Auth — Least-privilege credentials in connector env.
2. Webhooks — Verify signatures; map to razorpay.* events.
3. Flows — Enable flows with matching trigger.event.
4. Test emit — Idempotent test event; watch Flow Runs.
5. Observe — Event list + tool logs + dead-letter retry.

Related topics