@n8n/i18n 2.0.0-rc.2 → 2.0.0

package/dist/index.d.cts

@@ -2176,6 +2176,7 @@ declare const i18nInstance: vue_i18n0.I18n<{
     "resourceLocator.placeholder.searchOrCreate": string;
     "resourceLocator.placeholder.search": string;
     "resourceLocator.url.placeholder": string;
+    "resourceLocator.workflow.inactive.tooltip": string;
     "resourceMapper.autoMappingNotice": string;
     "resourceMapper.mappingMode.label": string;
     "resourceMapper.mappingMode.defineBelow.name": string;

package/dist/index.d.mts

@@ -2176,6 +2176,7 @@ declare const i18nInstance: vue_i18n0.I18n<{
     "resourceLocator.placeholder.searchOrCreate": string;
     "resourceLocator.placeholder.search": string;
     "resourceLocator.url.placeholder": string;
+    "resourceLocator.workflow.inactive.tooltip": string;
     "resourceMapper.autoMappingNotice": string;
     "resourceMapper.mappingMode.label": string;
     "resourceMapper.mappingMode.defineBelow.name": string;

package/dist/index.mjs

@@ -1307,7 +1307,7 @@ var en_default = {
 	"mainSidebar.workersView": "Workers",
 	"mainSidebar.whatsNew": "What’s New",
 	"mainSidebar.whatsNew.fullChangelog": "Full changelog",
-	"mcp.workflowNotEligable.description": "Only active workflows with one of the following trigger nodes can be accessible via MCP: {triggers}",
+	"mcp.workflowNotEligable.description": "Only published workflows with one of the following trigger nodes can be accessible via MCP: {triggers}",
 	"mcp.instanceLevelAccessDisabled.description": "Instance-level MCP access is disabled. Enable it to allow workflow-level access.",
 	"mcp.workflowDeactivated.title": "MCP Access Disabled",
 	"mcp.productionChecklist.title": "Enable MCP access",
@@ -2172,6 +2172,7 @@ var en_default = {
 	"resourceLocator.placeholder.searchOrCreate": "Search or create...",
 	"resourceLocator.placeholder.search": "Search...",
 	"resourceLocator.url.placeholder": "Enter URL...",
+	"resourceLocator.workflow.inactive.tooltip": "Must be published before using",
 	"resourceMapper.autoMappingNotice": "In this mode, make sure the incoming data fields are named the same as the {fieldWord} in {serviceName}. (Use an 'Edit Fields' node before this node to change them if required.)",
 	"resourceMapper.mappingMode.label": "Mapping Column Mode",
 	"resourceMapper.mappingMode.defineBelow.name": "Map Each Column Manually",
@@ -2582,10 +2583,10 @@ var en_default = {
 	"settings.usageAndPlan.callOut.link": "Unlock",
 	"settings.usageAndPlan.edition": "Edition",
 	"settings.usageAndPlan.error": "@:_reusableBaseText.error",
-	"settings.usageAndPlan.activeWorkflows": "Active workflows",
+	"settings.usageAndPlan.activeWorkflows": "Published workflows",
 	"settings.usageAndPlan.activeWorkflows.unlimited": "@:_reusableBaseText.unlimited",
 	"settings.usageAndPlan.activeWorkflows.count": "{count} of {limit}",
-	"settings.usageAndPlan.activeWorkflows.hint": "Active workflows with multiple triggers count multiple times",
+	"settings.usageAndPlan.activeWorkflows.hint": "Published workflows with multiple triggers count multiple times. Error and Sub-workflow triggers are excluded.",
 	"settings.usageAndPlan.button.activation": "Enter activation key",
 	"settings.usageAndPlan.button.plans": "View plans",
 	"settings.usageAndPlan.button.manage": "Manage plan",
@@ -2935,7 +2936,7 @@ var en_default = {
 	"nodeIssues.input.missing": "No node connected to required input \"{inputName}\"",
 	"ndv.trigger.moreInfo": "More info",
 	"ndv.trigger.copiedTestUrl": "Test URL copied to clipboard",
-	"ndv.trigger.webhookBasedNode.executionsHelp.inactive": "<b>While building your workflow</b>, click the 'execute step' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.<br /> <br /> <b>Once you're happy with your workflow</b>, <a data-key=\"activate\">activate</a> it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor.",
+	"ndv.trigger.webhookBasedNode.executionsHelp.inactive": "<b>While building your workflow</b>, click the 'execute step' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.<br /> <br /> <b>Once you're happy with your workflow</b>, publish it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor.",
 	"ndv.trigger.webhookBasedNode.executionsHelp.active": "<b>While building your workflow</b>, click the 'execute step' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.<br /> <br /> <b>Your workflow will also execute automatically</b>, since it's activated. Every time there’s a matching event in {service}, this node will trigger an execution. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor. ",
 	"ndv.trigger.webhookNode.listening": "Listening for test event",
 	"ndv.trigger.chatTrigger.openChat": "Open Chat Window",
@@ -2945,14 +2946,14 @@ var en_default = {
 	"ndv.trigger.webhookBasedNode.serviceHint": "Go to {service} and create an event",
 	"ndv.trigger.webhookBasedNode.chatTrigger.serviceHint": "Send a message in the chat",
 	"ndv.trigger.webhookBasedNode.formTrigger.serviceHint": "Submit the test form that just opened in a new tab",
-	"ndv.trigger.webhookBasedNode.activationHint.inactive": "Once you’ve finished building your workflow, <a data-key=\"activate\">activate it</a> to have it also listen continuously (you just won’t see those executions here).",
+	"ndv.trigger.webhookBasedNode.activationHint.inactive": "Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).",
 	"ndv.trigger.webhookBasedNode.activationHint.active": "This node will also trigger automatically on new {service} events (but those executions won’t show up here).",
-	"ndv.trigger.pollingNode.activationHint.inactive": "Once you’ve finished building your workflow, <a data-key=\"activate\">activate it</a> to have it also check for events regularly (you just won’t see those executions here).",
+	"ndv.trigger.pollingNode.activationHint.inactive": "Once you’ve finished building your workflow, publish it to have it also check for events regularly (you just won’t see those executions here).",
 	"ndv.trigger.pollingNode.activationHint.active": "This node will also trigger automatically on new {service} events (but those executions won’t show up here).",
 	"ndv.trigger.executionsHint.question": "When will this node trigger my flow?",
 	"ndv.trigger.pollingNode.fetchingEvent": "Fetching event",
 	"ndv.trigger.pollingNode.fetchingHint": "This node is looking for an event in {name} that is similar to the one you defined",
-	"ndv.trigger.pollingNode.executionsHelp.inactive": "<b>While building your workflow</b>, click the 'fetch' button to fetch a single mock event. It will show up in this editor.<br /><br /><b>Once you're happy with your workflow</b>, <a data-key=\"activate\">activate</a> it. Then n8n will regularly check {service} for new events, and execute this workflow if it finds any. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor.",
+	"ndv.trigger.pollingNode.executionsHelp.inactive": "<b>While building your workflow</b>, click the 'fetch' button to fetch a single mock event. It will show up in this editor.<br /><br /><b>Once you're happy with your workflow</b>, publish it. Then n8n will regularly check {service} for new events, and execute this workflow if it finds any. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor.",
 	"ndv.trigger.pollingNode.executionsHelp.active": "<b>While building your workflow</b>, click the 'fetch' button to fetch a single mock event. It will show up in this editor.<br /><br /><b>Your workflow will also execute automatically</b>, since it's activated. n8n will regularly check {app_name} for new events, and execute this workflow if it finds any. These executions will show up in the <a data-key=\"executions\">executions list</a>, but not in the editor.",
 	"ndv.trigger.webhookBasedNode.action": "Pull in events from {name}",
 	"ndv.search.placeholder.output": "Search output",
@@ -2997,7 +2998,7 @@ var en_default = {
 	"workflowActivator.inactive": "Inactive",
 	"workflowActivator.showError.title": "Workflow could not be {newStateName}",
 	"workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.message": "Please resolve outstanding issues before publishing",
-	"workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.title": "Problem publishing workflow ({count} node has issues) | Problem publishing workflow ({count} nodes have issues)",
+	"workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.title": "{count} node has issues, fix before publishing: | {count} nodes have issues, fix before publishing:",
 	"workflowActivator.showMessage.activeChangedWorkflowIdUndefined.message": "Please save it before activating",
 	"workflowActivator.showMessage.activeChangedWorkflowIdUndefined.title": "Problem activating workflow",
 	"workflowActivator.showMessage.displayActivationError.message.catchBlock": "Sorry there was a problem requesting the error",