Integration
Connect Mailparser to Federal Register
When something happens in Mailparser, your agent does the next thing in Federal Register. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and Federal Register 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 Mailparser and Federal Register
Triggers and actions 3 triggers · 7 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
Trigger
New Email Parsed (One Request Per Row)Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
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.
Action
Find documentsSearch 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 documentsSearch public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}
Action
Get agencyFetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}
Action
Get documentFetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}
Action
Get issueFetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}
Action
Get public inspection documentFetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}
Action
List agenciesFetch all agency details known to the Federal Register. Endpoint: GET /agencies
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.