Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Gorgias

Helpdesk platform for ecommerce teams to manage tickets, customers, and support conversations.

CategoryCustomer Support
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Gorgias with Flows360

Helpdesk platform for ecommerce teams to manage tickets, customers, and support conversations.

Use the Gorgias connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and no declared triggers.

Available actions

  • Create Ticket
  • Get Ticket
  • Update Ticket
  • List Tickets
  • Create Message
  • Get Customer
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Gorgias
  • Package: @activepieces/piece-gorgias@0.1.0
  • Exact artifact digest: sha256:eec3ee81d626496ac4afd03ceb05ee65ef9e8872341907b59846dcbf72ee1612
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Ticket (create_gorgias_ticket), Create a new Gorgias ticket with an initial message. Classification: read.
  • Get Ticket (get_gorgias_ticket), Retrieve a Gorgias ticket by ID. Classification: read.
  • Update Ticket (update_gorgias_ticket), Update a Gorgias ticket. Classification: read.
  • List Tickets (list_gorgias_tickets), List Gorgias tickets with cursor-based pagination support. Classification: read.
  • Create Message (create_gorgias_ticket_message), Create a reply or message on an existing Gorgias ticket. Classification: read.
  • Get Customer (get_gorgias_customer), Retrieve a Gorgias customer by ID or find one by email. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Helpdesk Domain Required
  • Email Address Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Ticket Yes No Create a new Gorgias ticket with an initial message.
Get Ticket Yes No Retrieve a Gorgias ticket by ID.
Update Ticket Yes No Update a Gorgias ticket.
List Tickets Yes No List Gorgias tickets with cursor-based pagination support.
Create Message Yes No Create a reply or message on an existing Gorgias ticket.
Get Customer Yes No Retrieve a Gorgias customer by ID or find one by email.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Ticket · Read

Create a new Gorgias ticket with an initial message.

create_gorgias_ticket · Risk: low · Retry: safe

Inputs

  • fromAddress · string · Required, The sender address for the initial message, typically the customer email.
  • toAddress · string · Required, The recipient address for the initial message.
  • subject · string · Required
  • message · string · Required, Initial ticket message. HTML is accepted by the API.
  • channel · string · Required
  • via · string · Required, How the message reached Gorgias.
Get Ticket · Read

Retrieve a Gorgias ticket by ID.

get_gorgias_ticket · Risk: low · Retry: safe

Inputs

  • ticketId · number · Required
Update Ticket · Read

Update a Gorgias ticket.

update_gorgias_ticket · Risk: low · Retry: safe

Inputs

  • ticketId · number · Required
  • subject · string · Optional
  • status · string · Optional
  • channel · string · Optional
  • customerId · number · Optional, Optional customer ID to attach to the ticket.
  • customerEmail · string · Optional, Optional customer email to attach alongside the customer ID.
  • fromAgent · boolean · Optional, Whether the first message of the ticket was sent by your company.
  • isUnread · boolean · Optional
  • spam · boolean · Optional
  • externalId · string · Optional
List Tickets · Read

List Gorgias tickets with cursor-based pagination support.

list_gorgias_tickets · Risk: low · Retry: safe

Inputs

  • customerId · number · Optional, Optional customer ID to filter tickets for one customer.
  • cursor · string · Optional, Optional cursor returned by a previous list response.
  • limit · number · Optional, Maximum number of tickets to return in this page. Defaults to 25.
  • orderBy · string · Optional, Optional ordering, for example `created_datetime:desc`.
Create Message · Read

Create a reply or message on an existing Gorgias ticket.

create_gorgias_ticket_message · Risk: low · Retry: safe

Inputs

  • ticketId · number · Required
  • fromAgent · boolean · Required, True when the sender is an agent/user; false when the sender is a customer.
  • senderId · number · Required, User ID when From Agent is true, otherwise Customer ID.
  • receiverId · number · Required, Customer ID when From Agent is true, otherwise User ID.
  • fromAddress · string · Required, Email or channel address of the sender.
  • toAddress · string · Required, Email or channel address of the receiver.
  • message · string · Required, Message body. HTML is accepted by the API.
  • subject · string · Optional
  • channel · string · Required
  • via · string · Required
  • sentDatetime · string · Optional, Optional ISO-8601 timestamp for when the message was sent.
Get Customer · Read

Retrieve a Gorgias customer by ID or find one by email.

get_gorgias_customer · Risk: low · Retry: safe

Inputs

  • customerId · number · Optional, Use this when you already know the customer ID.
  • email · string · Optional, If Customer ID is not provided, search customers by email using Gorgias server-side filtering.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Gorgias connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Helpdesk Domain (domain), required.
  • Email Address (email), required.
  • API Key (api_key), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-gorgias@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Gorgias connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-gorgias@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com