Review automation and integration settings
Use Automations and Resource settings to inspect saved rules and connections. For the Mailchimp flow, these pages show configuration rather than processing history. Ask the integration owner to check whether the expected action completed.
Inspect the rule
- Confirm the publication and open Automations.
- Narrow the list with Event title, Type and Active where useful. Use the list's paging controls to locate the intended rule.
- Read its #, Event, Type, Condition, Value from event, Template when applicable, and Active indication.
- Click # to inspect the editor's saved event, action and mappings. Avoid changing Active, saving or deleting during inspection.
The list can include global rules as well as rules for the selected publication. Confirm which rule the integration owner intends you to inspect; visibility alone does not establish exclusive publication ownership.
For City Journal's profile-update example, check the corresponding event, Mailchimp type and intended first-name mapping. Mailchimp hides the Condition selector and does not apply the generic condition checks, even if a stored condition appears in the list.
Interpret the state narrowly
| What you can see | What it establishes |
|---|---|
| Rule ID, event, type and mappings | The stored association and selected data fields. |
| Rule Active | The rule's stored eligibility setting. It is separate from the reader-account Active flag and does not prove an attempt occurred. |
| Condition or Value from event | Saved configuration; whether it restricts execution depends on the selected handler. |
| Provider key/audience/category settings | The available saved connection configuration, not verified provider health or successful processing. |
| Reader newsletter flags or Mail log elsewhere | Their specific preference or mail-record state, rather than a universal record of this automation's execution. |
The saved rule describes what should be processed. To trace an expected event through processing and the provider result, give the integration owner the event and observation time.
Inspect the connection
Open the publication's Resource settings → Email & COMMS platforms → MailChimp settings when available. Compare the intended audience ID and interest-category Name with the service owner's configuration. Keep the private Key out of copied records and shared screenshots.
Missing or locked fields are an access/configuration question, not proof that the service is off. Field-catalogue choices and reader preference views can contact the provider; they are separate from an automation run log.
Investigate an apparently missing action
First check the selected publication, intended event, rule ID, action type, Active state, mapping and connection configuration. Confirm that the event you expected corresponds to the configured trigger. Saving or enabling a rule does not establish that it processed that occurrence.
Give the integration owner the intended event and time, publication, rule ID and relevant reader context. Keep keys, invitation codes and Magic links out of the brief. Ask the owner to inspect the applicable event, processing and provider records.
If a result is missing, have the owner check those records before repeating an external action.
Use Prepare an automation rule or Prepare a third-party integration for the setup boundaries. Reader membership and article access remain separate from provider audience state.