diff --git a/packages/@n8n/nodes-langchain/nodes/mcp/McpTrigger/McpTrigger.node.ts b/packages/@n8n/nodes-langchain/nodes/mcp/McpTrigger/McpTrigger.node.ts index 360e4d26456..35a67d9375f 100644 --- a/packages/@n8n/nodes-langchain/nodes/mcp/McpTrigger/McpTrigger.node.ts +++ b/packages/@n8n/nodes-langchain/nodes/mcp/McpTrigger/McpTrigger.node.ts @@ -46,7 +46,7 @@ export class McpTrigger extends Node { header: 'Listen for MCP events', executionsHelp: { inactive: - "This trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'execute step' button, then make an MCP request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Activate the workflow, then make requests to the production URL. These executions will show up in the executions list, but not the editor.", + "This trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'execute step' button, then make an MCP request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Publish the workflow, then make requests to the production URL. These executions will show up in the executions list, but not the editor.", active: "This trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'execute step' button, then make an MCP request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Since your workflow is activated, you can make requests to the production URL. These executions will show up in the executions list, but not the editor.", }, diff --git a/packages/frontend/@n8n/i18n/src/locales/en.json b/packages/frontend/@n8n/i18n/src/locales/en.json index fca61e7dee5..e94a15b9386 100644 --- a/packages/frontend/@n8n/i18n/src/locales/en.json +++ b/packages/frontend/@n8n/i18n/src/locales/en.json @@ -2948,7 +2948,7 @@ "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": "While building your workflow, 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.

Once you're happy with your workflow, activate it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "ndv.trigger.webhookBasedNode.executionsHelp.inactive": "While building your workflow, 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.

Once you're happy with your workflow, publish it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the executions list, but not in the editor.", "ndv.trigger.webhookBasedNode.executionsHelp.active": "While building your workflow, 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.

Your workflow will also execute automatically, 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 executions list, but not in the editor. ", "ndv.trigger.webhookNode.listening": "Listening for test event", "ndv.trigger.chatTrigger.openChat": "Open Chat Window", @@ -2958,14 +2958,14 @@ "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, activate it 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, activate it 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": "While building your workflow, click the 'fetch' button to fetch a single mock event. It will show up in this editor.

Once you're happy with your workflow, activate 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 executions list, but not in the editor.", + "ndv.trigger.pollingNode.executionsHelp.inactive": "While building your workflow, click the 'fetch' button to fetch a single mock event. It will show up in this editor.

Once you're happy with your workflow, 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 executions list, but not in the editor.", "ndv.trigger.pollingNode.executionsHelp.active": "While building your workflow, click the 'fetch' button to fetch a single mock event. It will show up in this editor.

Your workflow will also execute automatically, 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 executions list, but not in the editor.", "ndv.trigger.webhookBasedNode.action": "Pull in events from {name}", "ndv.search.placeholder.output": "Search output", diff --git a/packages/frontend/editor-ui/src/app/constants/workflows.ts b/packages/frontend/editor-ui/src/app/constants/workflows.ts index bec51a68bd4..0fa6a2877d5 100644 --- a/packages/frontend/editor-ui/src/app/constants/workflows.ts +++ b/packages/frontend/editor-ui/src/app/constants/workflows.ts @@ -12,4 +12,5 @@ export const WORKFLOWS_DRAFT_PUBLISH_ENABLED_FLAG = 'WORKFLOWS_DRAFT_PUBLISH_ENA // TODO: We need to do a proper cleanup of the old functionality (non-draft-publish mode) // and then drop this constant // make sure to drop the activeChange and activeChangeCurrent external hooks +// double check that onWorkflowActivate is never called in NodeDetailsViewV2.vue and NodeDetailsView.vue and clean it up export const IS_DRAFT_PUBLISH_ENABLED = true; diff --git a/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsView.vue b/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsView.vue index ab0955786f3..2bc60b1bb14 100644 --- a/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsView.vue +++ b/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsView.vue @@ -20,7 +20,6 @@ import { START_NODE_TYPE, STICKY_NODE_TYPE, } from '@/app/constants'; -import { useWorkflowActivate } from '@/app/composables/useWorkflowActivate'; import type { DataPinningDiscoveryEvent } from '@/app/event-bus'; import { dataPinningEventBus } from '@/app/event-bus'; import { ndvEventBus } from '@/features/ndv/shared/ndv.eventBus'; @@ -37,7 +36,7 @@ import { useI18n } from '@n8n/i18n'; import { storeToRefs } from 'pinia'; import { useStyles } from '@/app/composables/useStyles'; import { useTelemetryContext } from '@/app/composables/useTelemetryContext'; - +import { nodeViewEventBus } from '@/app/event-bus'; import { ElDialog } from 'element-plus'; import { N8nIcon, N8nText, N8nTooltip } from '@n8n/design-system'; const emit = defineEmits<{ @@ -70,7 +69,6 @@ const externalHooks = useExternalHooks(); const nodeHelpers = useNodeHelpers(); const { activeNode } = storeToRefs(ndvStore); const pinnedData = usePinnedData(activeNode); -const workflowActivate = useWorkflowActivate(); const nodeTypesStore = useNodeTypesStore(); const workflowsStore = useWorkflowsStore(); const deviceSupport = useDeviceSupport(); @@ -373,9 +371,7 @@ const onInputTableMounted = (e: { avgRowHeight: number }) => { const onWorkflowActivate = () => { ndvStore.unsetActiveNodeName(); - setTimeout(() => { - void workflowActivate.activateCurrentWorkflow('ndv'); - }, 1000); + nodeViewEventBus.emit('publishWorkflow'); }; const onOutputItemHover = (e: { itemIndex: number; outputIndex: number } | null) => { diff --git a/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsViewV2.vue b/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsViewV2.vue index 523fa965d0c..ddb67d3866d 100644 --- a/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsViewV2.vue +++ b/packages/frontend/editor-ui/src/features/ndv/shared/views/NodeDetailsViewV2.vue @@ -18,7 +18,6 @@ import { useNodeHelpers } from '@/app/composables/useNodeHelpers'; import { usePinnedData } from '@/app/composables/usePinnedData'; import { useStyles } from '@/app/composables/useStyles'; import { useTelemetry } from '@/app/composables/useTelemetry'; -import { useWorkflowActivate } from '@/app/composables/useWorkflowActivate'; import { APP_MODALS_ELEMENT_ID, EXECUTABLE_TRIGGER_NODE_TYPES, @@ -41,7 +40,7 @@ import OutputPanel from '../../panel/components/OutputPanel.vue'; import PanelDragButtonV2 from '../../panel/components/PanelDragButtonV2.vue'; import TriggerPanel from '../../panel/components/TriggerPanel.vue'; import { useTelemetryContext } from '@/app/composables/useTelemetryContext'; - +import { nodeViewEventBus } from '@/app/event-bus'; import { N8nResizeWrapper } from '@n8n/design-system'; import NDVFloatingNodes from '@/features/ndv/panel/components/NDVFloatingNodes.vue'; const emit = defineEmits<{ @@ -70,7 +69,6 @@ const externalHooks = useExternalHooks(); const nodeHelpers = useNodeHelpers(); const { activeNode } = storeToRefs(ndvStore); const pinnedData = usePinnedData(activeNode); -const workflowActivate = useWorkflowActivate(); const nodeTypesStore = useNodeTypesStore(); const uiStore = useUIStore(); const workflowsStore = useWorkflowsStore(); @@ -384,9 +382,7 @@ const onInputTableMounted = (e: { avgRowHeight: number }) => { const onWorkflowActivate = () => { ndvStore.unsetActiveNodeName(); - setTimeout(() => { - void workflowActivate.activateCurrentWorkflow('ndv'); - }, 1000); + nodeViewEventBus.emit('publishWorkflow'); }; const onOutputItemHover = (e: { itemIndex: number; outputIndex: number } | null) => { diff --git a/packages/nodes-base/nodes/Cron/Cron.node.ts b/packages/nodes-base/nodes/Cron/Cron.node.ts index b2fa21f2596..f6bd9a4da3e 100644 --- a/packages/nodes-base/nodes/Cron/Cron.node.ts +++ b/packages/nodes-base/nodes/Cron/Cron.node.ts @@ -29,7 +29,7 @@ export class Cron implements INodeType { properties: [ { displayName: - 'This workflow will run on the schedule you define here once you activate it.

For testing, you can also trigger it manually: by going back to the canvas and clicking \'execute workflow\'', + "This workflow will run on the schedule you define here once you publish it.

For testing, you can also trigger it manually: by going back to the canvas and clicking 'execute workflow'", name: 'notice', type: 'notice', default: '', diff --git a/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts b/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts index 76cc1e34f05..b79bc741dfb 100644 --- a/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts +++ b/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts @@ -73,12 +73,12 @@ const versionDescription: INodeTypeDescription = { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, inputs: [], diff --git a/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts b/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts index 044e6358f97..c0f1ec2b76a 100644 --- a/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts +++ b/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts @@ -46,12 +46,12 @@ const versionDescription: INodeTypeDescription = { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, usableAsTool: true, inputs: [], diff --git a/packages/nodes-base/nodes/Form/common.descriptions.ts b/packages/nodes-base/nodes/Form/common.descriptions.ts index b2bac9fe4ab..b8ede9050e9 100644 --- a/packages/nodes-base/nodes/Form/common.descriptions.ts +++ b/packages/nodes-base/nodes/Form/common.descriptions.ts @@ -532,15 +532,15 @@ export const formTriggerPanel = { header: 'Pull in a test form submission', executionsHelp: { inactive: - "Form Trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'Execute step' button, then fill out the test form that opens in a popup tab. The executions will show up in the editor.

Use production mode to run your workflow automatically. Activate the workflow, then make requests to the production URL. Then every time there's a form submission via the Production Form URL, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "Form Trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'Execute step' button, then fill out the test form that opens in a popup tab. The executions will show up in the editor.

Use production mode to run your workflow automatically. Publish the workflow, then make requests to the production URL. Then every time there's a form submission via the Production Form URL, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "Form Trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'Execute step' button, then fill out the test form that opens in a popup tab. The executions will show up in the editor.

Use production mode to run your workflow automatically. Activate the workflow, then make requests to the production URL. Then every time there's a form submission via the Production Form URL, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "Form Trigger has two modes: test and production.

Use test mode while you build your workflow. Click the 'Execute step' button, then fill out the test form that opens in a popup tab. The executions will show up in the editor.

Use production mode to run your workflow automatically. Publish the workflow, then make requests to the production URL. Then every time there's a form submission via the Production Form URL, the workflow will execute. These executions will show up in the executions list, but not in the editor.", }, activationHint: { active: "This node will also trigger automatically on new form submissions (but those executions won't show up here).", inactive: - 'Activate this workflow to have it also run automatically for new form submissions created via the Production URL.', + 'Publish this workflow to have it also run automatically for new form submissions created via the Production URL.', }, }; diff --git a/packages/nodes-base/nodes/Interval/Interval.node.ts b/packages/nodes-base/nodes/Interval/Interval.node.ts index 5d040cd6ad0..202d2453377 100644 --- a/packages/nodes-base/nodes/Interval/Interval.node.ts +++ b/packages/nodes-base/nodes/Interval/Interval.node.ts @@ -28,7 +28,7 @@ export class Interval implements INodeType { properties: [ { displayName: - 'This workflow will run on the schedule you define here once you activate it.

