DOC-1114: Update Manual Trigger node to critical tier template (#2484)

This commit is contained in:
Kate Mueller 2024-09-23 13:01:32 -04:00 committed by GitHub
parent df23d9359d
commit 5d8311e12f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 39 additions and 16 deletions

View File

@ -1,14 +1,32 @@
---
#https://www.notion.so/n8n/Frontmatter-432c2b8dff1f43d4b1c8d20075510fe4
title: Manual trigger
description: Documentation for the Manual trigger node in n8n, a workflow automation platform. Includes guidance on usage, and links to examples.
title: Manual Trigger node documentation
description: Learn how to use the Manual Trigger node in n8n. Follow technical documentation to integrate Manual Trigger node into your workflows.
contentType: integration
priority: critical
---
# Manual trigger
# Manual Trigger node
Use this node if you want to start a workflow by selecting **Test Workflow**, and don't want any option for the workflow to run automatically.
Use this node if you want to start a workflow by selecting **Test Workflow** and don't want any option for the workflow to run automatically.
Workflows always need a trigger (start point). In most cases, a trigger node starts the workflow in response to an external event. However, you still need a trigger node even when starting the workflow manually.
Workflows always need a trigger, or start point. Most workflows start with a trigger node firing in response to an external event or the [Schedule Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger/) firing on a set schedule.
The Manual Trigger node serves as the workflow trigger for workflows that don't have an automatic trigger.
Use this trigger:
* To test your workflow before you add an automatic trigger of some kind.
* When you don't want the workflow to run automatically.
## Common issues
Here are some common issues/questions and suggested solutions for the Manual Trigger node.
<!-- vale off -->
### Only one 'Manual Trigger' node is allowed in a workflow
<!-- vale on -->
This error displays if you try to add a Manual Trigger node to a workflow which already includes a Manual Trigger node.
Remove your existing Manual Trigger or edit your workflow to connect that trigger to a different node.

View File

@ -18,23 +18,23 @@ Set the meta title and meta description in the frontmatter
---
#https://www.notion.so/n8n/Frontmatter-432c2b8dff1f43d4b1c8d20075510fe4
title: _Name_ trigger
description: Documentation for the _Name_ trigger node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information.
title: _Name_ Trigger node documentation
description: Learn how to use the _Name_ Trigger node in n8n. Follow technical documentation to integrate _Name_ Trigger node into your workflows.
contentType: integration
---
<!--
The title should be the name of the integration, plus "trigger". For example, "Asana trigger"
Match the brand name exactly. For example, GitHub NOT Github
The title should be the name of the integration and capitalized as it is in the UI, most often "Trigger". For example, "Asana Trigger".
Match the brand name exactly. For example, GitHub NOT Github.
-->
# _Name_ trigger
# _Name_ Trigger node
<!-- Briefly summarize the node. For example:_
Use the _Name_ trigger node to respond to events in _Name_ and integrate _Name_ with other applications. n8n has built-in support for a wide range of _Name_ events, including . . .
Use the _Name_ Trigger node to respond to events in _Name_ and integrate _Name_ with other applications. n8n has built-in support for a wide range of _Name_ events, including . . .
-->
On this page, you'll find a list of events the _Name_ trigger node can respond to, and links to more resources.
On this page, you'll find a list of events the _Name_ Trigger node can respond to, and links to more resources.
/// note | Credentials
You can find authentication information for this node [here](/integrations/builtin/credentials/_Name_/).
@ -56,10 +56,15 @@ View [example workflows and related content](https://n8n.io/integrations/_Name_/
<!-- add a link to the service's documentation. This should usually go direct to the API docs -->
Refer to [_Name_'s documentation](){:target=_blank .external-link} for details about their API.
## Common issues
<!--
Add any other sections here.
You should include: quirks, pain points, complex topics that trip people up
You should not include: basic usage examples
If the node is small enough for a single page, add a subheading here for each error, quirk, pain point, or other complex topic that might trip people up. Refer to the common_issues.md template for suggested wording.
If the node is large enough to warrant subpages, create a separate Common issues page using the common-issues.md template and link to it here using this text:
For common questions or issues and suggested solutions, refer to [Common issues](/integrations/builtin/_relativepath_).
-->

View File

@ -380,7 +380,7 @@ nav:
- integrations/builtin/core-nodes/n8n-nodes-base.limit.md
- integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger.md
- integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches.md
- integrations/builtin/core-nodes/n8n-nodes-base.manualworkflowtrigger.md
- Manual Trigger: integrations/builtin/core-nodes/n8n-nodes-base.manualworkflowtrigger.md
- integrations/builtin/core-nodes/n8n-nodes-base.markdown.md
- integrations/builtin/core-nodes/n8n-nodes-base.merge.md
- integrations/builtin/core-nodes/n8n-nodes-base.n8n.md