Cadres IT Operations & Infrastructure
Products Architecture Docs Blog
Sheet SYN-12 Rev 2026.08
Start Trial

Sheet SYN-12 · Network Operations Manual

Governed Actions & Journeys

The action catalog with risk classes, journeys with schedules and scope, the approval inbox, and signed webhook exports.

Audience: Operators, approvers, and automation owners Focus: Changes that wait for approval and keep a record

Scope

This guide covers how Synapse makes changes: the action catalog, journeys, the approval inbox, and signed webhook exports to downstream systems.

The action catalog

The catalog lists every action with a risk class (read, external-write, or device-write) and the permission it needs. Examples: reboot a device, sync an integration now, evaluate a compliance policy, generate a CSV report, change device configuration through the collector, and push a signed export to a webhook endpoint.

Each action’s parameters appear as a form built from the action’s schema. The execute button appears only for an operator who holds both the general execute permission and the action’s own permission. The platform enforces the same rule.

Journeys

A journey is a named sequence of catalog actions:

  • Steps pick actions and set their parameters. A step can repeat for each device or each site in the journey’s scope, so “reboot every device at this site” is one step.
  • Schedules run daily, weekly, or monthly, including forms such as “last Friday of the month”.
  • Scope uses the same organization, label, or site selector as compliance policies.
  • Synapse validates the whole journey when you save it. A bad action reference or a scope that matches nothing is caught then, not at run time.

You cannot delete a journey that has run history. Disable it instead. Its runs stay available as audit history.

Approval and run records

A run that contains a device-write step, or belongs to a journey that requires approval, waits in the approval inbox. Approving it clears the gate. Executing it is a separate step that needs a separate permission.

Each run has a step timeline: status, risk class, error text, and results for every step. For a configuration change, the run detail shows the collector’s progress live and, when it finishes, the unified diff of the configuration before and after.

Signed webhook exports

Downstream systems, such as IP address management, configuration databases, or business intelligence tools, register an HTTPS endpoint. They subscribe to export types such as inventory, compliance, and scores. Synapse signs every delivery so the receiver can verify where it came from.

  • The signing secret is shown once, when you create the endpoint. You can regenerate it.
  • A test send pushes a signed delivery through the same path as a live one.
  • Delivery history records every attempt.
  • An endpoint with delivery history can be disabled but not deleted, because its deliveries are audit evidence.