Elastic Email
Elastic Email provides transactional email delivery, email marketing, contact and campaign management, reporting, verification, and account administration APIs.
Integration
- Vendor
- Elastic Email
- Category
- other
- Auth
- API_KEY
- Tools
- 50
- Composio slug
elastic_email
Tools
- Add Contact List Members
Add selected existing contacts to a named Elastic Email contact list.
- Add Contacts
Add up to 1000 Elastic Email contacts and optionally assign them to existing lists.
- Add Suppressions
Add up to 1000 email addresses to Elastic Email's bounce, complaint, or unsubscribe suppression records.
- Adjust Subaccount Credits
Add or remove email credits from a managed Elastic Email subaccount. Requires an Elastic Email PRO plan. The signed adjustment is not idempotent; a retry can apply the adjustment twice.
- Check Domain Restriction
Check whether Elastic Email restricts a domain or identifies it as a free-provider domain.
- Create Campaign
Create a campaign. An active or scheduled campaign may initiate email delivery, and sent messages cannot be recalled.
- Create Contact List
Create a contact list, optionally with initial email members.
- Create Domain
Create a sending or tracking domain in the connected Elastic Email account.
- Create Inbound Route
Create a new inbound email route.
- Create Segment
Create a dynamic contact segment from a name and SQL-like rule.
- Create Subaccount
Create a managed subaccount with optional initial email settings. An activation email can be sent; when activation email delivery is disabled, the subaccount is activated immediately. Requires an Elastic Email PRO plan.
- Create Template
Create a new email template with its name, content, and scope.
- Create Webhook
Create a webhook subscription for selected email events.
- Delete Campaigndestructive
Delete one campaign by exact name. This does not cancel email already in progress.
- Delete Contactdestructive
Delete one contact by exact email address.
- Delete Contact Listdestructive
Delete one contact list by exact name. Contacts that belonged to the list are removed from it but are not deleted.
- Delete Contactsdestructive
Permanently delete 1-10 contacts by exact email address. This destructive action sends one targeted deletion per address and reports partial failures; it does not use rule-based bulk deletion.
- Delete Domaindestructive
Delete one configured domain from the connected Elastic Email account.
- Delete Email Verificationdestructive
Delete one saved email verification result by exact email address.
- Delete Filedestructive
Permanently delete one stored file by its exact name.
- Delete Inbound Routedestructive
Permanently delete one inbound email route by its public ID.
- Delete Segmentdestructive
Delete one Elastic Email dynamic contact segment by its exact name.
- Delete Suppressiondestructive
Remove one email address from Elastic Email suppression records. This can allow sending to resume, so use only with documented recipient consent.
- Delete Templatedestructive
Delete one Elastic Email template by its exact name.
- Delete Verification Filedestructive
Delete one uploaded verification file job by its VerificationID.
- Delete Webhookdestructive
Delete one webhook subscription by its public WebhookID.
- Download File
Download a stored Elastic Email file by its exact name.
- Download Verification File Results
Download the ZIP result archive for a completed verification file job.
- Get Account Statistics
Return aggregate Elastic Email delivery statistics for a time interval.
- Get Campaign
Return one Elastic Email campaign by its exact name.
- Get Contact
Return one Elastic Email contact by email address.
- Get Contact Export Status
Get the current status of an asynchronous contact export job.
- Get Contact List
Return one Elastic Email contact list by its exact name.
- Get Credential Metadata
Get one Elastic Email API-key or SMTP credential's audit metadata without returning its secret token.
- Get Domain
Return detailed DNS and certificate state for one Elastic Email domain.
- Get Email Job Status
Return delivery status and optional recipient-level details for an Elastic Email transaction.
- Get Email Preview
Return the rendered preview, attachment metadata, and delivery status for an Elastic Email message ID.
- Get Email Verification
Return the saved Elastic Email verification result for one email address.
- Get Event Export Status
Get the current status of an asynchronous global or channel event export. Use export_scope='global' when Start Event Export had no channel, and export_scope='channel' when it targeted a channel.
- Get File Info
Return metadata for a stored Elastic Email file without downloading it.
- Get Inbound Route
Return one Elastic Email inbound route by its public ID.
- Get Segment
Return one Elastic Email dynamic contact segment by its exact name.
- Get Statistics Breakdown
Return one Elastic Email campaign or channel delivery summary by exact name.
- Get Subaccount
Return one managed Elastic Email subaccount by its login email. Requires an Elastic Email PRO plan.
- Get Suppression
Return suppression details for one Elastic Email address.
- Get Template
Return one Elastic Email template by its exact name.
- Get Verification File Results
Return one page of detailed results and metadata for a verification file.
- Get Webhook
Return one Elastic Email webhook subscription by its public ID.
- Import Contacts
Start an asynchronous contact import using exactly one source: an uploaded CSV file or a provider-accessible CSV URL.
- Import Suppressions
Upload CSV content containing bounced, complained, or unsubscribed email addresses for asynchronous suppression import.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Elastic Email.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Elastic Email tools in chat.
What teammates see: by default, memories from Elastic Email are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.