01
Audience operations desk
Keep authorized audience records and campaign preparation organized around your own process.
Communication
Build more with Mailchimp.
Email marketing platform for managing campaigns, audiences, and automation. Shape those capabilities into a system that fits your team.
Build concepts, not preinstalled apps. Provider plans, permissions, and API availability apply.
The possibilities
What could you build?
02
Campaign approval workspace
Review content, targeting, and readiness before a campaign reaches subscribers.
Start with the audience operations desk.
Keep the first version small enough to test with the people who will use it.
- 01Mailchimp
- 02Audience operations desk
- 03Reviewed next action
- 01
Choose the first job
Use the first idea as your brief: Keep authorized audience records and campaign preparation organized around your own process. Name the person responsible and the information they need to act.
- 02
Confirm access before connecting
Choose the intended audience and connect with an authorized Mailchimp user. Sending depends on that user's role. Preserve unsubscribe status and marketing consent.
- 03
Shape the app with Scout
Use the starter prompt below. Ask Scout to propose the records, source field mapping, views, and access rules. Preview sample data before connecting Mailchimp; keep source IDs so records stay traceable.
- 04
Pilot, then expand
Test with a small approved dataset and a least-privileged user. Check missing records, revoked access, repeated events, and failed requests. Enable live writes or messages only after the responsible owner approves the workflow.
Start with this prompt
Paste into Scout, then adapt it to your team. Do not paste credentials or private customer data.
Create this app with Mailchimp: Audience operations desk. Keep authorized audience records and campaign preparation organized around your own process. Start with sample data and a small, approved set of records. Before connecting live data: Choose the intended audience and connect with an authorized Mailchimp user. Sending depends on that user's role. Preserve unsubscribe status and marketing consent. Propose the data model, access rules, and source-to-app field mapping before implementation. Add source links, a last-updated time, and clear empty and connection-error states. Keep credentials out of client code. Require human approval for external messages, source changes, or money movement. Test duplicate events, revoked access, and recovery before publishing.
Make it work your way.
Start with Scout, or map the first build with our team.