Zuora

The Zuora connector lets you connect to a Zuora instance and access Zuora data as a traditional database.

Supported versions

This connector leverages the Zuora API version v1 to enable bidirectional access to Zuora.

Before you begin

Before using the Zuora connector, do the following tasks:

In your Google Cloud project:
- Ensure that network connectivity is set up. For information about network patterns, see Network connectivity.
- Grant the roles/connectors.admin IAM role to the user configuring the connector.
- Grant the following IAM roles to the service account that you want to use for the connector:
  - roles/secretmanager.viewer
  - roles/secretmanager.secretAccessor
  A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. For more information, see Creating a service account.
- Enable the following services:
  - secretmanager.googleapis.com (Secret Manager API)
  - connectors.googleapis.com (Connectors API)
  To understand how to enable services, see Enabling services.
If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.

Configure the connector

Configuring the connector requires you to create a connection to your data source (backend system). A connection is specific to a data source. It means that if you have many data sources, you must create a separate connection for each data source. To create a connection, do the following steps:

In the Cloud console, go to the Integration Connectors > Connections page and then select or create a Google Cloud project.
Go to the Connections page
Click + Create new to open the Create Connection page.
In the Location section, choose the location for the connection.
1. Region: Select a location from the drop-down list.
  Supported regions for connectors include:
  For the list of all the supported regions, see Locations.
2. Click Next.
In the Connection Details section, complete the following:
1. Connector: Select Zuora from the drop down list of available Connectors.
2. Connector version: Select the Connector version from the drop down list of available versions.
3. In the Connection Name field, enter a name for the Connection instance.
  Connection names must meet the following criteria:
  - Connection names can use letters, numbers, or hyphens.
  - Letters must be lower-case.
  - Connection names must begin with a letter and end with a letter or number.
  - Connection names cannot exceed 49 characters.
4. Optionally, enter a Description for the connection instance.
5. Optionally, enable Cloud logging, and then select a log level. By default, the log level is set to Error.
6. Service Account: Select a service account that has the required roles.
7. Optionally, configure the Connection node settings:
  - Minimum number of nodes: Enter the minimum number of connection nodes.
  - Maximum number of nodes: Enter the maximum number of connection nodes.
  A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
8. Tenant: Set this to your Zuora tenant. By default we use "USProduction" tenant.
9. URL: This is required only in case you have a US Production Copy environment. If this property is provided, the value of Tenant property has no effect in authentication process.
10. ZuoraService: Specifies which execution service or schema to use
11. Use Client Side Paging: Whether or not the CData ADO.NET Provider for SAP Cloud for Customer should use client side paging.
12. Use Custom Service: Indicates if the custom SAP Cloud for Customer OData service should be used.
13. User Defined Views: A filepath pointing to the JSON configuration file containing your custom views.
14. Optionally, click + Add label to add a label to the Connection in the form of a key/value pair.
15. Click Next.
In the Authentication section, enter the authentication details.
1. Select an Authentication type and enter the relevant details.
  The following authentication types are supported by the Zuora connection:
  - OAuth 2.0 Client Credentials
2. Click Next.
Review: Review your connection and authentication details.
Click Create.

Configure authentication

Enter the details based on the authentication you want to use.

OAuth 2.0 Client Credentials
- Client ID: The client id provided by connector for the app you created.
- Client Secret: Secret Manager Secret containing the client secret for the connected app you created.

Entities, operations, and actions

All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.

Entity: An entity can be thought of as an object, or a collection of properties, in the connected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.
However, it is possible that a connector doesn't support or have any entities, in which case the Entities list will be empty.
Operation: An operation is the activity that you can perform on an entity. You can perform any of the following operations on an entity:
- List
- Get
- Create
- Update
- Delete
Selecting an entity from the available list, generates a list of operations available for the entity. For a detailed description of the operations, see the Connectors task's entity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in the Operations list.
Action: An action is a first class function that is made available to the integration through the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case the Actions list will be empty.

Entity operation examples

This section shows how to perform some of the entity operations in this connector.

Example - List all the records in Refunds

This example lists all the records in the Refunds entity.

In the Configure connector task dialog, click Entities.
Select Refunds from the Entity list.
Select the List operation, and then click Done.
Optionally, in Task Input section of the Connectors task, you can filter your result set by specifying a filter clause.

Example - Get a debit memo record

This example gets a record whose ID is 45 from the Debit_Memo entity.

In the Configure connector task dialog, click Entities.
Select Debit_Memo from the Entity list.
Select the Get operation, and then click Done.
In the Task Input section of the Connectors task, click EntityId and then enter 45 in the Default Value field.
Here, 45 is a primary key value in the Debit_Memo entity.

Example - Create a ticket

This example creates a ticket in the Ticket entity.

In the Configure connector task dialog, click Entities.
Select Tickets from the Entity list.
Select the Create operation, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
{
"Name": "Test735362767",
"Label": "Test735362767",
"Type": "String",
"FieldType": "Insert ticket1",
"GroupName": "ticketinformation",
"Description": "Test ticket"
}
```
If the integration is successful, your connector task's connectorOutputPayload field will have a value similar to the following:
```
{
"Name": "Test1695971640609"
}
```

Example - Update a deals entry

This example updates the record whose ID is 97 in the Deals entity.

In the Configure connector task dialog, click Entities.
Select Deals from the Entity list.
Select the Update operation, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
{
"Description": "New description"
}
```
Click entityId, and then enter 97 in the Default Value field.
Alternately, instead of specifying the entityId, you can also set the filterClause to 97.

Example - Delete a form

This example deletes the record whose ID is 78 in the Forms entity.

In the Configure connector task dialog, click Entities.
Select Forms from the Entity list.
Select the Delete operation, and then click Done.
In the Task Input section of the Connectors task, click entityId and then enter 78 in the Default Value field.

Use terraform to create connections

You can use the Terraform resource to create a new connection.

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

To view a sample terraform template for connection creation, see sample template.

When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:

Parameter name	Data type	Required	Description
tenant	ENUM	False	Set this to your Zuora tenant. By default we use "USProduction" tenant. Supported values are: USProduction, USAPISandbox, USPerformanceTest, EUProduction, EUSandbox, EUCentralSandbox, USCloudProduction, USCloudAPISandbox, USCentralSandbox
url	STRING	False	This is required only in case you have a US Production Copy environment. If this property is provided, the value of Tenant property has no effect in authentication process.
zuora_service	ENUM	False	Specifies which execution service or schema to use Supported values are: DataQuery, AQuADataExport
use_client_side_paging	BOOLEAN	False	Whether or not the CData ADO.NET Provider for SAP Cloud for Customer should use client side paging.
use_custom_service	BOOLEAN	False	Indicates if the custom SAP Cloud for Customer OData service should be used.
user_defined_views	STRING	False	A filepath pointing to the JSON configuration file containing your custom views.

Use the Zuora connection in an integration

After you create the connection, it becomes available in both Apigee Integration and Application Integration. You can use the connection in an integration through the Connectors task.

To understand how to create and use the Connectors task in Apigee Integration, see Connectors task.
To understand how to create and use the Connectors task in Application Integration, see Connectors task.

Get help from the Google Cloud community

You can post your questions and discuss this connector in the Google Cloud community at Cloud Forums.

What's next

Understand how to suspend and resume a connection.
Understand how to monitor connector usage.
Understand how to view connector logs.