Integration
Connect MailSlurp Email Plugin to Wachete
When something happens in MailSlurp Email Plugin, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want MailSlurp Email Plugin and Wachete 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 MailSlurp Email Plugin and Wachete
Triggers and actions 5 triggers · 12 actions
Trigger
New AttachmentTriggered when a new attachment is uploaded or received in your MailSlurp account.
Trigger
New ContactTriggered when a new contact is created in your MailSlurp address book.
Trigger
New InboxTriggers when a new inbox is created on your MailSlurp account.
Action
Delete InboxPermanently deletes a MailSlurp inbox, its email address and all of its emails.
Action
Get email attachmentReturns the contents of one attachment on an email, base64 encoded, along with its file type and size.
Action
Get InboxFetches one MailSlurp inbox by id, including its email address, name and tags. An error occurs if the inbox is not found.
Action
List ContactsReturns the contacts in your MailSlurp address book, newest or oldest first, optionally narrowed by a search term or a date range.
Action
List InboxesReturns the email inboxes on your MailSlurp account, with their addresses, names and tags. Returns at most 100 inboxes.
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.