Zoho Billing Trigger icon

Zoho Billing Trigger

Starts the workflow when Zoho Billing webhook events are received

Zoho Billing Trigger

AI-generated

Summary

Starts a workflow when Zoho Billing sends a POST webhook to the node's URL, filtering events by organization and optionally by event type, and emitting one item per matching event.

Inputs

  • organizationId (required) — Zoho Billing organization, loaded from the API using the OAuth2 credential. Payloads whose organization_id (top-level or nested under organization) differs from this are dropped. Payloads with no organization ID are not dropped.
  • path — Webhook path segment (default "zoho-billing-webhook"). Use the resulting Production URL when configuring the webhook in Zoho Billing.
  • eventTypes — Multi-select of events such as subscription_created, invoice_created, payment_refunded, card_expiring. Matches against the payload's event_type. Leave empty to accept all events. When set, payloads with no event_type are dropped.
  • setupNotice — Display-only notice. Zoho Billing has no webhook registration API, so you must create the webhook manually under Settings → Automation → Workflow Actions → New Webhook, using method POST and the n8n Production URL. Create one per module.

Output shape

One output item per matching event. Each item's json has method, headers, query, organizationId (the selected one), event (the received payload object), and receivedAt (ISO timestamp).

The body may be a single object or an array, and each entry becomes its own item. If nothing matches, the workflow does not run, but the webhook still replies {"status":"ok"}. The response is sent immediately on receipt (responseMode onReceived). The node does not register the webhook itself, and it requires the zohoBillingOAuth2Api credential.

Examples

Example 1: Run a workflow whenever a new invoice is created.

Select the organization, leave Path as the default, and set Event Types to Invoice Created. In Zoho Billing, create a webhook on the Invoice module that POSTs to the Production URL.

Example 2: Alert on failed or refunded payments.

Select the organization and set Event Types to Payment Declined and Payment Refunded. Create a webhook on the Customer Payment module that points to the Production URL.

Example 3: Process every subscription lifecycle event.

Select the organization and leave Event Types empty. Create a webhook on the Subscriptions module that POSTs to the Production URL.

Links

Discussion