Gorgias Strawberry

Macros checked against tickets, in one pass

Your Gorgias, worked while you do something else: 10 reads to go through it, 13 writes to change it, and a card in front of every one of those changes.

Open the macro. Check it against something else. Write the change. Move to the next one. That is the Gorgias afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a macro until you approve it.

What it can do is exactly what Gorgias exposes to an account you authorise and nothing beyond it: 23 operations, 10 reads and 13 writes. In practice that means it can update a ticket, update ticket field values and update a macro, and work across the macros, tickets and customers.

The Gorgias API stops at Gorgias. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Does it read the macros or ask you for them?

10 of the 23 operations are reads.

Your account, not a guess at it: a companion can retrieve an a customer, list tickets and list ticket tags, and the full list below is the whole list, with nothing inferred from Gorgias's documentation.

The macros are what most of this inventory is about, alongside the tickets. A companion can hold all 23 of these operations and forty open tabs in the same pass, which is how an afternoon of Gorgias admin becomes a queue you review.

  • Retrieve a Customer
  • List Tickets
  • List Ticket Tags
  • List Ticket Messages
  • List Ticket Field Values
  • List Messages
  • List Macros
  • Get Ticket
  • Get Ticket Message
  • Get Macro

Which macros wait for your approval?

All 13 write operations wait for you.

A companion can update a ticket, update ticket field values and update a macro, and each one is staged on an approval card first: you see the macro, the field and the new value before it lands in Gorgias.

Nothing in Gorgias is sent, changed or deleted on your behalf without that click, and a rejected card leaves the macro exactly as it was. The gate is the same one on every surface, described at security.

  • Update Ticket
  • Update Ticket Field Values
  • Update Macro
  • Update Customer
  • Set Ticket Tags
  • Send Public Reply
  • Send Internal Note
  • Delete Macro
  • Create Ticket
  • Create Ticket Message
  • Create Macro
  • Create Customer
  • Add Ticket Tags

Does the macro sweep have to be asked for every time?

Yes.

Saved as a routine, the Gorgias macros pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The operations playbook catalogues the other recurring shapes of store admin, the Gorgias macros sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Gorgias account and a companion works 23 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide