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, go to https://unstructured.io/contact and fill out the online form to indicate your interest.
  • If you already have an Unstructured account, sign in by using the URL of the sign in page that Unstructured provided to you when your Unstructured account was created. If you do not have this URL, contact Unstructured Sales at sales@unstructured.io.
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.You can also create source connectors with the Unstructured API. Learn how.If you need help, reach out to the community on Slack, or contact us directly.You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Zendesk. The requirements are as follows.
  • 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.
To create the source connector:
  1. On the sidebar, click Connectors.
  2. Click Sources.
  3. Cick New or Create Connector.
  4. Give the connector some unique Name.
  5. In the Provider area, click Zendesk.
  6. Click Continue.
  7. Follow the on-screen instructions to fill in the fields as described later on this page.
  8. Click Save and Test.
Fill in the following fields:
  • Name (required): A unique name for the 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 include tickets and articles. If no value is provided, the default is tickets.
  • Batch size: The maximum number of items to structure per batch. The default is 2.

​
Learn more