Integration
Connect Archive.org to Emailr
When something happens in Archive.org, your agent does the next thing in Emailr. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Archive.org and Emailr 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 Archive.org and Emailr
Triggers and actions 1 trigger ยท 14 actions
Trigger
New itemFires when a new item matching a saved search query is added to the Internet Archive.
- Find items
Search the Internet Archive catalog for items matching a query using the advanced search API.
- Get item
Fetch an Internet Archive item's full metadata record and file listing by identifier.
Action
Add contactCreate a contact. POST /v1/contacts
- Add segment
Create a contact segment. POST /v1/segments
- Add template
Create an email template. POST /v1/templates
- Delete contact
Delete a contact by ID. DELETE /v1/contacts/{id}
- Delete segment
Delete a segment by ID. DELETE /v1/segments/{id}
- Delete template
Delete a template by ID. DELETE /v1/templates/{id}
- Get contact
Fetch a contact by ID. GET /v1/contacts/{id}
- Get template
Fetch a template by ID. GET /v1/templates/{id}
- List segments
List contact segments. GET /v1/segments
- Update contact
Update a contact by ID. PUT /v1/contacts/{id}
- Update segment
Update a segment by ID. PUT /v1/segments/{id}
- Update template
Update a template by ID. PUT /v1/templates/{id}
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