Connect Reply and Wachete

Both apps 32Reply 23Wachete 9

• Trigger
  Inbox Category Set for Reply

  Triggers when an email reply in Reply is given an inbox category, automatically or by a user.

• Trigger
  New Email Opened

  Triggers when a contact opens a tracked email sent from Reply.

• Trigger
  New Emails Sent

  Triggers when Reply sends an email from a sequence step.

• Trigger
  New Link Clicked

  Triggers when a recipient clicks a tracked link in an email sent from Reply.

• Trigger
  New Person Bounce

  Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server.

• Trigger
  New Person Opt Out

  Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).

• Trigger
  Prospect Finished

  Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.

• Action
  Add contact list

  Creates a new contact list in Reply, optionally shared with your team.

• Action
  Add note to contact

  Adds a note to a contact's timeline in Reply.

• Action
  Add sequence

  Creates a new sequence in Reply with its steps, schedule, sending accounts and settings.

• Action
  Create\Update Person

  Creates a Reply contact, or updates the existing contact with the same email address.

• Action
  Delete contact

  Deletes a contact from your Reply account.

• Action
  Find contacts by criteria

  Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.

• Action
  Get contact

  Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.

• Action
  Get sequence

  Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.

• Action
  List contact lists

  Returns the contact lists you own plus those shared with your team, optionally filtered by name.

• Action
  List contacts

  Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.

• Action
  List inbox categories

  Returns the inbox categories you can file conversations under.

• Action
  List Sequence Contacts

  Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.

• Action
  List sequences

  Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.

• Action
  Mark as Finished

  Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.

• Action
  Remove Person From Campaign

  Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.

• Action
  Send Test Webhook Event

  Sends a test event from an existing Reply webhook subscription to its configured URL.

• 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.

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