|
| 1 | +--- |
| 2 | +title: Transform data in Zendesk (Preview) |
| 3 | +titleSuffix: Azure Data Factory & Azure Synapse |
| 4 | +description: Learn how to transform data in Zendesk (Preview) by using Data Factory or Azure Synapse Analytics. |
| 5 | +ms.author: jianleishen |
| 6 | +author: jianleishen |
| 7 | +ms.service: data-factory |
| 8 | +ms.subservice: data-movement |
| 9 | +ms.topic: conceptual |
| 10 | +ms.custom: synapse |
| 11 | +ms.date: 02/28/2022 |
| 12 | +--- |
| 13 | + |
| 14 | +# Transform data in Zendesk (Preview) using Azure Data Factory or Synapse Analytics |
| 15 | + |
| 16 | +[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)] |
| 17 | + |
| 18 | +This article outlines how to use Data Flow to transform data in Zendesk (Preview). To learn more, read the introductory article for [Azure Data Factory](introduction.md) or [Azure Synapse Analytics](../synapse-analytics/overview-what-is.md). |
| 19 | + |
| 20 | +## Supported capabilities |
| 21 | + |
| 22 | +This Zendesk connector is supported for the following activities: |
| 23 | + |
| 24 | +- [Mapping data flow](concepts-data-flow-overview.md) |
| 25 | + |
| 26 | +## Create a Zendesk linked service using UI |
| 27 | + |
| 28 | +Use the following steps to create a Zendesk linked service in the Azure portal UI. |
| 29 | + |
| 30 | +1. Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then select New: |
| 31 | + |
| 32 | + # [Azure Data Factory](#tab/data-factory) |
| 33 | + |
| 34 | + :::image type="content" source="media/doc-common-process/new-linked-service.png" alt-text="Screenshot of creating a new linked service with Azure Data Factory U I."::: |
| 35 | + |
| 36 | + # [Azure Synapse](#tab/synapse-analytics) |
| 37 | + |
| 38 | + :::image type="content" source="media/doc-common-process/new-linked-service-synapse.png" alt-text="Screenshot of creating a new linked service with Azure Synapse U I."::: |
| 39 | + |
| 40 | +2. Search for Zendesk (Preview) and select the Zendesk (Preview) connector. |
| 41 | + |
| 42 | + :::image type="content" source="media/connector-zendesk/zendesk-connector.png" alt-text="Screenshot showing selecting Zendesk connector."::: |
| 43 | + |
| 44 | +3. Configure the service details, test the connection, and create the new linked service. |
| 45 | + |
| 46 | + :::image type="content" source="media/connector-zendesk/configure-zendesk-linked-service.png" alt-text="Screenshot of configuration for Zendesk linked service."::: |
| 47 | + |
| 48 | +## Connector configuration details |
| 49 | + |
| 50 | +The following sections provide information about properties that are used to define Data Factory and Synapse pipeline entities specific to Zendesk. |
| 51 | + |
| 52 | +## Linked service properties |
| 53 | + |
| 54 | +The following properties are supported for the Zendesk linked service: |
| 55 | + |
| 56 | +| Property | Description | Required | |
| 57 | +|:--- |:--- |:--- | |
| 58 | +| type | The type property must be set to **Zendesk**. |Yes | |
| 59 | +| url | The base URL of your Zendesk service. | Yes | |
| 60 | +| authenticationType | Type of authentication used to connect to the Zendesk service. Allowed values are **basic** and **token**. Refer to corresponding sections below on more properties and examples respectively.|Yes | |
| 61 | + |
| 62 | +### Basic authentication |
| 63 | + |
| 64 | +Set the **authenticationType** property to **basic**. In addition to the generic properties that are described in the preceding section, specify the following properties: |
| 65 | + |
| 66 | +| Property | Description | Required | |
| 67 | +|:--- |:--- |:--- | |
| 68 | +| userName | The user name used to log in to Zendesk. |Yes | |
| 69 | +| password | Specify a password for the user account you specified for the user name. Mark this field as **SecureString** to store it securely. Or, you can [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). |Yes | |
| 70 | + |
| 71 | +**Example:** |
| 72 | + |
| 73 | +```json |
| 74 | +{ |
| 75 | + "name": "ZendeskLinkedService", |
| 76 | + "properties": { |
| 77 | + "type": "Zendesk", |
| 78 | + "typeProperties": { |
| 79 | + "url": "<base url>", |
| 80 | + "authenticationType": "basic", |
| 81 | + "userName": "<user name>", |
| 82 | + "password": { |
| 83 | + "type": "SecureString", |
| 84 | + "value": "<password>" |
| 85 | + } |
| 86 | + } |
| 87 | + } |
| 88 | +} |
| 89 | +``` |
| 90 | + |
| 91 | +### Token authentication |
| 92 | + |
| 93 | +Set the **authenticationType** property to **token**. In addition to the generic properties that are described in the preceding section, specify the following properties: |
| 94 | + |
| 95 | +| Property | Description | Required | |
| 96 | +|:--- |:--- |:--- | |
| 97 | +| apiToken | Specify an API token for the Zendesk. Mark this field as **SecureString** to store it securely. Or, you can [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). |Yes | |
| 98 | + |
| 99 | +**Example:** |
| 100 | + |
| 101 | +```json |
| 102 | +{ |
| 103 | + "name": "ZendeskLinkedService", |
| 104 | + "properties": { |
| 105 | + "type": "Zendesk", |
| 106 | + "typeProperties": { |
| 107 | + "url": "<base url>", |
| 108 | + "authenticationType": "token", |
| 109 | + "apiToken": { |
| 110 | + "type": "SecureString", |
| 111 | + "value": "<API token>" |
| 112 | + } |
| 113 | + } |
| 114 | + } |
| 115 | +} |
| 116 | +``` |
| 117 | + |
| 118 | +## Mapping data flow properties |
| 119 | + |
| 120 | +When transforming data in mapping data flow, you can read tables from Zendesk. For more information, see the [source transformation](data-flow-source.md) in mapping data flows. You can only use an [inline dataset](data-flow-source.md#inline-datasets) as source type. |
| 121 | + |
| 122 | +### Source transformation |
| 123 | + |
| 124 | +The below table lists the properties supported by Zendesk source. You can edit these properties in the **Source options** tab. |
| 125 | + |
| 126 | + |
| 127 | +| Name | Description | Required | Allowed values | Data flow script property | |
| 128 | +| ---- | ----------- | -------- | -------------- | ---------------- | |
| 129 | +| Entity | The logical name of the entity in Zendesk. | Yes when use inline mode| `activities`<br/>`group_memberships`<br/>`groups`<br/>`organizations`<br/>`requests` <br/>`satisfaction_ratings`<br/>`sessions`<br/>`tags`<br/>`targets`<br/>`ticket_audits`<br/>`ticket_fields`<br/>`ticket_metrics`<br/>`tickets`<br/>`triggers`<br/>`users`<br/>`views` | entity | |
| 130 | + |
| 131 | +#### Zendesk source script examples |
| 132 | + |
| 133 | +``` |
| 134 | +source(allowSchemaDrift: true, |
| 135 | + validateSchema: false, |
| 136 | + store: 'zendesk', |
| 137 | + format: 'rest', |
| 138 | + entity: 'tickets') ~> ZendeskSource |
| 139 | +``` |
| 140 | + |
| 141 | +## Next steps |
| 142 | + |
| 143 | +For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats). |
0 commit comments