Connect Beamer to Wachete

Both apps 17Beamer 8Wachete 9

• Trigger
  New Idea Comment

  Triggers when a new comment is sent for an idea.

• Trigger
  New Idea Vote

  Triggers when a new vote is sent for an idea.

• Action
  Create Idea

  Creates a new Feedback idea.

• Action
  Create Idea Comment

  Creates a new idea comment.

• Action
  Create Idea Vote

  Creates a new idea vote.

• Action
  Create Post

  Creates a new post.

• Action
  Get Post

  Fetches a post by ID, with its per-language title and content, category, publication state, and engagement counts. An error occurs if the post is not found. Reading a post through this action does not count as a view in your Beamer analytics.

• Action
  List Posts

  Returns all posts from your Beamer feed, each with its per-language title and content, category, publication state, and engagement counts. Reading posts through this action does not count as a view in your Beamer analytics.

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