Documentation Index

Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt

Use this file to discover all available pages before exploring further.

Gorgias

Prev Next

Gorgias is a customer support and helpdesk platform designed for e-commerce businesses. It integrates with various e-commerce platforms to provide a unified system for managing customer inquiries, support tickets, and communication across multiple channels, streamlining customer service operations.

Refer to our website for the list of metrics and attributes available in Dataddo.

Refer to Gorgias's official documentation to see all available endpoints from the Gorgias API.

Authorize Connection to Gorgias

In Gorgias

To authorize your Gorgias account, you will need your subdomain, email, and an API key (= API token).

  1. In your Gorgias account, in the top of the left-side navigation, click on the Tickets field to expand the menu and select Settings.
  2. Scroll all the way down to REST API.
  3. Continue by clicking on the Create API key and copy the value.

Your subdomain is the first part of your URL. E.g. If your URL is agencyname.gorgias.com, your subdomain is agencyname.

In Dataddo

  1. On the Authorizers page, click on Authorize New Service and select Gorgias.
  2. Fill in the following fields:
    1. Subdomain: Gorgias subdomain name (e.g. agencyname from agencyname.gorgias.com).
    2. Email: Email address you log in to Gorgias with.
    3. API Token: Gorgias API key.
  3. Rename your authorizer for easier identification and click on Save.

Data Coverage

Gorgias exposes the following datasets. Each dataset maps to a table you can extract. Example fields are a representative sample; each dataset returns more columns.

Dataset Description Example fields Date range
Customers All customers and their profile details including contact information, preferences, and account status. ID, Active, Bio, Country, Created datetime, Deactivated datetime (+9 more) No
Events System events triggered by users or automation, grouped by context UUID for tracing event sequences. ID, Context, Created datetime, Object ID, Object type, Type (+2 more) No
Macros Predefined action sequences agents apply to tickets to automate responses or workflows. ID, Created datetime, Intent, Name, Updated datetime, Usage No
Satisfaction surveys Customer satisfaction (CSAT) survey responses linked to tickets, including score and comment. ID, Body text, Created datetime, Customer ID, Score, Scored datetime (+4 more) No
First Response Time First response time statistics with trend line data for the selected date range. Data Axes X, Data Lines Data, Data Lines Name, End Datetime, Label, Legend Axes X (+2 more) Yes
Latest Satisfaction Surveys Most recent satisfaction survey responses per customer for the selected date range. Data Axes X Name, Data Axes X Type, Data Lines Customer Id, Data Lines Customer Name, Data Lines Type, End Datetime (+2 more) Yes
Resolution Time Resolution time statistics with trend line data for the selected date range. Data Axes X, Data Lines Data, Data Lines Name, End Datetime, Label, Legend Axes X (+2 more) Yes
Satisfaction Survey Statistics Aggregated satisfaction survey metrics for the selected date range, including score and response rate. Data Delta, Data More Is Better, Data Name, Data Type, Data Value, End Datetime (+1 more) Yes
Support Volume Support volume statistics showing ticket counts over time for the selected date range. Data Axes X, Data Lines Data, Data Lines Name, End Datetime, Label, Legend Axes X (+2 more) Yes
Total Tickets Closed Aggregated count of tickets closed during the selected date range with period-over-period delta. Data Delta, Data Name, Data Type, Data Value, End Datetime, Start Datetime Yes
Total Tickets Created Aggregated count of tickets created during the selected date range with period-over-period delta. Data Delta, Data Name, Data Type, Data Value, End Datetime, Start Datetime Yes
Total Tickets Replied Aggregated count of tickets replied to during the selected date range with period-over-period delta. Data Delta, Data Name, Data Type, Data Value, End Datetime, Start Datetime Yes
Teams Support agent teams used for auto-assignment of tickets, with member composition. ID, Created datetime, Description, Members, Name, URI No
Ticket messages Individual messages within support tickets, including sender and receiver details, delivery status, and timestamps. ID, Channel, Created datetime, Deleted datetime, External id, Failed datetime (+16 more) Yes
Tickets Support tickets with full lifecycle data including assignment, status, channel, timestamps, and customer and agent details. ID, Assignee team ID, Assignee team name, Assignee user email, Assignee user first name, Assignee used ID (+25 more) No
User audit logs Audit log entries recording actions performed by users on Gorgias objects. ID, Created datetime, Object ID, Object type, Type, URI (+1 more) No
Users Agent accounts with profile details, login status, and account lifecycle timestamps. ID, Active, Bio, Created datetime, Deactivated datetime, Email (+5 more) No

