Make.com Workflow Patterns

Four ready-to-build patterns covering the most common FlowBeacon use cases. Each pattern names the modules in sequence and explains what to map at every step.

---

Pattern 1 — Evaluate and poll for results

When to use: Run governance on a scenario's own blueprint and work through the full violation list in a single scenario run.

Module flow:

Submit Evaluation
  → Repeater + Get Evaluation  (poll until status = complete)
  → Iterator over Scenarios[]
  → Get Scenario Results
  → Iterator over Violations[]
  → Get Remediation Steps  (for each violation where remediation_available = true)

Step-by-step

Step 1 — Submit Evaluation

• Set Scenario ID to {{scenario.id}}.
• Set Save scenario to FlowBeacon workspace to true so Get Scenario Results can read the data in step 5.
• Note the Evaluation ID output — you'll map it into the polling loop.

Step 2 — Set up the polling loop

• Add a Repeater module after Submit Evaluation. Set Maximum number of cycles to 30 and Interval to 3 seconds (covers up to 90 seconds of processing).
• Add Get Evaluation after the Repeater. Map Evaluation ID from step 1.
• Add a Router after Get Evaluation with two routes:
  • Route A (keep polling): filter Status ≠ complete. Route back to the Repeater.
  • Route B (continue): filter Status = complete. Continue to step 3.
• Set the Repeater's Break directive to stop when route B triggers.

Step 3 — Iterate over scenarios

• Add an Iterator on route B. Source array: Scenarios[] from Get Evaluation.
• Each iteration bundle contains Scenario ID, Governance Score, Total Violations, and Critical Violations for one scenario.

Step 4 — Filter: skip clean scenarios

• Add a Filter after the Iterator: Total Violations > 0. This skips scenarios that passed cleanly.

Step 5 — Get Scenario Results

• Input: Scenario ID from the Iterator bundle.
• Returns the full Violations[] array with severity, evidence, and module attribution.

Step 6 — Iterate over violations

• Add another Iterator. Source array: Violations[] from step 5.
• Add a Filter: Remediation Available = true AND Status = fail.

Step 7 — Get Remediation Steps

• Input: Scenario ID from the step 3 iterator; Policy Code from the violation bundle (Policy Code field).
• Outputs ordered Steps[] and Estimated Effort — route these to your notification, ticketing, or logging module.

---

Pattern 2 — Event-driven with Watch Completed Evaluations

When to use: Trigger a Make scenario automatically the instant any evaluation completes. No polling, no delay — FlowBeacon pushes to Make the moment results are ready.

Module flow:

Watch Completed Evaluations  (instant trigger)
  → Iterator over Scenarios[]
  → Filter: failing_count > 0
  → Get Scenario Results
  → Iterator over Violations[]
  → Get Remediation Steps
  → Notify / log / create ticket

Step-by-step

Step 1 — Watch Completed Evaluations

• Add as the first module of a new scenario.
• Make registers a webhook with FlowBeacon automatically when you activate the scenario. Activate it before triggering any evaluations.
• Each trigger fires delivers one evaluation batch. The Scenarios[] array contains summary data for every scenario in the batch.

Step 2 — Iterator over Scenarios[]

• Source array: Scenarios[] from the trigger.
• Each bundle contains Scenario ID, Scenario Name, Passing Count, Failing Count, and Evaluated Codes.

Step 3 — Filter: skip passing scenarios

• Add a Filter: Failing Count > 0. Scenarios with no violations pass through; the rest are discarded.

Step 4 — Get Scenario Results

• Input: Scenario ID from the Iterator bundle.
• Returns full Violations[] with per-violation detail.

Workspace required

Get Scenario Results reads from the FlowBeacon workspace. The evaluation that triggered the webhook must have had Save to FlowBeacon workspace enabled (set on Submit Evaluation or Evaluate Blueprint). Without this, the module returns not_evaluated.

Step 5 — Iterator + Get Remediation Steps

• Same as Pattern 1, steps 6–7: iterate Violations[], filter on Remediation Available = true, call Get Remediation Steps with Scenario ID + Policy Code.

Step 6 — Downstream action

• Route remediation steps to Slack, a Jira ticket, a Google Sheets row, or any notification module.

---

Pattern 3 — Audit an external blueprint

When to use: Evaluate a scenario you don't own — another team's scenario, a scenario stored in a data store, or a blueprint from a CI pipeline. Uses Evaluate Blueprint instead of Submit Evaluation.

Module flow:

Make · Get a Scenario Blueprint
  → Evaluate Blueprint
  → Get Results By Token

Step-by-step

Step 1 — Make — Get a Scenario Blueprint (built-in Make module)

• Input: the target Scenario ID.
• Outputs the raw Blueprint object.

Step 2 — Evaluate Blueprint

• Scenario ID: the same ID from step 1 (or your own identifier).
• Scenario Name: a human-readable label for this blueprint in FlowBeacon reports.
• Blueprint (object): map the Blueprint output from step 1 directly.
• Save to FlowBeacon workspace: set true if you want to follow up with Get Scenario Results later.
• Outputs Evaluation ID and Result Token.

Step 3 — Get Results By Token

• Input: Result Token from step 2.
• Returns Passing Count, Failing Count, and Evaluated Codes immediately — no polling loop needed.
• The token is single-use and expires after 15 minutes.

For full violation detail: follow Get Results By Token with Get Scenario Results (requires workspace save = true from step 2), then Get Remediation Steps as in Pattern 1.

---

Pattern 4 — Scheduled org health digest

When to use: Daily or weekly report showing org-wide compliance posture with policy context. No trigger module needed — runs on a schedule.

Module flow:

[Schedule: daily or weekly]
  → Get Org Summary
  → Filter: critical_violations > 0
  → List Policies
  → Iterator over policies
  → Text Aggregator → Send report

Step-by-step

Step 1 — Schedule the scenario

• Open scenario settings and set the schedule to daily or weekly. No trigger module is required.

Step 2 — Get Org Summary

• No inputs.
• Key outputs: Score (0–100), Critical Violations, Passing, Total Scenarios, Evaluated.

Step 3 — Conditional alert

• Add a Router after Get Org Summary:
  • Route A: Critical Violations > 0 — continue to step 4 for urgent reporting.
  • Route B: Critical Violations = 0 — send a clean-bill summary directly and stop.

Step 4 — List Policies

• No required inputs. Set Limit to 50 unless you need the full catalog.
• Add an Iterator to process one policy bundle at a time.
• Use a Filter to surface only policies matching the severity of your failing scenarios (e.g. Severity = critical or Severity = high).

Step 5 — Aggregate and send

• Use a Text Aggregator to build a summary block from Score, Critical Violations, Passing, and the top policy titles.
• Route to your reporting destination — email, Slack, Google Docs, or a webhook.

---

Choosing the right pattern

Goal	Pattern
Evaluate the current scenario and act on results in the same run	1 — Evaluate and poll
React automatically when any evaluation completes	2 — Event-driven
Audit a scenario you don't own or control	3 — External blueprint
Scheduled compliance report for leadership	4 — Org health digest
Need full violation detail with compliance framework mappings	Any — follow with Get Scenario Results
Want results immediately without a polling loop	Any — use Get Results By Token after submission