Integration
Connect Pneumatic to Federal Register
When something happens in Pneumatic, 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 Pneumatic 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 Pneumatic and Federal Register
Triggers and actions 5 triggers ยท 13 actions
Trigger
Task CompletedTriggers when some task is completed.
- Task Returned
Triggers when a process is returned to this task.
- Workflow Completed
Triggers when a workflow is completed.
- Workflow Started
Triggers when a new workflow is started.
- Get Task
Get a single task by id. GET https://api.pneumatic.app/tasks/{task_id}.
- Get Template
Get a specific workflow template by id. GET https://api.pneumatic.app/templates/{template_id}.
- List Templates
List all workflow templates in the account. GET https://api.pneumatic.app/templates, supports ordering/limit/offset query params.
- List Users
List users in the account. GET https://api.pneumatic.app/users.
- Run Workflow
Run a New Workflow
- Update Task
Complete a task. POST https://api.pneumatic.app/tasks/{task_id}/complete (marks the task done and advances the workflow).
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
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