Integration
Connect thanks.io to Federal Register
When something happens in thanks.io, 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 thanks.io 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 thanks.io and Federal Register
Triggers and actions 4 triggers · 10 actions
Trigger
Item DeliveredTriggers when a postcard, letter, notecard, or giftcard is delivered to a recipient.
Trigger
New OrderFires once for each new order placed in your thanks.io account.
Trigger
QR Code ScanTriggers when a QR Code on a postcard, letter, or notecard is scanned. This will also trigger when a giftcard is redeemed.
Action
Add RecipientAdds a recipient to your account and to an optional list. Only US or Canadian addresses are accepted. If no/invalid address is specified and a valid email address is, we'll attempt to look up a valid street address using the email address for a fee.
Action
Delete RecipientDeletes a Recipient from Mailing List.
Action
Lookup Address by EmailReturns the mailing address on file for a recipient in a thanks.io mailing list, looked up by their email address. Returns an empty list of matches when no recipient in that list has the email.
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.
Each app on its own
Reviews