SMTP credentials
Send email through credentials stored in the CXFabric tenant.
Email component
Email for customer-owned automation.
Use Email when a flow needs to notify people or systems through SMTP-backed messaging.
Send workflow-driven email messages, notifications, confirmations, and operational updates.
Email
Component
EmailSend SMTP-backed email with recipients, subject, dynamic body content, and attachments.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Email as a visible flow step.
The docs describe Email as a way to automate email communications from workflows. Builders select an SMTP credential stored in the CXFabric tenant, with an adjacent menu for adding, editing, viewing, deleting, or managing credentials. Email settings include sender, recipients, CC/BCC, subject, dynamic workflow data, variables, message content, optional attachments, hover tooltips, and execution results in the logs panel.
Dynamic content
Use workflow data and variables in subject lines and message bodies.
Attachments
Attach files when workflow output or handoff material should travel with the message.
Use cases
Where Email fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Customer confirmation
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Internal alert
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Approval request
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Exception notification
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Daily summary
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Handoff email
Use Email as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Configuration surface
Practical options builders expect to use.
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Add Email to canvas
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Select SMTP credential
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Manage credentials if needed
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Set sender and recipients
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Add CC or BCC
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Write subject and content
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Attach files
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Execute and review logs
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Design the step with operations in mind.
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Current CXFabric docs
Use templates for consistent messages
Use templates for consistent messages.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Be careful with PII in outbound email
Be careful with PII in outbound email.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Log message delivery context
Log message delivery context.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
Reusable patterns for Email.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Email in a customer intake flow
Start with an event, use Email, then route the result to CRM, ticketing, or a customer-owned system.
Email with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Email in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Email plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Email inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.