Gorgias
Send the right update through Gorgias at the right moment, with a person approving what reaches customers.
28 ways to read, 11 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Gorgias, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create customerApproval by rule
- Add internal noteApproval by rule
- List custom fieldsRead
Example flow
- Gorgias · List custom fieldsDone
- Gorgias · Create customerNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Gorgias.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Gorgias
- Gorgias's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Gorgias tickets, internal notes, customers, tags and field values; read macros, rules, views, users, teams, CSAT, integrations and events.
Gorgias API docs- Source actions
- 28
- Destination actions
- 11
- Data types
- 17
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account1
- Get accountSource
The helpdesk account with status and settings (business hours and others).
Custom fields1
- List custom fieldsSource
Ticket or customer custom field definitions.
Customer field values2
- List customer custom field valuesSource
Custom field values set on a customer.
- Set customer custom field valueDestinationProvider duplicate protectionApproval before production
Sets one custom field value on a customer, leaving other fields unchanged.
Customers4
- Create customerDestinationNot retried automaticallyApproval before production
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 customerDestinationProvider duplicate protectionApproval before production
Updates a customer's details, channels and custom data.
Events1
- List eventsSourceIncremental
Audit events on customers, macros, tags, users, views and other objects.
Integrations2
- Get integrationSource
One integration by ID.
- List integrationsSource
Connected integrations (email, Shopify, HTTP…) with type and status.
Macros2
- Get macroSource
One macro by ID.
- List macrosSource
Saved replies and actions agents apply to tickets (read only).
Messages4
- Add internal noteDestinationNot retried automaticallyApproval before production
Adds an internal note visible only to agents.
- Get messageSource
One ticket message or internal note.
- List messagesSource
Messages and internal notes, optionally for one ticket.
- Send message to customerDestinationNot retried automaticallyApproval before production
Sends an agent message on a ticket through email, SMS, chat or social.
Rules2
- Get ruleSource
One rule by ID.
- List rulesSource
Automation rules with triggering events and priority (read only).
Satisfaction surveys2
- Get satisfaction surveySource
One satisfaction survey by ID.
- List satisfaction surveysSource
CSAT surveys with score (1–5) and customer comment.
Tags4
- Create tagDestinationNot retried automaticallyApproval before production
Creates a ticket tag.
- Get tagSource
One tag by ID.
- List tagsSource
Ticket tags with usage.
- Update tagDestinationProvider duplicate protectionApproval before production
Renames a tag or changes its description or colour.
Teams2
- Get teamSource
One team by ID.
- List teamsSource
Agent teams with members.
Ticket field values2
- List ticket custom field valuesSource
Custom field values set on a ticket.
- Set ticket custom field valueDestinationProvider duplicate protectionApproval before production
Sets one custom field value on a ticket, leaving other fields unchanged.
Ticket tags2
- Add ticket tagsDestinationProvider duplicate protectionApproval before production
Adds tags to a ticket by name, keeping existing tags.
- List ticket tagsSource
Tags on one ticket.
Tickets4
- Create ticketDestinationNot retried automaticallyApproval before production
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 ticketDestinationProvider duplicate protectionApproval before production
Updates status, priority, assignee, tags, snooze or spam flag.
Users2
- Get userSource
One user by ID.
- List usersSource
Agents and admins with role and status.
Views2
- Get viewSource
One view by ID.
- List viewsSource
Ticket and customer views with filters and sharing.
Access and limits
- 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.
- Pagination
- Cursor pagination with meta.next_cursor and limit up to 100.
- Provider events
- HTTP integrations triggered by ticket and message events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
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.
- Macros, rules, views, users, teams, integrations and satisfaction surveys are read only; creating surveys (which can be sent to customers), editing rules or macros, and deleting or merging tags are intentionally excluded.
- Ticket tags are added (never removed or replaced) by the add-tags operation; updating a ticket's tags field still replaces them.
- Gorgias documents macro, rule, event and ticket-tag lists as bare arrays; Nexra accepts either an array or a data envelope.
Developer reference
- Create the Gorgias credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Gorgias, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/gorgias and the Connections API.