> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Gorgias Webhook Setup Guide

> Configure Gorgias to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/gorgias#getting-started) on the Gorgias connector page.

<section data-guide-section data-guide-scopes="">
  <h2>How webhooks are set up</h2>

  <p>StackOne creates and manages the webhook subscription automatically when the account is connected. For each event you enable, StackOne creates a Gorgias <strong>HTTP integration</strong> named `StackOne - <event>` that posts to your StackOne callback URL, and deletes it when the event is disabled or the account is disconnected. There is nothing to configure in Gorgias.</p>

  <ul>
    <li>Do not edit or delete the `StackOne - <event>` HTTP integrations in <strong>Settings > App Store > HTTP Integration</strong> — changing their URL, triggers, or request body stops event delivery.</li>
  </ul>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The following Gorgias events can be enabled. Only events selected in StackOne are subscribed — Gorgias does not deliver events that have no HTTP integration.</p>

  <Steps>
    <Step title="Ticket events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to the lifecycle, status, and assignment of tickets.</p>

        <ul>
          <li><strong>Ticket Created</strong> (`ticket-created`) — Fired when a new ticket is created in Gorgias</li>
          <li><strong>Ticket Updated</strong> (`ticket-updated`) — Fired when a ticket is updated (status, tags, custom fields, assignee, priority, or other attributes)</li>
          <li><strong>Ticket Status Updated</strong> (`ticket-status-updated`) — Fired when the status of a ticket changes (for example open to closed)</li>
          <li><strong>Ticket Assignment Updated</strong> (`ticket-assignment-updated`) — Fired when the assignee user or assignee team of a ticket changes</li>
          <li><strong>Ticket Self Unsnoozed</strong> (`ticket-self-unsnoozed`) — Fired when a snoozed ticket reopens automatically because its snooze period expired</li>
          <li><strong>Ticket Handed Over</strong> (`ticket-handed-over`) — Fired when a ticket is handed over from automation (such as the Gorgias AI Agent) to a human agent</li>
        </ul>
      </div>
    </Step>

    <Step title="Message events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to messages on tickets.</p>

        <ul>
          <li><strong>Ticket Message Created</strong> (`ticket-message-created`) — Fired when a message (customer reply, agent reply, or internal note) is added to a ticket</li>
          <li><strong>Ticket Message Failed</strong> (`ticket-message-failed`) — Fired when an outbound message on a ticket fails to send</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>Gorgias sends one JSON request per event with its full ticket/message payload. Every event includes a `ticket` object (IDs, status, channel, customer, assignee, tags, custom fields, and timestamps). Message events and most ticket events also include the related `message` object. Ticket Status Updated and Ticket Assignment Updated send a smaller `ticket` object with assignee and customer IDs instead of nested objects.</p>

  <ul>
    <li>Each request times out after 5 seconds. Gorgias retries up to 3 times (10s, 20s, 40s backoff) only when the endpoint cannot be reached — error responses are not retried.</li>
    <li>Gorgias automatically disables an HTTP integration after 500 consecutive failed requests.</li>
  </ul>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.