@n8n/i18n 2.0.0-rc.2 → 2.0.0-rc.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.cjs CHANGED
@@ -1307,7 +1307,7 @@ var en_default = {
1307
1307
  "mainSidebar.workersView": "Workers",
1308
1308
  "mainSidebar.whatsNew": "What’s New",
1309
1309
  "mainSidebar.whatsNew.fullChangelog": "Full changelog",
1310
- "mcp.workflowNotEligable.description": "Only active workflows with one of the following trigger nodes can be accessible via MCP: {triggers}",
1310
+ "mcp.workflowNotEligable.description": "Only published workflows with one of the following trigger nodes can be accessible via MCP: {triggers}",
1311
1311
  "mcp.instanceLevelAccessDisabled.description": "Instance-level MCP access is disabled. Enable it to allow workflow-level access.",
1312
1312
  "mcp.workflowDeactivated.title": "MCP Access Disabled",
1313
1313
  "mcp.productionChecklist.title": "Enable MCP access",
@@ -2172,6 +2172,7 @@ var en_default = {
2172
2172
  "resourceLocator.placeholder.searchOrCreate": "Search or create...",
2173
2173
  "resourceLocator.placeholder.search": "Search...",
2174
2174
  "resourceLocator.url.placeholder": "Enter URL...",
2175
+ "resourceLocator.workflow.inactive.tooltip": "Must be published before using",
2175
2176
  "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.)",
2176
2177
  "resourceMapper.mappingMode.label": "Mapping Column Mode",
2177
2178
  "resourceMapper.mappingMode.defineBelow.name": "Map Each Column Manually",
@@ -2582,10 +2583,11 @@ var en_default = {
2582
2583
  "settings.usageAndPlan.callOut.link": "Unlock",
2583
2584
  "settings.usageAndPlan.edition": "Edition",
2584
2585
  "settings.usageAndPlan.error": "@:_reusableBaseText.error",
2585
- "settings.usageAndPlan.activeWorkflows": "Active workflows",
2586
+ "settings.usageAndPlan.activeWorkflows": "Published workflows",
2586
2587
  "settings.usageAndPlan.activeWorkflows.unlimited": "@:_reusableBaseText.unlimited",
2587
2588
  "settings.usageAndPlan.activeWorkflows.count": "{count} of {limit}",
2588
- "settings.usageAndPlan.activeWorkflows.hint": "Active workflows with multiple triggers count multiple times",
2589
+ "settings.usageAndPlan.activeWorkflows.hint": "Published workflows with multiple triggers count multiple times",
2590
+ "settings.usageAndPlan.activeWorkflows.overcountWarning": "You may notice this number go up because workflows with sub-workflow and error-workflows triggers are now published. However, you will not be billed for them.",
2589
2591
  "settings.usageAndPlan.button.activation": "Enter activation key",
2590
2592
  "settings.usageAndPlan.button.plans": "View plans",
2591
2593
  "settings.usageAndPlan.button.manage": "Manage plan",
@@ -2935,7 +2937,7 @@ var en_default = {
2935
2937
  "nodeIssues.input.missing": "No node connected to required input \"{inputName}\"",
2936
2938
  "ndv.trigger.moreInfo": "More info",
2937
2939
  "ndv.trigger.copiedTestUrl": "Test URL copied to clipboard",
2938
- "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.",
2940
+ "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.",
2939
2941
  "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. ",
2940
2942
  "ndv.trigger.webhookNode.listening": "Listening for test event",
2941
2943
  "ndv.trigger.chatTrigger.openChat": "Open Chat Window",
@@ -2945,14 +2947,14 @@ var en_default = {
2945
2947
  "ndv.trigger.webhookBasedNode.serviceHint": "Go to {service} and create an event",
2946
2948
  "ndv.trigger.webhookBasedNode.chatTrigger.serviceHint": "Send a message in the chat",
2947
2949
  "ndv.trigger.webhookBasedNode.formTrigger.serviceHint": "Submit the test form that just opened in a new tab",
2948
- "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).",
2950
+ "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).",
2949
2951
  "ndv.trigger.webhookBasedNode.activationHint.active": "This node will also trigger automatically on new {service} events (but those executions won’t show up here).",
2950
- "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).",
2952
+ "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).",
2951
2953
  "ndv.trigger.pollingNode.activationHint.active": "This node will also trigger automatically on new {service} events (but those executions won’t show up here).",
2952
2954
  "ndv.trigger.executionsHint.question": "When will this node trigger my flow?",
2953
2955
  "ndv.trigger.pollingNode.fetchingEvent": "Fetching event",
2954
2956
  "ndv.trigger.pollingNode.fetchingHint": "This node is looking for an event in {name} that is similar to the one you defined",
2955
- "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.",
2957
+ "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.",
2956
2958
  "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.",
2957
2959
  "ndv.trigger.webhookBasedNode.action": "Pull in events from {name}",
2958
2960
  "ndv.search.placeholder.output": "Search output",
@@ -2997,7 +2999,7 @@ var en_default = {
2997
2999
  "workflowActivator.inactive": "Inactive",
2998
3000
  "workflowActivator.showError.title": "Workflow could not be {newStateName}",
2999
3001
  "workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.message": "Please resolve outstanding issues before publishing",
3000
- "workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.title": "Problem publishing workflow ({count} node has issues) | Problem publishing workflow ({count} nodes have issues)",
3002
+ "workflowActivator.showMessage.activeChangedNodesIssuesExistTrue.title": "{count} node has issues, fix before publishing: | {count} nodes have issues, fix before publishing:",
3001
3003
  "workflowActivator.showMessage.activeChangedWorkflowIdUndefined.message": "Please save it before activating",
3002
3004
  "workflowActivator.showMessage.activeChangedWorkflowIdUndefined.title": "Problem activating workflow",
3003
3005
  "workflowActivator.showMessage.displayActivationError.message.catchBlock": "Sorry there was a problem requesting the error",