Skip to main content
Automations turn repeatable instructions into operational work. They use workspace context, connected sources, pages, and skills to prepare analysis or next steps on a schedule or in response to an event. An Automation is owned by one Space. Its Instructions can draw on reusable Skills as reference instructions. Flowglad does not run a Skill’s supporting scripts, so put work that needs to run in the Automation’s own code. A Skill does not schedule itself, and an Automation run does not automatically create an assigned Task.

An Automation Can

  • Read from connected systems and source files
  • Combine source data with workspace context
  • Draft analysis, updates, or proposed actions
  • Record the run and its supporting evidence

Reviewable Actions

When an automation would affect another system or produce a client-facing output, it should produce a proposal or reviewable result first. A reviewer can inspect the rationale, evidence, and intended action before approving it.

Runs

Each run should make its progress and outcome understandable. Runs provide the context needed to distinguish a successful action, a failed attempt, a pending review, and a result that needs follow-up.

Create a New Automation

Automations belong to one Space. In an external MCP client, describe the repeatable work and the Space where it belongs. The client uses automations.create to create the Automation and its initial revision. Use automations.update to create a later revision and explicitly select or activate the intended revision. Publishing a referenced Skill never creates, revises, or activates an Automation automatically.

Configure Triggers

When asking your MCP client to create or revise an Automation, specify when it should run. Available choices include Schedule, File Upload, and Connection events supported by the Space. For scheduled work, specify the intended cadence, time, and timezone.

Add Instructions and Connections

Describe what the Automation should do and which connected systems it should use. Before creating it, open the target Space → Connections and confirm that every required Connection is available there. If one is missing, configure it from the organization menu → Connectors, expose it to the Space, and then ask your MCP client to create or revise the Automation.

Save the Automation

Review the proposed behavior, triggers, inputs, code, and Connections before allowing the MCP client to call automations.create or automations.update. Activation is explicit. Saving or publishing a Skill does not create a Task or mutate an Automation.

Run and Inspect an Automation

Open the Automation. Overview shows its configuration; Runs shows past and current runs. Select Run now for a manual run when the action is available, review the confirmation, and then open the run to inspect its activity and result. Use the Space-level Automations → Runs view to review runs across that Space.

Who Can Run an Automation

A manual run or rerun requires the invoking person’s Run Automations permission (AutomationsRun) in the owner Space. That permission admits the request; it does not grant the Automation access to the caller’s other Spaces or Connections. Once admitted, an enabled Automation runs with service authority limited to its owner Space. Its creator’s later role or membership changes do not stop it. The run and audit history retain the invoking person as the cause of a manual run. Schedules and external events can start an enabled Automation without a person invoking it. A trusted first-party Page event records its authenticated person as the cause. Scheduled occurrences, external webhooks, and Connector events record Flowglad System as the cause; a sender’s email or provider ID does not become a Flowglad member identity. Retries preserve the original cause.

Current Space Access and Revocation

Each run uses the active Automation revision and the resources and Connections currently available to its owner Space. A declared resource or Connection exposed to that Space after activation can become usable on a later run. Removing its exposure, revoking a Connection, disabling the Automation, or deleting its owner Space prevents affected future access or execution. Resources that belong only to other Spaces do not become available. Administrators can revoke access by changing Space exposure, Connection access, or Automation state without changing the creator. A run’s service authority does not approve its proposed actions. Commands must be declared and bound to resources visible in the owner Space, and actions that require approval wait for an independently authorized reviewer or an applicable Automation approval policy. Tool calls use current verified supplier pricing, including for Automations pinned to an earlier tool revision. Flowglad checks the fresh maximum against available credits and any applicable spend cap. Postpaid tools have no maximum and are charged the verified supplier amount after the run. See Tools. Each accepted tool run saves its quote for billing.

Edit or Delete an Automation

Use automations.get and automations.list_revisions to inspect the current definition and history. Use automations.update to publish a revised definition and explicitly activate the intended revision. Historical definitions and runs remain readable but are not themselves executable unless selected as the active valid revision. To delete an Automation, open its More actions menu, select Delete, and confirm. Deleting it stops all future runs.