Connect Woodpecker.co to Wachete

Both apps 34Woodpecker.co 25Wachete 9

• Trigger
  Campaign Completed

  Triggers when a Woodpecker campaign status changes to COMPLETED.

• Trigger
  Email Opened

  Triggers when a prospect opens your email.

• Trigger
  Email Sent

  Triggers when Woodpecker sends an email to prospect from campaign.

• Trigger
  Follow-Up After Autoreply

  Triggers when you set a date for resuming follow-ups after you got an autoreply from a prospect.

• Trigger
  Link Clicked

  Triggers when a prospect clicks on a link in your email.

• Trigger
  Manual Task Created

  Triggers when a manual task of any type is created.

• Trigger
  Manual Task Done

  Triggers when a manual task is marked as done.

• Trigger
  Manual Task Ignored

  Triggers when a manual task is marked as ignored.

• Trigger
  Prospect Autoreplied

  Triggers when you get an autoresponder from a prospect, or when you manually mark a prospect as AUTOREPLIED.

• Trigger
  Prospect Blacklisted

  Triggers when a prospect status is changed to BLACKLISTED manually or when prospect unsubscribes from Woodpecker.

• Trigger
  Prospect Bounced

  Triggers when a prospect’s email address bounces your message and the prospect status gets changed to BOUNCED in Woodpecker.

• Trigger
  Prospect Interested

  Triggers when a prospect is marked as INTERESTED.

• Trigger
  Prospect Invalid

  Triggers when a prospect’s email address doesn't exist on an external server. This check happens when Woodpecker tries to send an email to this prospect. Status is changed to INVALID in Woodpecker.

• Trigger
  Prospect Maybe Later

  Triggers when a prospect's interest level is marked as MAYBE LATER.

• Trigger
  Prospect Nonresponsive

  Triggers when a prospect's status is changed to NONRESPONSIVE

• Trigger
  Prospect Not Interested

  Triggers when a prospect is marked as NOT INTERESTED.

• Trigger
  Prospect Opt Out

  Triggers when prospect unsubscribes from your emails or is marked as OPT-OUT manually.

• Trigger
  Prospect Replied

  Triggers when a prospect replies to your email or is manually marked as REPLIED in Woodpecker.

• Trigger
  Prospect Saved

  Triggers when a Woodpecker prospect is created or updated.

• Trigger
  Secondary Reply

  Triggers when a secondary reply is found by Woodpecker.

• Action
  Blacklist Domain

  Add a domain to a blacklist. It will automatically block ongoing and future sending to all prospects within a given domain.

• Action
  Create/Update Prospect

  Adds a new prospect or Updates existing prospect in the list of Prospects.

• Action
  Create/Update Prospect in Campaign

  Adds a new prospect or updates existing prospect's data in a campaign of choice.

• Action
  Find Prospect Email

  Finds prospect by email address.

• Action
  Stop Follow-Ups

  Stop follow-ups planned for this prospect.

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