Connect Wachete to Gorgias

Both apps 24Wachete 9Gorgias 15

• Trigger
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

• Trigger
  New ticket

  Fires when a new ticket is created in Gorgias. Poll GET https://{domain}.gorgias.com/api/tickets ordered by created_datetime, or vendor webhook event ticket-created.

• Trigger
  New ticket message

  Fires when a new message is added to a ticket. Poll GET https://{domain}.gorgias.com/api/tickets/{id}/messages, or vendor webhook event message-created.

• Action
  Add customer

  Create a new customer profile. POST https://{domain}.gorgias.com/api/customers

• Action
  Add tag to ticket

  Apply a tag to a ticket. POST https://{domain}.gorgias.com/api/tickets/{id}/tags or PUT ticket with tags array

• Action
  Create Ticket

  Creates a ticket

• Action
  Create Ticket Message

  Creates a Ticket Message in an existing ticket

• Action
  Delete ticket

  Delete a ticket by id. DELETE https://{domain}.gorgias.com/api/tickets/{id}

• Action
  Find customers by email

  Search/list customers, filterable by email and other criteria. GET https://{domain}.gorgias.com/api/customers

• Action
  Get customer

  Retrieve a single customer by id. GET https://{domain}.gorgias.com/api/customers/{id}

• Action
  Get ticket

  Retrieve a single ticket by id. GET https://{domain}.gorgias.com/api/tickets/{id}

• Action
  Get Ticket Message

  Look up one message by its id and return its details, including its body, subject, channel, sender, receiver and whether the customer can see it.

• Action
  List ticket messages

  List messages belonging to a ticket. GET https://{domain}.gorgias.com/api/tickets/{id}/messages

• Action
  List tickets

  List tickets with optional filters (status, customer, tags). GET https://{domain}.gorgias.com/api/tickets

• Action
  Update customer

  Update fields on an existing customer record. PUT https://{domain}.gorgias.com/api/customers/{id}

• Action
  Update ticket

  Update fields on an existing ticket (status, priority, assignee, tags). PUT https://{domain}.gorgias.com/api/tickets/{id}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.