How Data Extraction Works

What each extraction pulls depends only on whether a dataset supports a date range (see the Date range column above):

  • Date range supported (Yes): the source reads a relative window (for example "last 7 days"), and that window slides forward with the current date. Every run re-reads the window, so a range of "1 day ago" always pulls the previous day (D-1). Each run replaces the window's data rather than adding older history. To load records from before the window, run a full data re-sync with a wider range. See Data Backfilling.
  • No date range (No): every run pulls all currently available data.

Set the relative date range when you create the source.

Metadata Columns

When you create a source, you can add these Dataddo metadata columns to the extracted data:

  • dataddo_hash - a fingerprint built from each record's key fields. It works as a natural key, so it is ideal for upserts (updating existing rows in your destination instead of creating duplicates).
  • dataddo_extraction_timestamp - the date and time the row was extracted. Use it to track how records change over time, for example to build slowly changing dimensions.

How to Create a Gorgias Source

Creating a data source takes you through six steps, shown in the progress bar at the top of the wizard. Each step is explained below.

1. Pick the connector

On the Sources page, click Create Source, then select the connector from the catalog. Use the search bar or the category tabs if you do not see it right away. You can rename the source at any time using the pencil icon next to its name.

2. Select the dataset

A dataset defines the shape of your data: which fields you get and how they relate. Select the dataset you want; you can still fine-tune the exact fields later.

  • Each dataset has a short description of what it contains. Use the search box to find a dataset, attribute, or metric by name.
  • The panel on the right previews the selected dataset's fields. For each field you can see its data type, whether it holds sensitive data (personal fields such as name or email are flagged), and which other datasets it links to, so you can see how the datasets relate.

3. Choose the account

This step selects what Dataddo reads from.

  • Authorizer: Select an account you have already authorized from the drop-down. If you have none yet, choose Add new account and follow the prompts. If no authorizer is selected, Dataddo asks you to authorize before you continue.
  • What to extract from: Select the exact entity you want to pull data from. Depending on the service this may be labelled an account, property, profile, workspace, or similar, sometimes with a sub-level to choose as well.
  • Multiple accounts: To pull the same data from every entity you can access, turn on Automatically collect data from all .... This is multi-account extraction. Leave it off to choose them by hand.

4. Refine the attributes and metrics

The dataset already sets the structure. Here you fine-tune it: tick or untick the specific attributes and metrics you want to keep, and use the search box to find a field quickly. Click Test on Sample Data at any point to preview the result before you continue.

5. Add metadata columns (optional)

Two optional columns help your destination handle the data.

  • Dataddo Hash (Include Row Hash): a fingerprint built from the columns you pick. It works as a natural key, so your destination can deduplicate rows and run upserts instead of creating duplicates. Turn it on, then select the columns that uniquely identify a row.
  • Dataddo Extraction Timestamp: the time each row was extracted. Use it to watermark the data, for example to build slowly changing dimensions or to track when a value last changed.

6. Set the schedule

Decide how often Dataddo runs the extraction.

  • Frequency: how often the pipeline runs, for example daily. Click Show advanced settings to also set the exact hour and minute (UTC).
  • Date range: the relative window each run extracts, for example "Yesterday". The window moves forward on every run.
  • Historical data: a new source starts from the current window. To load older data, run a full data re-sync after the source is created.
  • Allow Empty Data Extractions: when on, a run that returns no data records zero rows instead of failing. Turn it on if the source can legitimately have periods with no data.

Click Save. Your data source is ready.

Troubleshooting

Data Preview Unavailable

No data preview when you click on Test Data might be caused by an issue with your source configuration. The most common causes are:

  • Date range: Try a smaller date range. You can load the rest of your data afterward via manual data load.
  • Insufficient permissions: Please make sure your authorized account has at least admin-level permissions.

Related Articles

Now that you have successfully created a data source, see how you can connect your data to a dashboarding app or a data storage.

Sending Data to Dashboarding Apps

Sending Data to Data Storages

Other Resources