Integration
Connect Airbrake to Intelliprint
When something happens in Airbrake, 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 Airbrake 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 Airbrake and Intelliprint
Triggers and actions 1 trigger · 29 actions
Trigger
New errorTriggered when any new error is reported.
Action
Create noticeSubmit a new error notice to Airbrake — report an error from an automation.
Action
Delete error groupDelete/resolve an Airbrake error group by id.
Action
Get error groupFetch details for a single error group.
Action
Get projectFetch details for a single project by ID.
Action
List activitiesList the audit-log activities for an Airbrake project — deploys, mutes, resolves, etc.
Action
List deploysList recorded deploys for an Airbrake project.
Action
List error groupsList error groups (aggregated errors) for a project.
Action
List noticesList individual notices (occurrences) for an error group.
Action
List projectsList all projects accessible to the authenticated user key.
Action
List source mapsList the uploaded source maps for an Airbrake project.
Action
Mute error groupMute an error group so it no longer triggers notifications.
Action
Record deployRecord a new deployment for a project (environment, revision, version, etc.).
Action
Show deployRetrieve a single Airbrake deploy by id.
Action
Unmute error groupUnmute a previously muted error group to re-enable notifications.
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.
Each app on its own
Reviews