Integration
Connect DOOMSCROLLR to Intelliprint
When something happens in DOOMSCROLLR, your agent does the next thing in Intelliprint. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DOOMSCROLLR and Intelliprint 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 DOOMSCROLLR and Intelliprint
Triggers and actions 2 triggers ยท 31 actions
Trigger
New Audience MemberTriggers when a new audience member is added.
Trigger
New Content PostTriggers when a new content post is created.
Action
Add Audience MemberAdds a new audience member to your account.
Action
Add productCreate a new product. POST /products
Action
Create Image PostCreates a new image post.
Action
Create PostCreates a new post.
Action
Delete audience memberRemove a subscriber by id. DELETE /audience/{id}
Action
Delete postDelete a post by id. DELETE /posts/{id}
Action
Delete productDelete a product by id. DELETE /products/{id}
Action
Get audience memberRetrieve a single subscriber by id. GET /audience/{id}
Action
Get postRetrieve a single post by id. GET /posts/{id}
Action
Get productRetrieve a single product by id. GET /products/{id}
Action
List audience membersList subscribers/audience members. GET /audience
Action
List PostsLists all posts in your account.
Action
List productsList all products in the account. GET /products
Action
Update audience memberUpdate an existing subscriber. PATCH /audience/{id}
Action
Update postUpdate an existing post. PATCH /posts/{id}
Action
Update productUpdate an existing product. PATCH /products/{id}
Action
Add backgroundCreate a background/letterhead used for print jobs. POST /backgrounds
Action
Add mailing listCreate a mailing list. POST /mailing_lists
Action
Add recipientCreate a recipient in a mailing list. POST /mailing_lists/{mailing_list}/recipients
Action
Delete mailing listDelete a mailing list. DELETE /mailing_lists/{id}
Action
Delete print jobDelete or cancel a print job. DELETE /prints/{id}
Action
Delete recipientDelete a mailing list recipient. DELETE /mailing_lists/{mailing_list}/recipients/{id}
Action
Get mailing listRetrieve a mailing list by id. GET /mailing_lists/{id}
Action
Get print jobRetrieve a single print job by id. GET /prints/{id}
Action
Get recipientRetrieve a mailing list recipient by id. GET /mailing_lists/{mailing_list}/recipients/{id}
Action
List mailing listsList all mailing lists. GET /mailing_lists
Action
List recipientsList all recipients in a mailing list. GET /mailing_lists/{mailing_list}/recipients
Action
Send LetterWe'll print and mail out any content you provide us as a letter.
Action
Update mailing listUpdate a mailing list. POST /mailing_lists/{id}
Action
Update print jobUpdate an existing print job. POST /prints/{id}
Action
Update recipientUpdate a mailing list recipient. POST /mailing_lists/{mailing_list}/recipients/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.