Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
FlowBeacon
Tally

Connect FlowBeacon and Tally

Explore ready-made FlowBeacon and Tally templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate FlowBeacon with Tally and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Tally
Trigger: Watch New Responses
FlowBeacon
Action: Select an action
1. Select a trigger

  • Triggers when a new form response is submitted.

2. Select an action

  • Retrieves the module-by-module governance breakdown (the module graph) for a saved scenario.

  • Retrieves the status and per-scenario governance results of a submitted evaluation, including scores, violation counts, and module-level findings.

  • Organization-wide governance rollup: total scenarios, passing rate, critical violations, top violations by frequency, and compliance coverage per framework. Ideal for scheduled daily digests or executive dashboards.

  • Retrieves the ordered remediation steps for a specific policy violation on a scenario, with severity, estimated effort, and mapped compliance frameworks.

  • Retrieves the full results of a completed evaluation using its single-use result token.

  • Retrieves the latest governance results for a saved scenario, including its score, violations, per-module summary, and compliance status.

  • Evaluate one step's input and/or output against FlowBeacon runtime guardrails (PII, secrets, schema, prompt-injection, data-exfiltration, size). In Block mode the module stops the scenario when a guardrail fails; in Warn/Audit mode it returns the verdict so you can branch on it. Place this module right after (or before) the step you want to govern and map that step's data into Input/Output. FlowBeacon evaluates the data in flight and stores only a redacted verdict on its side; whatever you map into Input/Output is still written to your Make execution log like any other module's input.

  • Performs an arbitrary authorized API call.

  • Evaluate the current scenario against FlowBeacon's governance policies. The blueprint is sent inline — no pre-import required. Returns an evaluation ID, a single-use result token, and your remaining quota. Optionally save the scenario to your FlowBeacon workspace for history and trend tracking.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between FlowBeacon and Tally.

Get a scenario module graph
Retrieves the module-by-module governance breakdown (the module graph) for a saved scenario.
Action
Get an evaluation
Retrieves the status and per-scenario governance results of a submitted evaluation, including scores, violation counts, and module-level findings.
Action
Get organization summary
Organization-wide governance rollup: total scenarios, passing rate, critical violations, top violations by frequency, and compliance coverage per framework. Ideal for scheduled daily digests or executive dashboards.
Action
Get remediation steps
Retrieves the ordered remediation steps for a specific policy violation on a scenario, with severity, estimated effort, and mapped compliance frameworks.
Action
Get results by token
Retrieves the full results of a completed evaluation using its single-use result token.
Action
Get scenario results
Retrieves the latest governance results for a saved scenario, including its score, violations, per-module summary, and compliance status.
Action
Guard a step
Evaluate one step's input and/or output against FlowBeacon runtime guardrails (PII, secrets, schema, prompt-injection, data-exfiltration, size). In Block mode the module stops the scenario when a guardrail fails; in Warn/Audit mode it returns the verdict so you can branch on it. Place this module right after (or before) the step you want to govern and map that step's data into Input/Output. FlowBeacon evaluates the data in flight and stores only a redacted verdict on its side; whatever you map into Input/Output is still written to your Make execution log like any other module's input.
Action
List Fields Definitions
Lists all field definitions for the selected form.
Search
List policies
Lists the FlowBeacon governance policy catalog, returning each policy's code, title, category, severity, and mapped compliance frameworks.
Search
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.