Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zendesk Support Upgrade - Ticket Metrics Events #5802

Closed
Howard3 opened this issue Sep 2, 2021 · 4 comments
Closed

Zendesk Support Upgrade - Ticket Metrics Events #5802

Howard3 opened this issue Sep 2, 2021 · 4 comments

Comments

@Howard3
Copy link

Howard3 commented Sep 2, 2021

Tell us about the new connector you’d like to have

  • This is an upgrade to the existing Zendesk Support Source
  • Do you need a specific version of the underlying data source e.g: you specifically need support for an older version of the API or DB? No

Describe the context around this new connector

  • Which team in your company wants this integration, what for? Business intelligence
  • How often do you want to run syncs? 24 hours
  • If this is an API source connector, which entities/endpoints do you need supported? Currently the Zendesk Support connector supports sla_policies, ticket_metrics, and tickets however, these are not able to be referenced to one another without the use of the source endpoint Ticket Metric Events, this endpoints data acts as the "glue" between a lot of these data sources.

Describe the alternative you are considering or using

What are you considering doing if you don’t have this integration through Airbyte?

Are you willing to submit a PR?

I can try!

@Howard3 Howard3 added area/connectors Connector related issues new-connector labels Sep 2, 2021
@sherifnada
Copy link
Contributor

@Howard3 let us know if you need a hand with creating a PR!

@milo157
Copy link

milo157 commented Oct 11, 2021

@Howard3 @sherifnada Any progress on this issue? Do we have a branch we can check progress on?

@jonoirwinrsa
Copy link
Contributor

@sherifnada @Howard3 PR that addresses this issue here: #8168

@misteryeo
Copy link
Contributor

Closing as this PR was merged: #8316

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants