Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Zuora

Cloud-based subscription management platform that enables businesses to launch and monetize subscription services.

CategorySales And Crm
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedOctober 6, 2026

Overview

Connect Zuora with Flows360

Cloud-based subscription management platform that enables businesses to launch and monetize subscription services.

Use the Zuora 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 4 actions and no declared triggers.

Available actions

  • Create Invoice
  • Find Customer Account
  • Find Product Rate Plan
  • Find Product

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: Zuora
  • Package: @activepieces/piece-zuora@0.1.6
  • Exact artifact digest: sha256:40f544e7c614c6cbdcc51dbf90854e952839c0efe8c613fd5bcee25784de3d89
  • 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 Invoice (create-invoice), Create a standalone invoice. Classification: read.
  • Find Customer Account (find-account), Retrieves account based on name. Classification: read.
  • Find Product Rate Plan (find-product-rate-plan), Retrieves product rate plan with charges. Classification: read.
  • Find Product (find-product), Retrieves product based on sku. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Client ID Required
  • Client Secret Required · protected credential
  • Environment Required

Supported objects

ObjectReadWriteNotes
Create Invoice Yes No Create a standalone invoice.
Find Customer Account Yes No Retrieves account based on name.
Find Product Rate Plan Yes No Retrieves product rate plan with charges.
Find Product Yes No Retrieves product based on sku.

Supported actions

Create Invoice · Read

Create a standalone invoice.

create_invoice · Risk: low · Retry: safe

Inputs

  • accountNumber · string · Required, The number of the customer account associated with the invoice.
  • autoPay · boolean · Optional, Whether invoices are automatically picked up for processing in the corresponding payment run.
  • comments · string · Optional
  • dueDate · string · Required, Provide YYYY-MM-DD format.
  • invoiceDate · string · Required, Provide YYYY-MM-DD format.
  • invoiceItems · array · Optional
  • status · string · Optional
Find Customer Account · Read

Retrieves account based on name.

find_account · Risk: low · Retry: safe

Inputs

  • name · string · Required
Find Product Rate Plan · Read

Retrieves product rate plan with charges.

find_product_rate_plan · Risk: low · Retry: safe

Inputs

  • name · string · Required, i.e. StealthCo Premium
  • productid · string · Required
Find Product · Read

Retrieves product based on sku.

find_product · Risk: low · Retry: safe

Inputs

  • sku · string · Required

Setup

Setup

  1. Add the Zuora 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:
  • Client ID (clientId), required.
  • Client Secret (clientSecret), required; stored as a sensitive connection value.
  • Environment (environment), required.
  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-zuora@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 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

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Zuora connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-zuora@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com