FlowBeacon on Make.com
The FlowBeacon custom app lets you run governance evaluations, retrieve violations and remediation steps, and monitor org-wide compliance — all from within your Make.com scenarios. The app is available in the Make.com marketplace under FlowBeacon Governance.
Connect the app
- Open any Make.com scenario and click + to add a module.
- Search for FlowBeacon.
- Select any module — Make prompts you to create a connection on first use.
- In the connection dialog, paste your
fb_live_...API key from the FlowBeacon console. - Click Save. The connection test calls the health endpoint; a green checkmark confirms it worked.
If you don't have one yet, sign up for API access, then go to Settings → API Keys → Create Key. Keys start with fb_live_ and are shown once on creation.
Module reference
The app has eleven modules across four groups.
Evaluation modules
Submit blueprints for governance analysis and retrieve results.
Submit Evaluation
Evaluates the current running scenario's blueprint inline. The blueprint is captured automatically from the scenario — no extra modules needed. This is the default evaluation entry point for most workflows.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
| Scenario ID | Text | Yes | Echoed back in all results and webhooks. Map from {{scenario.id}} or supply your own identifier. |
| Save scenario to FlowBeacon workspace | Boolean | No | When on, FlowBeacon persists the blueprint for history, trend tracking, and remediation lookups. Default: off (evaluation is ephemeral). |
Outputs
| Field | Type | Notes |
|---|---|---|
| Evaluation ID | Text | Pass to Get Evaluation to poll for completion. |
| Status | Text | Always processing on initial response. |
| Result Token | Text | Single-use JWT (15-min TTL). Pass to Get Results By Token to skip polling. |
| Quota › Plan | Text | free or pro |
| Quota › Evaluations used today | Integer | |
| Quota › Daily limit | Integer | null = unlimited (Pro). |
| Quota › Resets at | Date | When the current quota window resets. |
Evaluate Blueprint
Evaluates a blueprint object you supply explicitly — for example, one retrieved from another team's scenario via the Make Get a Scenario Blueprint module, or loaded from a data store. Use for cross-team audits and CI-style checks outside the current scenario.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
| Scenario ID | Text | Yes | Your identifier for this blueprint — echoed in all results. |
| Scenario Name | Text | Yes | Human-readable label shown in FlowBeacon reports. |
| Blueprint (object) | Any | Yes | Map the raw blueprint object from Get a Scenario Blueprint or another source. |
| Save to FlowBeacon workspace | Boolean | No | Default: on. |
Outputs
| Field | Type | Notes |
|---|---|---|
| Evaluation ID | Text | |
| Status | Text | processing on initial response. |
| Total Scenarios | Integer | |
| Mode | Text | |
| Result Token | Text | Single-use JWT, 15-min TTL. |
Get Evaluation
Polls the status of an evaluation started by Submit Evaluation or Evaluate Blueprint. Use in a loop with a filter on Status = complete before mapping results downstream.
Inputs
| Field | Type | Required |
|---|---|---|
| Evaluation ID | Text | Yes |
Outputs
| Field | Type | Notes |
|---|---|---|
| Status | Text | processing → complete or error |
| Total Scenarios | Integer | |
| Completed | Integer | Scenarios processed so far. |
| Error Message | Text | Only present when status = error. |
| Scenarios[] › Scenario ID | Text | |
| Scenarios[] › Scenario Name | Text | |
| Scenarios[] › Governance Score | Integer | 0–100 |
| Scenarios[] › Total Violations | Integer | |
| Scenarios[] › Critical Violations | Integer | |
| Scenarios[] › Compliance Gap Policy Codes | Array of Text | Policy codes with compliance gaps. |
| Scenarios[] › Module Violations[] | Array | Per-module badge and violated policy codes. |
Get Results By Token
Fetches evaluation results using the single-use JWT token returned by Submit Evaluation or Evaluate Blueprint. Bypasses the polling loop — ideal for short-lived evaluations where you want results immediately after submission.
:::note Token constraints The result token is single-use and expires 15 minutes after issue. Calling this module consumes it; a second call with the same token returns an error. :::
Inputs
| Field | Type | Required |
|---|---|---|
| Result Token (JWT) | Text | Yes |
Outputs
| Field | Type | Notes |
|---|---|---|
| Scenario ID | Text | |
| Scenario Name | Text | |
| Evaluation Status | Text | evaluated or not_evaluated |
| Passing Count | Integer | |
| Failing Count | Integer | |
| Evaluated Codes | Array of Text | Policy codes checked in this evaluation. |
Results and graph modules
Fetch scenario-level results and module topology from the FlowBeacon workspace. The scenario must have been saved (Save to workspace = on) for these modules to return data.
Get Scenario Results
Retrieves full violation detail for a saved scenario — per-violation severity, compliance framework mappings, evidence, and per-module badges. More detailed than the summary returned by Get Evaluation.
Inputs
| Field | Type | Required |
|---|---|---|
| Scenario ID | Text | Yes |
Outputs
| Field | Type | Notes |
|---|---|---|
| Scenario ID | Text | |
| Scenario Name | Text | |
| Evaluation Status | Text | evaluated or not_evaluated |
| Passing Count | Integer | |
| Failing Count | Integer | |
| FlowBeacon Score | Integer | 0–100 |
| Compliance Status | Text | compliant or gaps |
| Evaluated Policy Codes | Array of Text | |
| Violations[] › Policy Code | Text | |
| Violations[] › Title | Text | |
| Violations[] › Status | Text | fail / warn / pass / n-a |
| Violations[] › Severity | Text | critical / high / medium / low |
| Violations[] › Description | Text | |
| Violations[] › Evidence | Text | Why this policy failed. |
| Violations[] › Remediation Available | Boolean | |
| Violations[] › Failing Modules[] | Array | Module ID, name, type, badge, reason. |
| Violations[] › Compliance Frameworks[] | Array | Framework, control, article, section, requirement. |
| Module Summary[] | Array | Per-module badge and violation count rollup. |
Get Scenario Module Graph
Returns the full topology of a scenario — every module node with its governance badge, plus the connections between them. Use to build visual overlays, identify high-risk modules, or map data flows.
Inputs
| Field | Type | Required |
|---|---|---|
| Scenario ID | Text | Yes |
Outputs
| Field | Type | Notes |
|---|---|---|
| Scenario ID | Text | |
| Scenario Name | Text | |
| Modules Count | Integer | |
| Modules[] | Array | Module ID, name, type, governance badge. |
| Connections[] | Array | Source-to-target wiring between modules. |
Get Remediation Steps
Returns ordered, human-readable fix steps for a specific policy violation on a specific scenario. Feed in the scenario ID and the policy code from Get Scenario Results or Get Evaluation — FlowBeacon returns step-by-step instructions with compliance context.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
| Scenario ID | Text | Yes | |
| Policy Code | Text | Yes | e.g. FB-SEC-001. From Violations[] › Policy Code in scenario results. |
Outputs
| Field | Type | Notes |
|---|---|---|
| Policy Code | Text | |
| Title | Text | |
| Description | Text | |
| Severity | Text | critical / high / medium / low |
| Estimated Effort | Text | |
| Evidence Summary | Text | Why FlowBeacon flagged this violation. |
| Steps[] | Array of Text | Ordered remediation instructions. |
| Compliance Frameworks[] | Array | Framework, control, article, section, requirement. |
Organization and policy modules
Get Org Summary
Returns your organization's overall governance posture — aggregate score, critical violations count, passing rate, and total scenarios evaluated. Ideal for scheduled health digests and executive dashboards.
Inputs: None.
Outputs
| Field | Type | Notes |
|---|---|---|
| Organization ID | Text | |
| Score | Integer | 0–100 aggregate governance score. |
| Critical Violations | Integer | |
| Passing | Integer | Scenarios currently compliant. |
| Total Scenarios | Integer | |
| Evaluated | Integer | Scenarios with at least one evaluation on record. |
List Policies
Returns the full policy catalog with codes, categories, severity levels, and descriptions. Use to build policy pickers in downstream scenarios, or to enumerate which policies apply to a compliance program.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
| Limit | Integer | No | Maximum policies to return. Omit for all. |
Outputs (one bundle per policy)
| Field | Type | Notes |
|---|---|---|
| Code | Text | Stable identifier, e.g. FB-SEC-001. |
| Title | Text | |
| Category | Text | security / access-control / data-integrity / etc. |
| Severity | Text | critical / high / medium / low |
| Intent | Text | One-line summary of what the policy enforces. |
| Description | Text | Full policy description. |
Trigger module
Watch Completed Evaluations
Instant trigger — starts your scenario the moment FlowBeacon completes an evaluation for your organization. Eliminates polling loops entirely. Use as the entry point for event-driven governance workflows.
Make registers a webhook with FlowBeacon automatically when you activate a scenario that uses this trigger. FlowBeacon delivers one evaluation.complete payload per completed evaluation batch.
Inputs: None.
Outputs
| Field | Type | Notes |
|---|---|---|
| Event | Text | Always evaluation.complete |
| Evaluation ID | Text | |
| Organization ID | Text | |
| Scenarios[] › Scenario ID | Text | |
| Scenarios[] › Scenario Name | Text | |
| Scenarios[] › Evaluation Status | Text | |
| Scenarios[] › Passing Count | Integer | |
| Scenarios[] › Failing Count | Integer | |
| Scenarios[] › Evaluated Codes | Array of Text | Policy codes checked. |
Advanced module
Make a FlowBeacon API Call
Raw HTTP access to any FlowBeacon API endpoint. Use when you need an endpoint not covered by the purpose-built modules, or for exploratory and debugging purposes.
Inputs
| Field | Type | Required | Notes |
|---|---|---|---|
| URL | Text | Yes | Path under /api/public/v1, e.g. /governance/policies. Leading slash required. |
| Method | Select | Yes | GET / POST / PUT / DELETE |
| Query String | Array | No | Key-value pairs appended as ?key=value. |
| Headers | Array | No | Additional request headers. |
| Body | Any | No | Request body for POST/PUT requests. |
Outputs
| Field | Type |
|---|---|
| Body | Any |
| Headers | Collection |
| Status Code | Integer |
HMAC signing
Make's expression language cannot sign request bodies inline, so the app does not send the X-FB-Signature header by default. If your FlowBeacon organization has HMAC enforcement enabled, route Make traffic through a thin signing proxy (a Cloudflare Worker, Lambda, or similar) that adds the signature before forwarding to api.flowbeacon.ai.
See Sign requests with HMAC for the canonical signing algorithm and a reference proxy implementation.
Error reference
All modules surface structured error messages:
| Error | Meaning | Action |
|---|---|---|
daily_limit_reached | Free-tier evaluation quota hit | Upgrade to Pro, or wait for the quota reset shown in Quota › Resets at. |
verify_email_required | Unverified account hit the free evaluation budget | Verify your email at app.flowbeacon.ai. |
blueprint_too_large | Blueprint exceeds the size limit | Simplify the scenario or split it before evaluating. |
| HTTP 401 | API key invalid or revoked | Generate a new key in the FlowBeacon console. |
| HTTP 429 | Rate limit hit | Respect the Retry-After header; add a delay module before retrying. |
| HTTP 403 | HMAC required but missing or invalid | Route requests through a signing proxy. |
Next steps
- Make.com Workflow Patterns — step-by-step module flows for common use cases.
- Sign requests with HMAC — how to sign behind a proxy.
- Handle webhooks — webhook delivery, verification, and rotation.