Content DistributionCan make changes
Publish Email
Send a final digest or standalone authority email through a configured ESP API.
Branding plugin
Email Service Provider
Provider-agnostic ESP contract for digest or standalone authority emails with list management, opt-in, unsubscribe, and metrics owned by the ESP.
Connection facts
What the Email Service Provider connector actually exposes.
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
- Connection method
- api-key
- Setup
- Select a project-designated ESP that exposes send and metrics APIs, then store only its API key and safe sender/audience refs in StackOS.
- Capability groups
- Content Distribution
- Action boundaries
- 1 write action
Action catalog
Actions listed for Email Service Provider.
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
1 matching action
Direct answer
How does the Email Service Provider integration work?
People continue using Email Service Provider as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
- 01Your requestStart in your AI
- 02StackOS planExpands the steps
- 03Email Service ProviderDoes its bounded part
- 04Checked resultKeeps the proof
More from Branding
Related integrations.
Branding
Channel Metrics
Provider-neutral metrics contract for channel-native outcome snapshots.
Outcome Learning
Branding
Git Remote
Git-backed canonical publishing target for static sites or repository-rendered blogs.
Content Distribution
Branding
LinkedIn API
LinkedIn publishing provider contract for member or organization posts where API access permits it.
Content Distribution
Common questions
Email Service Provider and StackOS.
What can the Email Service Provider integration do in StackOS?
The current catalog includes 1 Email Service Provider action across Content Distribution. The exact actions used depend on the workflow and approval rules.
Does StackOS replace Email Service Provider?
No. Email Service Provider remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.