For testing, you can also trigger it manually: by going back to the canvas and clicking \'execute workflow\'', + "This workflow will run on the schedule you define here once you publish it.

For testing, you can also trigger it manually: by going back to the canvas and clicking 'execute workflow'", name: 'notice', type: 'notice', default: '', diff --git a/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts b/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts index 19c13b7fe69..29bb1b29338 100644 --- a/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts +++ b/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts @@ -28,12 +28,12 @@ export class LocalFileTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, inputs: [], outputs: [NodeConnectionTypes.Main], diff --git a/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts b/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts index 0bddb4ef90b..d586a183d52 100644 --- a/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts +++ b/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts @@ -34,12 +34,12 @@ export class MqttTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, inputs: [], outputs: [NodeConnectionTypes.Main], diff --git a/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts b/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts index 97f60386b55..2df146257c8 100644 --- a/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts +++ b/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts @@ -32,12 +32,12 @@ export class PostgresTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you've finished building your workflow, activate it to have it also listen continuously (you just won't see those executions here).", + "Once you've finished building your workflow, publish it to have it also listen continuously (you just won't see those executions here).", }, inputs: [], outputs: [NodeConnectionTypes.Main], diff --git a/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts b/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts index dfa273197ad..390333c3cbe 100644 --- a/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts +++ b/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts @@ -29,12 +29,12 @@ export class RabbitMQTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, inputs: [], outputs: [NodeConnectionTypes.Main], diff --git a/packages/nodes-base/nodes/Schedule/ScheduleTrigger.node.ts b/packages/nodes-base/nodes/Schedule/ScheduleTrigger.node.ts index 7d0963a425f..e7bde427729 100644 --- a/packages/nodes-base/nodes/Schedule/ScheduleTrigger.node.ts +++ b/packages/nodes-base/nodes/Schedule/ScheduleTrigger.node.ts @@ -38,7 +38,7 @@ export class ScheduleTrigger implements INodeType { properties: [ { displayName: - 'This workflow will run on the schedule you define here once you activate it.

For testing, you can also trigger it manually: by going back to the canvas and clicking \'execute workflow\'', + "This workflow will run on the schedule you define here once you publish it.

For testing, you can also trigger it manually: by going back to the canvas and clicking 'execute workflow'", name: 'notice', type: 'notice', default: '', diff --git a/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts b/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts index 8d8b20ca284..2f77124408f 100644 --- a/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts +++ b/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts @@ -27,12 +27,12 @@ export class SseTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'execute step' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'execute step' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, publish it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: "While building your workflow, click the 'execute step' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: - "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", + 'Once you’ve finished building your workflow, publish it to have it also listen continuously (you just won’t see those executions here).', }, inputs: [], outputs: [NodeConnectionTypes.Main], diff --git a/packages/nodes-base/nodes/Webhook/Webhook.node.ts b/packages/nodes-base/nodes/Webhook/Webhook.node.ts index 31679ec0834..72d11c85363 100644 --- a/packages/nodes-base/nodes/Webhook/Webhook.node.ts +++ b/packages/nodes-base/nodes/Webhook/Webhook.node.ts @@ -60,7 +60,7 @@ export class Webhook extends Node { header: '', executionsHelp: { inactive: - 'Webhooks have two modes: test and production.

Use test mode while you build your workflow. Click the \'listen\' button, then make a request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Activate the workflow, then make requests to the production URL. These executions will show up in the executions list, but not in the editor.', + "Webhooks have two modes: test and production.

Use test mode while you build your workflow. Click the 'listen' button, then make a request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Publish the workflow, then make requests to the production URL. These executions will show up in the executions list, but not in the editor.", active: 'Webhooks have two modes: test and production.

Use test mode while you build your workflow. Click the \'listen\' button, then make a request to the test URL. The executions will show up in the editor.

Use production mode to run your workflow automatically. Since the workflow is activated, you can make requests to the production URL. These executions will show up in the executions list, but not in the editor.', },