Unsubscribe
Receive unsubscribe events for your selected audience after activation. Historical opt-outs, cleaned, profile-update and email-change events are not imported by this source.
Workflow template
Propagate Mailchimp unsubscribe events to the matching Sendy list. Use the same audience and Sendy List ID as your subscriber-sync workflow, with the event email mapped automatically.
How it works
Receive unsubscribe events for your selected audience after activation. Historical opt-outs, cleaned, profile-update and email-change events are not imported by this source.
Send the event email to the unsubscribe action for your fixed Sendy List ID. The address must be present in that list; the action does not create a subscriber or delete the contact.
The result
Email: fictional@example.com Destination: The Sendy List ID used by your subscriber-sync workflow Requested action: Unsubscribe from this list Contact deletion: Not requested
Fictional event and illustrative request. If the address is absent from the selected list, Sendy can return subscriber-not-found. The recipe sends no campaign; list notifications or automations can still depend on Sendy settings.
Before activation
Connect Mailchimp and Sendy, choose the Mailchimp audience and enter the same Sendy List ID used by your subscriber-sync workflow. Review the email mapping before activation.
Use a fictional test address already present in the selected Sendy list. For a test without emails, disable any Sendy unsubscribe notification or automation. The workflow does not create missing list entries.
Activate and wait for the Mailchimp trigger to show Connected, then unsubscribe the test address in the chosen Mailchimp audience. Verify its unsubscribed state in the matching Sendy list and inspect any error before retrying.
The list must match your subscribe workflow. Both templates need the same Mailchimp audience and Sendy List ID to propagate subscriptions and opt-outs for the same destination. This is one-way processing; it does not unsubscribe someone in Mailchimp from Sendy changes.
Missing subscribers can produce an error. Sendy can return subscriber-not-found if the email is absent from the selected list. The workflow does not create the missing subscriber or delete contact records as a workaround.
Historical and other event types are excluded. Only unsubscribe events received after activation are processed. Historical opt-outs, cleaned events, profile updates and email changes are not synchronized.
Destination automation settings still apply. No campaign is sent by this recipe. For tests without emails, disable Sendy unsubscribe notifications and automations. Manual reruns repeat the unsubscribe request rather than guaranteeing a single downstream effect.
Use the same Sendy List ID and Mailchimp audience as your subscriber-sync workflow. Otherwise the opt-out request can target a different list from the one receiving subscriptions.
Sendy can return a subscriber-not-found error. The workflow does not create a missing subscriber; verify the address and matching destination list before retrying.
No. It sends a one-way unsubscribe request to the selected Sendy list. It does not delete contacts, update Mailchimp or process cleaned, profile-update or email-change events.
Historical opt-outs are not imported; only unsubscribe events after activation are processed. The recipe sends no campaign, but disable any Sendy unsubscribe notification or automation for a test without emails.
Add subscribers to a Sendy list when they subscribe to your Mailchimp audience.
View template →