Automations and 3rd party integration
Automations associate a Wallkit system event with an action. An external connection supplies the publication settings that a service such as Mailchimp uses.
Know the pieces
| Piece | Meaning |
|---|---|
| Event or trigger | A system occurrence that can lead to processing, such as a reader profile update. It is separate from a ticketed gathering in Tickets & Events. |
| Condition | An action-specific check of the event's value, where that action supports one. Conditions are not applied uniformly to every action type. |
| Action | The selected handler, shown as Type in Automations. It may attempt an external update or another configured operation. |
| Connection | The publication's provider settings, including the target audience and private credential where required. |
For City Journal, a Mailchimp rule can map a reader's first name after a profile update. That action can also request a subscribed-state change; it is not just a harmless name copy. Confirm the intended behavior with the publication and integration owners before enabling it.
Choose your task
| Need | Start here |
|---|---|
| Prepare a reader profile-update rule | Prepare an automation rule |
| Prepare the publication's Mailchimp settings | Prepare a third-party integration |
| Inspect the saved rule and connection | Review automation and integration settings |
Start with Find your publication settings to confirm the publication context. Reader newsletter preferences, provider audience state, Wallkit membership and article access remain separate. A saved setting is not evidence that an external action completed or a message was delivered.