Integration
Connect Federal Register to Amplitude
When something happens in Federal Register, your agent does the next thing in Amplitude. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Federal Register and Amplitude to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Federal Register and Amplitude
Triggers and actions 1 trigger ยท 19 actions
Trigger
New documentPolling 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.
- 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}
- Find public inspection documents
Search public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}
- Get agency
Fetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}
- Get document
Fetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}
- Get issue
Fetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}
- Get public inspection document
Fetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}
- List agencies
Fetch all agency details known to the Federal Register. Endpoint: GET /agencies
Action
Batch upload eventsSends a batch of events to Amplitude in one call. Use this when you have many events to record at once rather than one at a time.
- Export event data
Exports every event Amplitude recorded in a time window, as a zip archive of event data.
- Get cohort
Returns one behavioral cohort's details, including its name, size and when it was last recalculated.
- Get event segmentation
Counts how often an event happened over a date range, optionally split by a property or filtered to a segment of users.
- Get funnel analysis
Runs a funnel over a series of events and returns how many users reached each step and how many dropped off.
- Get retention analysis
Shows how many users came back and did something again after a starting event, over a date range.
- Get user properties
Looks a user up in Amplitude and returns what Amplitude knows about them, including their Amplitude ID.
- Group identify
Sets properties on a group in Amplitude, such as a company or team, so you can analyse behaviour by group.
- Identify user
Sets properties on a user in Amplitude without recording an event, so later events are attributed with the new details.
- List cohorts
Lists every behavioral cohort in the Amplitude project, with each cohort's name, size and owner.
- Send event
Records a single event in Amplitude for a user, with optional event and user properties.
- Upload cohort
Creates a cohort in Amplitude from a list of users you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews