Integration Types

EnjoyHQ has, broadly, two types of integrations: for fetching data (written feedback and customer information) from an external service and sharing data from EnjoyHQ to a connected service (e.g. sharing a Story link to Slack or a Project status to Jira).

How to read the table?

Fetch means that the data will be synchronized from given service and stored in EnjoyHQ.

Push means that a link or data from EnjoyHQ can be pushed to an another service.

Upload means fetching a single files from a given destination and converting it into an EnjoyHQ document containing written feedback and/or customer profile & attributes.

Authentication type: outlines what type of authentication credentials we need in order to fetch the data from a 3rd party service

Integration

Type

Data imported or pushed

Free?

Authentication type

Zendesk

Fetch

Tickets, customer information

No

Email + dedicated API token

Intercom

Fetch

Conversations, customer attributes and segments

No

OAuth 2

Salesforce

Fetch

Any object configured in the Salesforce integration

No

EnjoyHQ Api token

Typeform

Fetch

Any survey can be configured to send response data as feedback or customer attributes

No

OAuth 2

Drift

Fetch

Tickets, customer information

No

OAuth 2

Jira Service Desk

Fetch

Tickets, customer information

No

Jira API credentials (dedicated)

Delighted

Fetch

NPS survey answers, ratings, customer information

No

API Token

Satismeter

Fetch

NPS survey answers, ratings, customer information

No

OAuth 2

AskNicely

Fetch

NPS survey answers, ratings, customer information

No

API keys

Promoter

Fetch

NPS survey answers, ratings, customer information

No

API keys

Wootric

Fetch

NPS survey answers, ratings, customer information

No

API keys

Twitter

Fetch

Public Tweets matching a handle

No

OAuth

Play Store

Fetch

Written reviews and their ratings

No

None

App Store

Fetch

Written reviews and their ratings

No

None

TrustPilot

Fetch

Written reviews and their ratings

No

None

Jira

Pull

Projects can be linked to Jira issues and have their status synchronized

Yes

Jira API credentials (dedicated)

Slack

Both

Feedback can be sent through Slack to EnjoyHQ and links to EnjoyHQ documents, stories, projects etc can be shared to Slack

Yes

OAuth 2

Trello

Pull

Links to EnjoyHQ documents, stories, projects etc can be shared to

Yes

OAuth 2

Google Drive

Upload

Documents, spreadsheets and PDF files

Yes

OAuth 2

Dropbox

Upload

Documents, spreadsheets and PDF files

Yes

OAuth 2

Box

Upload

Documents, spreadsheets and PDF files

Yes

OAuth 2

One Drive

Upload

Documents, spreadsheets and PDF files

Yes

OAuth 2

Email

Upload

Email data is imported as feedback documents

Yes

N/A

Zapier

Fetch

Any data sent via Zapier trigger can be imported as feedback

Yes

N/A

API

Fetch

Both feedback and customer data can be pushed via the API

No

API keys


How Did We Do?


Powered by HelpDocs (opens in a new tab)