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/automations/meeting-triggers.md.
  • English

      • How do I start an automation from a Clickmax Meet meeting?

      Use one of the three meeting triggers in the Scheduling category of the automation editor. They react to what happens in the Clickmax Meet room of a scheduled meeting: the contact who did not show up, the report that is ready and the outcome nobody recorded.

      Before you start

      • Workspace role: anyone who already edits automations.
      • Only meetings scheduled in the CRM with a Clickmax Meet room fire these triggers. Meetings on Google Meet, a fixed link or a standalone room created straight in Clickmax Meet do not.
      • The meeting needs a contact. Without a contact there is no contact automation to start.
      • All three accept the same optional filters as the other scheduling triggers: Event type, Attendant and Team. Empty fires for any meeting.

      Add the trigger

      1. Open the automation in the editor and click the start trigger.
      2. Under Scheduling, pick one of the triggers below.
      3. Set the filters in the drawer and click Done.
      4. Connect the trigger to a next step and publish the automation.

      Contact Did Not Join the Meeting

      Fires when the host is in the room and the contact has not joined 10 minutes after the scheduled time. It is the moment to send a "we are waiting for you" message with the room link.

      • The tolerance is fixed at 10 minutes and cannot be changed in the trigger.
      • It only fires if the host joined the room. A meeting nobody opened does not count as the contact missing it.
      • It only fires while the meeting still has no outcome (scheduled or confirmed). If it was already marked as completed, cancelled or no-show, it does not fire.
      • It fires at most once per meeting.

      Available variables: Meeting room link ({{meetingLink}}) — the same link the contact received in the invitation —, Meeting date and Meeting time (see Meeting date and time in messages).

      Meeting Report Ready

      Fires when the meeting report is ready. It fires once per meeting: regenerating the report later does not start the automation again.

      Specific filters, all optional:

      • Minimum score and Maximum score — from 0 to 10. Use both together for a range, for example 4 to 7.
      • Score band — A, B, C, D or F.
      • Meeting outcome — Closed, Deposit paid, Next step scheduled, Agreed to revisit, No next step or Lost.
      • Weakest stage — the stage of the method that took the most points from the score, such as Problem or Implication.

      When the meeting got no evaluation (for example, a conversation that was too short), it has no score, band, outcome or weakest stage. In that case a trigger with any of these filters does not fire; without an evaluation filter it fires normally. When the meeting was evaluated but no stage of the current scale carried weight, it has no score and no band but keeps its outcome: score and band filters do not fire, and the outcome filter works.

      Examples:

      • Score band F → create a coaching task for the manager.
      • Meeting outcome Next step scheduled → start the contact's follow-up sequence.

      Available variables:

      • Meeting summary ({{meetReportSummary}})
      • Meeting next steps ({{meetNextSteps}}) — the agreed tasks, one per line.
      • Meeting report link ({{meetReportUrl}})
      • Meeting recording link ({{meetRecordingUrl}})

      Both links only open for people with access to the workspace in Clickmax. Use them to notify your team, not to send to the contact.

      Meeting Outcome Pending

      Fires when the meeting ended — or nobody joined the room — and the outcome is still not recorded after the chosen number of hours. Use it to remind the host to record what happened.

      • Pick Hours without outcome: 1 h, 2 h, 4 h, 8 h, 24 h or 48 h. The field is required and accepts no other values.
      • Hours count from the end of the room. If nobody joined, they count from the scheduled end time.
      • Each mark fires once per meeting. To remind more than once, create one trigger per mark.
      • Recording the outcome (completed, cancelled or no-show) stops the following reminders for that meeting.
      • A meeting in progress does not fire.

      Meeting date and time in messages

      The Meeting date ({{meetingDate}}, formatted dd/mm/yyyy) and Meeting time ({{meetingTime}}, formatted HH:MM) variables show up in the editor when every start trigger of the automation is a meeting trigger: Meeting booked, Meeting rescheduled, Meeting confirmed, Meeting completed, Meeting no-show or Contact Did Not Join the Meeting. With any other start trigger alongside them (including Meeting cancelled), they don't show up.

      • Both use Brasília time.
      • The value is read from the meeting at send time, not when the automation starts: if the meeting is rescheduled while the automation waits, the message goes out with the new date and time. If the meeting is cancelled, the variables come out empty.

      For simple reminders from an agenda (for example, the day before at 10 a.m.), the agenda's Notifications tab does it without building an automation — see How do I send the meeting reminder the day before, at 10 a.m.?.

      If the trigger does not fire

      • The meeting has no Clickmax Meet room or no contact. Check the meeting location and the contact in the meeting panel.
      • The contact started the automation shortly before. The same contact only restarts an automation after the minimum interval set on the trigger (1 hour by default). With the default, the 1 h and 2 h reminders of the same meeting can fall inside that interval if they are in the same automation.
      • The evaluation filter does not match. A meeting without an evaluation never matches a score, band, outcome or weakest stage filter. A meeting with No score does not match a score or band filter.
      • Report regenerated. The report ready trigger already fired the first time and does not fire again.
      • Outcome pending on an old meeting. The reminder only fires when the meeting crosses the mark. Meetings that crossed it before the automation was published do not get the reminder.