If you’re new to Unstructured, read this note first.Before you can create a source connector, you must first sign in to your Unstructured account:
- If you do not already have an Unstructured account, sign up for free. After you sign up, you are automatically signed in to your new Unstructured Let’s Go account, at https://platform.unstructured.io. To sign up for a Business account instead, contact Unstructured Sales, or learn more.
- If you already have an Unstructured Let’s Go, Pay-As-You-Go, or Business SaaS account and are not already signed in, sign in to your account at https://platform.unstructured.io. For other types of Business accounts, see your Unstructured account administrator for sign-in instructions, or email Unstructured Support at support@unstructured.io.
-
After you sign in to your Unstructured Let’s Go, Pay-As-You-Go, or Business account, click API Keys on the sidebar.
For a Business account, before you click API Keys, make sure you have selected the organizational workspace you want to create an API key for. Each API key works with one and only one organizational workspace. Learn more. -
Click Generate New Key.
-
Follow the on-screen instructions to finish generating the key.
-
The generated key is displayed. Copy this key to a secure location, as you will not be able to access it again after you close the dialog. If you lose this key, you must generate a new one.
- A Zendesk account.
- Your Zendesk subdomain, for example, the
<organization>part of<organization>.zendesk.com. - The login email address for your Zendesk account.
- An API token (not an OAuth token) for your login email address.
<name>(required) - A unique name for this connector.<subdomain>(required): The subdomain of your Zendesk site, for example the<organization>part of<organization>.zendesk.com.<email>(required): The email address of the user account that has access to the Zendesk subdomain.<api-token>(required): The API token (not an OAuth token) for the user account. For more information, see Managing access to the Zendesk API.<item-type>: The type of item to parse. Allowed values includeticketsandarticles. If no value is provided, the default istickets.<batch-size>: The maximum number of items to structure per batch. The default is2.

