Integration
Connect Federal Register to Autobound
When something happens in Federal Register, your agent does the next thing in Autobound. 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 Autobound 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 Autobound
Triggers and actions 1 trigger ยท 13 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
Find buyer intent contactsSearch 38,000+ B2B intent topics to find contacts showing purchase intent for given topics. POST https://signals.autobound.ai/v1/buyer-intent/contacts, X-API-KEY header.
- Find companies by signal
Search for companies showing a given signal activity (signal type, date range, or keyword content inside social posts). POST https://signals.autobound.ai/v1/companies/search, X-API-KEY header.
- Find contacts by signal
Search for contacts showing a given signal activity, filterable by seniority, department, and job title. POST https://signals.autobound.ai/v1/contacts/search, X-API-KEY header.
- Get company signals
Enrich a company by domain, name, or LinkedIn URL and return every signal on file (financials, hiring trends, SEC filings, social activity, news). POST https://signals.autobound.ai/v1/companies/enrich, X-API-KEY header.
- Get contact signals
Enrich a contact by email or LinkedIn URL and return person-level signals (job changes, LinkedIn posts/comments, milestones, speaking appearances). POST https://signals.autobound.ai/v1/contacts/enrich, X-API-KEY header.
- Verify email
Verify an email address (or up to 1000 in bulk) for deliverability. POST https://signals.autobound.ai/v1/emails/verify, X-API-KEY header.
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