Knowi connects to Gorgias via the REST API using basic authentication. With your Gorgias login email and password, you can pull ticket data, configure automatic cursor-based pagination, and transform the response into clean flat rows using Cloud9QL, with no manual exports needed.
Quick Summary (TL;DR)
- Knowi connects to Gorgias via the REST API using basic authentication: your Gorgias login email and password.
- The base URL is your domain-specific Gorgias API URL, which you find in your Gorgias account.
- The tickets endpoint pulls support ticket data; you can also pull customers, events, and other data types by changing the endpoint.
- Gorgias uses cursor-based pagination: Knowi reads meta.next_cursor from each response and keeps fetching until all records are pulled.
- Two Cloud9QL transformations are required: selectData to pull the response into Knowi, and expand to unnest the tickets array into flat rows.
- Set a daily schedule so your Gorgias data refreshes automatically, overnight or on a schedule you define.
Table of Contents
How to Connect Gorgias to Knowi via REST API
Gorgias connects to Knowi through the REST API datasource type using basic authentication. You need your Gorgias API base URL and your Gorgias login credentials.
- Go to Queries in Knowi and select New Data Source.
- Select REST API as the connection type.
- Give the datasource an internal name so you can identify it in Knowi.
- Paste in the base URL of your Gorgias API. This is your domain-specific URL from your Gorgias account (replace the example domain with your own).
- Keep the Authentication Type as Basic.
- Enter your Gorgias login email as the user ID and your Gorgias password.
- Click Test Connection. When the test is successful, click Save.
How to Query Gorgias Data in Knowi
Once the datasource is saved, you build your query in the REST API Query Builder. The tickets endpoint is shown below. Other Gorgias endpoints such as customers and events follow the same pattern.
| Setting | Value | Notes |
|---|---|---|
| Endpoint | tickets | Also available: customers, events, and other endpoints per Gorgias API documentation. |
| URL Parameters | limit=100 | Sets 100 tickets per page. Knowi auto-paginates through all pages. |
| Headers | None required | No additional headers needed for basic authentication. |
| Pagination: Response field name | meta.next_cursor | Gorgias uses cursor-based pagination. Knowi reads this field from each response. |
| Pagination: URL parameter name | cursor | Knowi passes the cursor value into each subsequent request until all records are fetched. |
Cloud9QL Transformations for Gorgias
Two Cloud9QL transformations are needed to get Gorgias data into a clean, usable format in Knowi.
- selectData: Selects the data field from the API response to pull into Knowi.
- expand: Unnests the tickets array from the response into clean flat rows, so each ticket becomes its own row in your dataset.
No additional configuration is needed beyond these two transformations.
Data Strategy and Schedule
- Set your Data Strategy to run daily.
- Configure it to run overnight so fresh data is available when you start your day.
- Click Create and Run to save and execute your query.
Watch a Video Walkthrough
Frequently Asked Questions
What authentication does the Gorgias integration use?
Basic authentication. Your Gorgias login email is the user ID and your Gorgias password is the password. No separate API token is required.
How does pagination work for Gorgias in Knowi?
Gorgias uses cursor-based pagination. In the Query Builder, set the response field name to meta.next_cursor and the URL parameter name to cursor. Knowi reads the cursor from each page response and keeps fetching until all records are pulled.
What Gorgias endpoints can I pull into Knowi?
The integration video demonstrates the tickets endpoint. You can also pull customers, events, and other data types by changing the endpoint in the Query Builder. Reference the Gorgias API documentation for the full list of available endpoints.
Why do I need Cloud9QL transformations for Gorgias?
The Gorgias API returns a nested JSON response with tickets in an array. The two Cloud9QL transformations (selectData and expand) are needed to pull the data into Knowi and flatten the tickets array into individual rows, one per ticket.
How often does Knowi refresh Gorgias data?
You can set any data strategy. The integration video configures a daily refresh running overnight.
Is Gorgias a native connector in Knowi?
Gorgias connects through Knowi’s REST API datasource type, which supports any REST API using basic, OAuth, API key, or other authentication methods. The setup process is the same for any REST API source.
Ready to connect your Gorgias support data to Knowi? Schedule a demo to see it in action, or set up your REST API datasource directly in your Knowi account.