
Gorgias
Read and write Gorgias tickets, messages, internal notes, customers and ticket field values, plus tags, users, teams, CSAT and integrations.
Connect ecommerce support tickets and customers with order, returns and CRM systems.
Source actions
12
Destination actions
7
Data types
10
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
custom fields
- List custom fieldsSource
Ticket or customer custom field definitions.
customers
- Create customerDestinationNot retried automatically
Creates a customer with channels and custom data.
- Get customerSource
A customer with channels and custom data.
- List customersSource
Customers, optionally by email or external ID.
- Update customerDestinationDuplicate protected
Updates a customer's details, channels and custom data.
integrations
- List integrationsSource
Connected integrations (email, Shopify, HTTP…) with type and status.
messages
- Add internal noteDestinationNot retried automatically
Adds an internal note visible only to agents.
- List messagesSource
Messages and internal notes, optionally for one ticket.
- Send message to customerDestinationNot retried automatically
Sends an agent message on a ticket through email, SMS, chat or social.
satisfaction surveys
- List satisfaction surveysSource
CSAT surveys with score (1–5) and customer comment.
tags
- List tagsSource
Ticket tags with usage.
teams
- List teamsSource
Agent teams with members.
ticket field values
- List ticket custom field valuesSource
Custom field values set on a ticket.
- Set ticket custom field valueDestinationDuplicate protected
Sets one custom field value on a ticket, leaving other fields unchanged.
tickets
- Create ticketDestinationNot retried automatically
Creates a ticket from a customer message (recorded, not emailed).
- Get ticketSource
A ticket with customer, assignee, tags and custom fields.
- List ticketsSource
Tickets, most recently updated first, optionally for a customer or view.
- Update ticketDestinationDuplicate protected
Updates status, priority, assignee, tags, snooze or spam flag.
users
- List usersSource
Agents and admins with role and status.
Authentication
User email and REST API key
Plans and access
All Gorgias plans include the REST API. Private API keys act with the permissions of the user who owns them.
Test environment
Gorgias trials and partner development accounts can be used for testing.
Rate limits
Leaky bucket of 40 requests per 20 seconds for API keys (80 for OAuth apps); HTTP 429 with Retry-After.
Provider events
HTTP integrations triggered by ticket and message events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Gorgias has no updated-since filter; ticket lists are ordered by updated_datetime descending.
- Ticket, customer and message deletion and customer merging are not implemented.
- Tickets created here record an inbound customer message (sent_datetime set) so nothing is emailed.
- Outbound messages without sent_datetime are delivered by Gorgias on the chosen channel.
- Gorgias documents no idempotency key: ticket, message and customer creates are not repeated automatically when uncertain.