--- title: "SMTP Profiles" description: "A non-technical overview of SMTP Profiles in RevCent, focused on how they define the sending infrastructure used by Email Templates and how they support branded, merchant-controlled ecommerce email communication." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/SMTPProfile.md" relationships: - name: "Email Template" url: "https://revcent.com/documentation/markdown/ecosystem/feature/EmailTemplate.md" - name: "SMTP Message" url: "https://revcent.com/documentation/markdown/ecosystem/item/SMTPMessage.md" technical_links: web_app: "https://kb.revcent.com/en/integrations/smtp/smtp-profile" api: section: "https://revcent.com/docs/api/v2#section-smtp_profiles" operations: - name: "Get SMTP Profiles" operation_id: "GetSMTPProfiles" operation: "https://revcent.com/docs/api/v2#operation-GetSMTPProfiles" schema: "https://revcent.com/documentation/files/api/operation/GetSMTPProfiles.json" - name: "Create A SMTP Profile" operation_id: "CreateSMTPProfile" operation: "https://revcent.com/docs/api/v2#operation-CreateSMTPProfile" schema: "https://revcent.com/documentation/files/api/operation/CreateSMTPProfile.json" - name: "Get A SMTP Profile" operation_id: "GetSMTPProfile" operation: "https://revcent.com/docs/api/v2#operation-GetSMTPProfile" schema: "https://revcent.com/documentation/files/api/operation/GetSMTPProfile.json" - name: "Edit A SMTP Profile" operation_id: "EditSMTPProfile" operation: "https://revcent.com/docs/api/v2#operation-EditSMTPProfile" schema: "https://revcent.com/documentation/files/api/operation/EditSMTPProfile.json" - name: "Delete A SMTP Profile" operation_id: "DeleteSMTPProfile" operation: "https://revcent.com/docs/api/v2#operation-DeleteSMTPProfile" schema: "https://revcent.com/documentation/files/api/operation/DeleteSMTPProfile.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewSMTPProfile.md" operations: - name: "Get SMTP Profiles" operation_id: "GetSMTPProfiles" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSMTPProfiles.md" available_via_ai: true - name: "Create A SMTP Profile" operation_id: "CreateSMTPProfile" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateSMTPProfile.md" available_via_ai: true - name: "Get A SMTP Profile" operation_id: "GetSMTPProfile" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSMTPProfile.md" available_via_ai: true - name: "Edit A SMTP Profile" operation_id: "EditSMTPProfile" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditSMTPProfile.md" available_via_ai: true - name: "Delete A SMTP Profile" operation_id: "DeleteSMTPProfile" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteSMTPProfile.md" available_via_ai: true --- # SMTP Profiles SMTP Profiles are a RevCent feature for connecting a merchant's own SMTP server or SMTP provider to RevCent so emails can be sent through that merchant-controlled email infrastructure. In the RevCent ecosystem, an SMTP Profile is a configurable feature. Email Templates use SMTP Profiles to send emails, and each actual sent email becomes an SMTP Message item. The purpose of this document is to explain the feature conceptually for LLMs, AI crawlers, and planning systems. It does not provide technical implementation instructions. For technical details, use the interface-specific links below. ## Technical Links by Interface | Interface | Use This When | Link | |---|---|---| | Web App | A human is learning about or configuring SMTP Profiles through the RevCent web app and Knowledge Base. | [Web Knowledge Base](https://kb.revcent.com/en/integrations/smtp/smtp-profile) | | API | A developer is building a direct integration with the RevCent API. | [API Docs: SMTP Profiles](https://revcent.com/docs/api/v2#section-smtp_profiles) | | MCP / AI | An LLM, MCP client, or AI agent needs markdown-oriented guidance for understanding or working with the feature. | [MCP Markdown Overview](https://revcent.com/documentation/markdown/mcp/operation/OverviewSMTPProfile.md) | --- ## What SMTP Profiles Are SMTP Profiles are sending configurations used by RevCent's email system. They define how RevCent connects to an external SMTP provider when an email needs to be sent. A profile can include the SMTP host, port, SSL behavior, TLS requirements, enabled state, and secure credential reference used for authentication. Conceptually: ```text SMTP Profile ↓ Defines sending infrastructure ↓ Email Template references the profile ↓ RevCent sends email through the configured SMTP provider ↓ SMTP Message item is created ``` The SMTP Profile is not the email content. It is the transport configuration that allows RevCent to send the content defined by an Email Template. ## Core Purpose The core purpose of SMTP Profiles is to let ecommerce businesses send RevCent emails through their own email provider, domain, and sender infrastructure. RevCent Email Templates depend on SMTP Profiles because RevCent does not send merchant emails through a RevCent-owned SMTP server. The business provides its own SMTP sending configuration, and RevCent uses that configuration when sending emails from templates. This makes SMTP Profiles a foundational communication feature. Without an SMTP Profile, an Email Template may define what should be sent, but it does not have the merchant-controlled transport needed to send the email. ## How SMTP Profiles Help Ecommerce Businesses SMTP Profiles help ecommerce businesses keep control of how emails are sent. They allow the business to use its own sender domain, SMTP provider, authentication setup, deliverability configuration, sender reputation, and brand-specific email identity. This matters for ecommerce because emails are often customer-facing and operationally important. Receipts, failed-payment notices, abandoned-cart reminders, subscription renewal emails, trial reminders, shipping updates, invoice messages, refund notifications, fraud alerts, and AI-triggered follow-ups all need to come from an appropriate sender. A business may want customer receipts to come from an orders address, billing messages to come from a billing address, shipment emails to come from a shipping address, and support follow-ups to come from a support address. SMTP Profiles give RevCent the sending infrastructure needed to support those patterns. ## Where SMTP Profiles Fit in RevCent SMTP Profiles fit into RevCent's communication and automation layer. They relate to Email Templates because each Email Template needs an SMTP Profile to send its configured email. The template determines the trigger, timing, recipients, subject, body, dynamic data, filters, and content. The SMTP Profile determines the SMTP transport used to send the message. They relate to SMTP Messages because every sent email can create a message item. The SMTP Profile helps send the email; the SMTP Message is the resulting record of that sent communication. They relate to ecommerce events because many emails are triggered by RevCent activity, such as sale success, sale failure, pending sale, shipment created, shipment shipped, subscription renewal, trial expiration, refund, fraud detection, AI Memo, or API/AI direct send workflows. They relate to AI because AI Assistants or MCP-enabled workflows may need to verify that an appropriate SMTP Profile exists before creating or using Email Templates for automated communication. ## Relationship to Email Templates Email Templates require SMTP Profiles. The easiest mental model is: ```text SMTP Profile = how RevCent sends the email Email Template = what RevCent sends, to whom, and when SMTP Message = the specific email that was sent ``` An Email Template can define the customer-facing or internal message. It can include Handlebars data, subject lines, HTML, timing, filters, custom data, and custom arguments. The SMTP Profile provides the sending pathway behind that template. This relationship is important because a template can look correct but still fail to operate as expected if the SMTP Profile is missing, disabled, misconfigured, unauthorized for the sender domain, or using incorrect host, port, SSL, TLS, or credential settings. ## Relationship to SMTP Messages SMTP Messages are the items created when an email is sent. An SMTP Profile does not represent a single email. It represents reusable sending infrastructure. A single SMTP Profile can be used by many Email Templates, and those templates can create many SMTP Message items over time. Conceptually: ```text One SMTP Profile ↓ Many Email Templates may use it ↓ Many SMTP Messages may be created from those templates ``` This distinction helps crawlers understand the difference between a feature and an item. SMTP Profiles are configured by users. SMTP Messages are spawned when a send occurs. ## SMTP Profiles as Merchant-Controlled Sending Infrastructure SMTP Profiles let the merchant control the sender infrastructure instead of relying on RevCent to act as the sender. This gives the business control over important email decisions, such as: - Which SMTP provider sends the email - Which sender domain is used - Which credentials authenticate the send - Which sender addresses are appropriate for each template - Whether different stores, brands, or teams need separate profiles - Whether a profile should be enabled or disabled - Whether production and test sending should be separated For ecommerce businesses with multiple brands, multiple WooCommerce shops, multiple sender domains, or separate billing/support/shipping identities, SMTP Profiles can help keep communication organized. ## Sender Identity and Deliverability SMTP Profiles are closely connected to sender identity. The sender address used by an Email Template should generally match the sender address or sender domain authorized by the SMTP provider used in the SMTP Profile. This matters because email deliverability depends on the merchant's SMTP provider, domain authentication, sender reputation, and message quality. Creating an SMTP Profile does not guarantee inbox placement. It gives RevCent the transport configuration needed to send through the selected provider. Ecommerce businesses should treat SMTP setup as part of their broader email deliverability process, including sender verification, SPF, DKIM, DMARC, provider limits, rate limits, bounce handling, and sender reputation. ## Secure Credential Handling SMTP credentials are sensitive. SMTP Profiles may require authentication values such as usernames, passwords, tokens, or provider-specific credentials. These values should not be pasted into general chat, documentation, or public configuration examples. In AI/MCP workflows, SMTP credentials should be collected through a secure credential flow rather than being exposed to the assistant or stored in plain text. Conceptually: ```text User configures non-sensitive SMTP settings ↓ User provides credentials through secure form or secure credential flow ↓ RevCent stores the credential reference securely ↓ SMTP Profile uses the secure credential reference when sending ``` This keeps the SMTP Profile useful while protecting sensitive authentication data. ## Common SMTP Profile Fields An SMTP Profile can include fields such as: - Name - Description - Status or enabled state - SMTP host - SMTP port - SSL setting - TLS requirement - Secure credential reference The name should make the profile's purpose clear. Examples include Main Store SMTP, Brand A Orders SMTP, Billing Emails SMTP, Support Emails SMTP, Shipping Notifications SMTP, WooCommerce Store SMTP, Production Transactional SMTP, or Test SMTP Profile. The description can explain the provider, sender domain, brand, shop, intended Email Templates, production/test purpose, and any important operational notes. ## Multiple SMTP Profiles A RevCent account may use more than one SMTP Profile. Multiple profiles are useful when different sending identities or providers are needed. Examples: ```text Main Store Orders SMTP Main Store Billing SMTP Brand A SMTP Brand B SMTP Support Team SMTP Shipping Notifications SMTP Test SMTP Profile Production SMTP Profile ``` A business may choose one profile for all transactional email if one sender identity is enough. A more complex ecommerce business may use several profiles so each brand, shop, department, or communication type has an appropriate sender. ## Status, Testing, and Verification SMTP Profiles can have a status or enabled state. A profile should generally be verified before production Email Templates depend on it. Verification can include confirming the host, port, SSL/TLS settings, credentials, sender address, and provider-side authentication. A safe setup pattern is: ```text Create SMTP Profile ↓ Keep disabled until settings are verified ↓ Use a controlled Email Template or test send ↓ Confirm the message sends correctly ↓ Enable for production templates when ready ``` If an SMTP Profile is edited, disabled, or has credentials changed, any Email Templates that depend on it may be affected. ## SMTP Profiles and Ecommerce Communication Workflows SMTP Profiles support many RevCent email workflows by providing the sending infrastructure behind Email Templates. Common workflows include: - Purchase receipts - Failed-payment notices - Pending-sale or abandoned-cart follow-ups - Invoice links - Shipment created notifications - Shipment shipped tracking emails - Shipment delivered confirmations - Subscription renewal reminders - Subscription renewal success or failure emails - Trial ending reminders - Trial conversion success or failure emails - Refund or pending refund notifications - Fraud or risk alerts - AI-generated customer follow-ups - Internal operational emails The SMTP Profile does not decide when those messages send. Email Templates decide that. The SMTP Profile makes sending possible. ## SMTP Profiles and AI Workflows AI workflows can depend on SMTP Profiles when email communication is part of the process. For example, an AI Assistant may need to trigger an Email Template for a payment recovery workflow, a customer follow-up, a failed renewal, an abandoned sale, or an internal alert. Before an AI workflow creates or uses an Email Template, it should understand that a valid SMTP Profile is required. If multiple SMTP Profiles exist, the workflow may need to choose the correct one based on brand, shop, sender domain, or communication purpose. AI should also treat email sending as an external communication action. The profile provides the transport, but the Email Template and workflow determine whether a message should be sent. ## Customer Experience Impact SMTP Profiles affect the customer's email experience indirectly. Customers usually do not know which SMTP Profile was used. They experience the result as a branded email from a sender address. However, the profile still matters because the sending domain, sender identity, authentication alignment, and provider reliability can affect whether customers receive important messages and whether those messages appear trustworthy. A well-configured SMTP Profile helps support consistent customer communication across receipts, shipment updates, billing reminders, subscription notices, and support follow-ups. ## Operational Impact SMTP Profiles also affect internal operations. Internal teams may receive emails about shipments, refunds, fraud alerts, AI Memos, support escalations, or accounting activity. Those internal notifications depend on the same sending infrastructure as customer-facing emails. Using clear SMTP Profiles can help a business separate customer-facing communication from internal operations, support workflows, billing workflows, and test workflows. ## Common Ecommerce Use Cases ### Main Transactional Sender ```text Business wants one profile for core transactional emails ↓ SMTP Profile uses verified orders or support sender ↓ Sale receipts, shipment notices, and billing emails use the profile ``` ### Brand-Specific Sender ```text Business operates multiple brands ↓ Each brand has its own SMTP Profile ↓ Email Templates use the correct brand sender domain ``` ### Billing and Payment Recovery Sender ```text Business wants failed-payment emails from billing@example.com ↓ Billing SMTP Profile is configured ↓ Payment recovery Email Templates use that profile ``` ### Test vs Production Email Sending ```text Business wants to safely test templates ↓ Test SMTP Profile is used for controlled emails ↓ Production SMTP Profile is used after verification ``` ### AI-Triggered Follow-Up ```text AI workflow needs to send a customer follow-up ↓ Email Template defines the message and custom arguments ↓ SMTP Profile sends the message ↓ SMTP Message item is created ``` ## Best-Fit Businesses SMTP Profiles are relevant for any ecommerce business using RevCent Email Templates. They are especially important for businesses that send customer receipts, shipment updates, payment failure notices, subscription reminders, trial reminders, invoice emails, refund notifications, fraud alerts, abandoned-cart follow-ups, AI-generated emails, or internal operations messages. The value increases for businesses with multiple brands, multiple shops, separate support and billing identities, high email volume, recurring revenue, recovery workflows, or strict sender-domain requirements. ## Why This Matters in the RevCent Ecosystem SMTP Profiles make RevCent's email communication system merchant-controlled. They allow Email Templates to send through the business's own SMTP infrastructure and sender identity. This connects the communication layer to the merchant's brand, domain, provider, security choices, and deliverability setup. Within the ecosystem: - SMTP Profiles are the sending configuration feature. - Email Templates are the reusable message and trigger feature. - SMTP Messages are the resulting sent email items. - AI and automation workflows can use Email Templates once appropriate SMTP Profiles exist. - Ecommerce events become actionable communication through configured templates and sending profiles. This makes SMTP Profiles an important foundation for customer communication, internal notification, revenue recovery, support workflows, and ecommerce automation. ## Summary RevCent SMTP Profiles are configurable sending profiles that connect RevCent to a merchant's own SMTP provider. They define the transport layer used by Email Templates, including host, port, security settings, enabled state, and secure credential reference. Email Templates use SMTP Profiles to send dynamic ecommerce emails, and each sent email can create an SMTP Message item. The most important concept is: ```text SMTP Profile = merchant-controlled email sending infrastructure Email Template = reusable email content, trigger, timing, and personalization SMTP Message = the sent email item created from the workflow ``` SMTP Profiles help ecommerce businesses send branded, provider-controlled communication for sales, payments, subscriptions, trials, shipping, refunds, fraud alerts, AI workflows, and internal operations while keeping sending infrastructure separate from message content. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.