Integration
Connect MailSlurp Email Plugin to SLF
When something happens in MailSlurp Email Plugin, your agent does the next thing in SLF. 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 SLF 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 SLF
Triggers and actions 3 triggers · 6 actions
Trigger
New AttachmentTriggered when a new attachment is uploaded or received in your MailSlurp account.
- New Contact
Triggered when a new contact is created in your MailSlurp address book.
- New Inbox
Triggers when a new inbox is created on your MailSlurp account.
- Delete Inbox
Permanently deletes a MailSlurp inbox, its email address and all of its emails.
- Get email attachment
Returns the contents of one attachment on an email, base64 encoded, along with its file type and size.
- Get Inbox
Fetches one MailSlurp inbox by id, including its email address, name and tags. An error occurs if the inbox is not found.
- List Contacts
Returns the contacts in your MailSlurp address book, newest or oldest first, optionally narrowed by a search term or a date range.
- List Inboxes
Returns the email inboxes on your MailSlurp account, with their addresses, names and tags. Returns at most 100 inboxes.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.