Inspect an automation workspace
Understand connections, endpoints, workflows, and runs before changing a client integration.
Automations organizes a client's integration connections, inbound endpoints, workflows, and execution history into workspaces. Inspect the workspace first so you understand which connection and workflow own the behavior you are investigating.
This guide is for Forge platform operators with workspace access. Workspace detail administration currently requires super-admin access. If you are a customer without that permission, give your Forge operator the business name and the automation outcome you need checked.
Open the intended workspace
- Select the correct account.
- Open Automations and its workspace directory.
- Choose the intended Northgate ESD Packaging workspace.
- Read Overview, including status and configured integration and workflow counts.
- Confirm the workspace name and slug match the integration you intend to inspect.
Automation routes live under /workspaces. A saved workspace link is therefore normal even though the navigation calls the module Automations.
An account is the business context; a workspace groups integration work. Do not confuse a project used for content assets with an automation workspace used for execution.
Follow the integration path
| Tab | What to inspect |
|---|---|
| Connections | The available integrations and their validation status |
| Endpoints | Inbound addresses, source, status, and attached workflows |
| Workflows | Workflow names, templates, status, and run counts |
| Tools | Attached connector actions and their state |
| Runs | Individual workflow executions |
| Audit | Recorded actions and results |
| Recovery | Failed validations and recent errors needing attention |
| Artifacts | Outputs or supporting content associated with the workspace |
For Northgate, trace a demo inquiry from its inbound endpoint to the workflow intended to handle it. The endpoint identifies where data arrives; the workflow identifies what should happen after arrival; a run records an execution. An endpoint existing does not establish that an event arrived or that processing succeeded.
Understand a draft workspace
A draft workspace has not completed activation. The draft notice directs the operator to add and validate the The Viking Stack (TVS) integration on Connections. Read the validation result before expecting the workspace to become active.
Creating additional workflows does not fix an invalid connection. Establish the correct connection first so the workflow's destination is clear.
The directory's Create Workspace action is for authorized operators creating an intentional new integration container. Do not create another workspace merely because the original one is empty or unhealthy; inspect its account, connection, and setup first.
Review workflow setup before use
In Workflows, read the available template's description and connection requirement. When creating an authorized workflow, inspect its name, selected validated TVS connection, and any message content before choosing Create Workflow.
A created workflow may display an inbound address and authentication material needed by the sending system. Transfer that material through the approved secure setup process. It does not belong in a customer-facing screenshot or a project brief.
Creation confirms configuration, not a successful delivery. Use a deliberately identified test event through the approved integration setup, then inspect its run and destination result. Do not send a real customer message merely to see whether a workflow exists.
Troubleshoot in dependency order
Start with connection validation, then inspect the endpoint, workflow, and run. Recovery helps locate invalid connections and recorded errors. Its empty state means no recovery actions are currently listed; it is not a guarantee that every external system is healthy.
If no runs exist, check whether the sending system actually submitted an event to the intended endpoint. If runs failed, move to the run detail rather than recreating the workflow. Preserve the workspace, run identifier, and visible error in the handoff.