Email marketing
Connect Mailchimp to Chatsy
Review the configured newsletter tools and their consent boundary. The connection can be set up, but an agent cannot run these actions yet.
Route these requests to your team
Until agent execution passes end-to-end testing, set up human handoff so a person handles the requests these tools would cover.
Connects with an API key
Chatsy verifies the credential with Mailchimp before saving it, then stores it encrypted with AES-256-GCM.
Scope
What is configured
Action templates
- Get audiencesReadsList Mailchimp audiences and their IDs.
- Add subscriberWritesAdd a subscriber with email and optional first and last name.
The tool instruction says to ask for email marketing consent; the endpoint does not require a separate consent-confirmation field.
Setup guide
Connect and review Mailchimp
Connect the service and review the configured tools.
- 01
Connect the service
In Integrations, choose Mailchimp and enter an API key that includes its datacenter suffix.
- 02
Review the configured tools
The connection creates provider tool records for existing agents. Review their methods, fields, and enabled state.
Limits and fit
Where this setup can fail, and when another path fits better.
Common failure modes
- The credential is invalid, expired, or later revoked.
- An enabled tool is asked to perform an action outside the fields and methods it supports.
- The agent runtime calls a provider route without the required session and the request is rejected.
Not a fit for
- Workflows that need actions not listed on this page.
- Requests that should always be reviewed by a person before an external action runs.
- Agent workflows that depend on these configured tools before the runtime authentication boundary is fixed and tested end to end.
FAQ
Common questions
Ready to connect Mailchimp?
Create an agent, connect the service, and review its configured tools.