Connect Federal Register to Uplup

Both apps 26Federal Register 8Uplup 18

• 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
  New Response

  Triggers when someone submits a response to a quiz or form in Uplup. Includes all answers, contact info, and quiz-specific data like score and result.

• Action
  Add field

  Add a new field to a form at an optional position. POST /api/v1/forms/{form_id}/fields.

• Action
  Add form

  Create a new form or quiz with optional fields, styling, and quiz settings. POST /api/v1/forms.

• Action
  Add wheel

  Create a new spinning wheel with customizable entries, settings, and appearance. POST /api/v1/wheels.

• Action
  Add wheel entries

  Append one or more entries to a wheel without replacing the existing list. POST /api/v1/wheels/{wheel_id}/entries.

• Action
  Delete field

  Remove a field from the form. DELETE /api/v1/forms/{form_id}/fields/{field_id}.

• Action
  Delete form

  Permanently delete a form and all associated data. DELETE /api/v1/forms/{form_id}.

• Action
  Delete wheel

  Permanently delete a wheel and all its associated data including spin history. DELETE /api/v1/wheels/{wheel_id}.

• Action
  Get form

  Retrieve a single form with all its fields, pages, styling, and settings. GET /api/v1/forms/{form_id}.

• Action
  Get wheel

  Retrieve detailed information about a specific wheel including all entries and settings. GET /api/v1/wheels/{wheel_id}.

• Action
  List fields

  Get all fields for a form, ordered by position. GET /api/v1/forms/{form_id}/fields.

• Action
  List forms

  Return a paginated list of all forms and quizzes in the account. GET /api/v1/forms.

• Action
  List submissions

  Get paginated submissions for a form with optional filtering (limit, since). GET /api/v1/forms/{form_id}/submissions.

• Action
  List wheels

  Retrieve a paginated list of all wheels belonging to the account. GET /api/v1/wheels.

• Action
  Spin wheel

  Programmatically spin a wheel and get a randomly selected winner; the spin is recorded to the wheel's results history. POST /api/v1/wheels/{wheel_id}/spin.

• Action
  Update field

  Update field properties; only provided fields are modified. PATCH /api/v1/forms/{form_id}/fields/{field_id}.

• Action
  Update form

  Update form properties; only provided fields are modified. PATCH /api/v1/forms/{form_id}.

• Action
  Update wheel

  Update an existing wheel's title, entries, settings, and appearance. PUT /api/v1/wheels/{wheel_id}.

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