For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/features/contacts/contact-automation-history.md.
  • English
  • How to see which automations a contact entered

    Every time a contact enters an automation, their history gets the Entered an automation activity, signed by Automation and carrying the name of the flow that fired. The name is a link: clicking it opens the automation in the editor.

    You find this by opening the contact and going to the History tab.

    What the activity shows

    ItemWhat it shows
    AuthorAutomation — no person was involved in the entry
    AutomationThe flow name, linking to its editor

    If the automation is renamed later, the history keeps showing the name it had when it fired — the trail does not change over time. If it is deleted, the link stays, but the editor will not find the flow.

    Filter the history by automation

    In the history filter, the Automation field lists the flows that appear in the selected period. Picking one leaves only what that automation did with the contact on screen — the entry and the actions that followed, such as tags applied.

    Works for both trigger and bulk dispatch

    Both paths record the same activity:

    • Trigger — the contact did something (was captured, received a tag, replied to a message) and the automation opened for them.
    • Bulk dispatch — you activated the automation over a list, a segment, or a tag, and it opened for every contact in the audience.

    In a bulk dispatch, the activities appear as the automation works through the audience, at the same pace as the dispatch. On a large audience, the last contacts get their history line after the first ones.

    What does not become an activity

    • Contact blocked by the repeat window. If the automation had already opened for that contact within the configured interval, the new attempt is discarded and no line is created — the history counts real entries, not attempts.
    • An automation that never opened. A trigger that did not match the flow conditions produces no activity at all.