Integration
Connect MailSlurp Email Plugin to Calendly
When something happens in MailSlurp Email Plugin, your agent does the next thing in Calendly. 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 Calendly 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 Calendly
Triggers and actions 5 triggers · 23 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.
Trigger
Canceled scheduled event (polling)Triggers when a scheduled event is canceled.
- New scheduled event (polling)
Triggers when a new scheduled event is created.
- Cancel scheduled event
Cancels a scheduled event with a specified reason for the cancellation.
- Create single-use scheduling link
Creates a single-use booking link that allows one person to schedule an event.
- Get current user
Returns the authenticated user's profile including name, email, timezone, and scheduling URL.
- Get event type
Returns details for the specified event type.
- Get invitee
Returns details about a specific invitee for a scheduled event.
- Get invitee next scheduled event
Gets the next scheduled event for the invitee specified by their email.
- Get scheduled event
Returns details about a specific scheduled event.
- Get user availability schedule
Returns details for the specified user availability schedule.
- List event invitees
Returns the list of invitees for a scheduled event, optionally filtered by status.
- List event type availability schedules
Returns the event type's availability schedules.
- List event types
Returns your calendar's event type templates, optionally filtered by scope and active status.
- List organization memberships
Returns all members of the connected Calendly organization (paginated). One record per membership: user_email, user_uri, user_name, role.
- List scheduled events
Returns scheduled events, filterable by scope, status, date range, and invitee email.
- List user availability schedules
Returns the user's availability schedules.
- List webhook subscriptions
Returns all webhook subscriptions for your organization.
- Mark invitee as no-show
Records that an invitee did not attend their scheduled event.
- Undo invitee no-show
Removes a no-show marking from an invitee.
- Update event type availability schedule
Replaces a single host's availability schedule on a Calendly event type with explicit date rules (full overwrite). Built for CalendarConnect: push real Mindbody bookable slots into Calendly so only MBO-bookable times are offered. CRITICAL: the host is targeted by the NESTED availability_rule.user — a top-level user alone is silently ignored and Calendly replaces the OAuth token owner's schedule instead. Always verify stored_user equals the requested host before trusting the result. For round-robin events, call once per host.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.