End-to-end chain: Service → Sub-service → Meta → DMF Object → MCP Tool(s) → n8n Workflow(s). Aligned to Configuration Steps 01–05.
| Client | Main Service | Sub Service | Sub Service Meta | DMF Object | MCP Tool | n8n Workflow / Config |
|---|
Data source: stc_development_v1 (main_service, sub_service, sub_service_meta, dm_object_new, n8n_workflow_master, n8n_workflow_configs). This view uses mock data until backend API is connected.
The n8n Workflow / Config column labels (e.g. "Config 1", "Config 19") are the id and name from the config database. Full details are in stc_development_v1 in these tables:
n8n_workflow_master — workflow-level (one per n8n workflow):
| Column | Description |
|---|---|
id | PK |
workflow_ref | n8n workflow reference (e.g. ejNXT7tb8O98pD8Q) |
name | e.g. TMS E2E, SCM E2E |
status | active / inactive |
trigger_webhook | Webhook URL for trigger |
n8n_workflow_configs — per-config details (Config 1, Config 2, …); sub_service_meta.workflow_config_id and service_workflow_executions.workflow_config_id point here:
| Column | Description |
|---|---|
id | PK (this is "Config 1", "Config 2", etc.) |
workflow_id | FK → n8n_workflow_master.id |
workflow_id_2 | Secondary workflow reference |
n8n_workflow_id | Links to n8n_workflow.id |
operation_template_code | e.g. OPT-25-0015 |
name | Display name (Order Creation, Pickup, Load, booking, si, vgm, etc.) |
operation_template_module | tms / scm |
dmf_template_object | DMF object code (e.g. OBJ-25-0068, OBJ-25-0042) |
workflow_execution_type | upload / ftp / api / pub_sub |
dependency | yes / no |
dependency_config_id | FK → n8n_workflow_configs.id (previous step in chain) |
To see details for a specific config (e.g. Config 19): query SELECT * FROM n8n_workflow_configs WHERE id = 19 and join n8n_workflow_master on workflow_id for the workflow name and webhook.
ID relationship map (for maintenance)
These IDs link the chain. Use "Show IDs" in the table above to see them per row.
| ID | Table | Referenced by / Used in |
|---|---|---|
main_service.id | main_service | sub_service.main_service_id, sub_service_meta.main_service_id, dm_object_new.main_service |
sub_service.id | sub_service | sub_service_meta.sub_service_id, dm_object_new.sub_service; service_workflow_executions.service_id when service_type='sub' |
sub_service_meta.id | sub_service_meta | dm_object_new.sub_service_meta; service_workflow_executions.service_id when service_type='sub_meta' |
n8n_workflow_configs.id | n8n_workflow_configs | sub_service.workflow_config_id, sub_service_meta.workflow_config_id, service_workflow_executions.workflow_config_id, workflow_config_nodes.workflow_config_id |
dm_object_new.id / code | dm_object_new | n8n_workflow_configs.dmf_template_object stores object code (e.g. OBJ-25-0042) |
service_workflow_executions.service_id is polymorphic: it points to main_service.id, sub_service.id, or sub_service_meta.id depending on service_type (main / sub / sub_meta). Always join using service_type to know which table to join.