Connect Federal Register to Wachete

Both apps 17Federal Register 8Wachete 9

• Trigger
  New document

  Polling trigger that fires when a new Federal Register document is published, using GET /documents.{format} sorted by publication_date descending as the dedup source for regulatory monitoring.

• Action
  Find documents

  Search all Federal Register documents published since 1994 by term, agency, document type, publication/effective date, and docket number. Endpoint: GET /documents.{format}

• Action
  Find public inspection documents

  Search public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}

• Action
  Get agency

  Fetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}

• Action
  Get document

  Fetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}

• Action
  Get issue

  Fetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}

• Action
  Get public inspection document

  Fetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}

• Action
  List agencies

  Fetch all agency details known to the Federal Register. Endpoint: GET /agencies

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