Activate Sub-account
Reactivate a suspended sub-account, restoring its ability to send email.
MailChannels provides transactional email delivery, domain and DKIM management, sub-account administration, usage reporting, suppression lists, metrics, and webhooks.
Reactivate a suspended sub-account, restoring its ability to send email.
Check a sending domain's DKIM, SPF, sender-domain DNS, and Domain Lockdown configuration without changing it.
Create a MailChannels-managed DKIM key pair and return the public key and DNS record that must be published.
Create a sub-account under the connected parent account. This creates persistent tenant state but no API or SMTP credential.
Explicitly create a sensitive API credential for a sub-account. The returned secret may be shown only once; store it securely because tool or application logs can expose it. This provider-created credential is output for the sub-account and is never connection authentication for this action.
Explicitly create a sensitive SMTP credential for a sub-account. The returned password may be shown only once; store it securely because tool or application logs can expose it. This provider-created credential is output for SMTP use and is never connection authentication for this action.
Atomically add one or more recipients to the connected account's suppression list, optionally also applying them to all associated sub-accounts.
Permanently remove every webhook endpoint enrolled for the connected MailChannels account. This destructive action has no endpoint selector and must not be used when any existing webhook configuration should be retained.
Permanently delete one custom tracking domain by exact hostname and scope. This destructive action immediately breaks tracking and unsubscribe URLs in previously sent messages that use the domain.
Permanently and irreversibly delete one MailChannels sub-account by its exact handle. This destructive action cannot be undone.
Permanently revoke one sub-account API key by exact sub-account handle and key ID. This explicit destructive credential deletion cannot be undone.
Delete a sub-account's explicit monthly send limit. This destructive quota reset makes the sub-account inherit the parent account's remaining send capacity.
Permanently revoke one sub-account SMTP password by exact sub-account handle and password ID. This explicit destructive credential deletion cannot be undone.
Destructively remove one source, or every source, of suppression protection for a recipient. This permits future matching email delivery to that recipient.
Enroll the account's single external endpoint for MailChannels event callbacks. This changes the webhook configuration and causes future events to be sent to that endpoint; delete the existing enrollment before replacing it.
Retrieve account message open and click metrics, optionally filtered by time range and campaign.
Retrieve account processed, delivered, hard-bounced, and complaint metrics.
Retrieve account recipient unsubscribe metrics, optionally filtered by time range and campaign.
Return a sub-account's configured monthly send limit; -1 means it inherits the parent account's remaining capacity.
Return a sub-account's usage, effective monthly limit, and current billing-period dates.
Return the connected account's usage, effective monthly limit, and current billing-period dates.
Retrieve account processed, delivered, and dropped message volume metrics.
Retrieve the MailChannels public key identified by a webhook's Signature-Input header for signature verification.
Return one page of custom domains registered for click tracking, open tracking, or unsubscribe links.
Return one page of DKIM keys for a domain, optionally filtered by selector or lifecycle status.
Return one page of campaign or sub-account delivery metrics sorted by message volume.
Return one page of API-key metadata for a sub-account. MailChannels redacts the key values. Returned provider-created keys are sub-account credentials, not connection authentication for this action.
List SMTP-password metadata for a sub-account. MailChannels returns only IDs and partially redacted passwords. These provider-created passwords are sub-account credentials, not connection authentication for this action.
Return one page of sub-accounts owned by the connected parent account, including handle, company name, and enabled state.
Return one page of suppression entries for the connected account, optionally filtered by recipient, source, or creation date range.
Return one page of webhook delivery batches, optionally filtered by creation time, response category, or endpoint. If no time filters are supplied, MailChannels uses the last three days.
List all webhook endpoints enrolled for the connected MailChannels account.
Register an owner-controlled hostname for click tracking, open tracking, or unsubscribe links. DNS TXT ownership verification and a CNAME to links.mailchannels.net may be required before registration completes.
Render email content without delivering a message to any recipient. This action always uses MailChannels dry-run mode and has no delivery effect.
Synchronously create one new external delivery attempt for an existing webhook batch. This sends events again to the batch's webhook endpoint. A successful action response means MailChannels completed the attempt, not that the endpoint returned a 2xx status; inspect status_code.
Irreversibly rotate an active DKIM key: mark the existing key as rotated and create a replacement key. Publish the returned replacement DNS record before the old key's signing grace period expires or DKIM validation may fail.
Deliver email to the specified recipients. This action always performs real, irreversible delivery and consumes recipient quota; use RENDER_EMAIL to preview without delivery.
Queue email for real, irreversible external delivery to the specified recipients. A successful response confirms queue acceptance only, not eventual delivery, and the operation consumes recipient quota.
Set a sub-account's monthly send limit; setting zero prevents it from sending.
Suspend a sub-account and immediately prevent it from sending email until it is explicitly reactivated. This is a service-affecting operation.
Change the label or active status of one custom tracking domain identified by its exact hostname and event scope. At least one of name or status is required. Reactivation may require DNS verification.
Irreversibly revoke, retire, or begin rotating an existing DKIM key. This changes which key can sign mail and may require coordinated DNS changes.
Create and send a test callback to every enrolled webhook endpoint, then report whether each endpoint returned a 2xx response. This has an external side effect: every enrolled endpoint receives a test event.
The MailChannels integration connects your Dench AI CRM directly to MailChannels, so agents can read and act on your MailChannels data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
43 actions are available for agents to invoke on your behalf. Every call runs through MailChannels's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find MailChannels and click Connect — you'll authorize access through MailChannels's own sign-in flow. No API keys or code required.
Ask an agent to use MailChannels in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench MailChannels integration connects your AI CRM to MailChannels, so AI agents can work with your MailChannels data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The MailChannels integration currently exposes 43 actions, including Activate Sub-account, Check Domain Authentication, Create DKIM Key, Create Sub-account, Create Sub-account API Key, and Create Sub-account SMTP Password. Agents invoke them on your behalf from chat or from automations.
No. You connect MailChannels from your Dench workspace using MailChannels's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through MailChannels's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the MailChannels connection from your workspace settings at any time.