| <!-- | |
| # How to use this template | |
| 1. Make a new branch. If working on an internal ticket, include it at the start of the name. For example, DOC-123-feature-summary. | |
| 2. Create a new file, or find the file you want to edit, in integrations/builtin/trigger-nodes/. If creating a new file, pay attention to the naming conventions: it should match the node name in the codex file. For example, in the Active Campaign Trigger node, the codex file (https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/ActiveCampaign/ActiveCampaignTrigger.node.json) reads: `"node": "n8n-nodes-base.activeCampaignTrigger"`. So the app node file name is n8n-nodes-base.activeCampaignTrigger. | |
| 3. Copy the template into the file (don't copy this comment). | |
| 4. Placeholder text is in _italic_ or between <>. Make sure to replace it! | |
| 5. Before publishing, delete any comments. | |
| Use the style guide: https://github.com/n8n-io/n8n-docs/wiki | |
| You can find more info on working with the docs project in the README: https://github.com/n8n-io/n8n-docs/blob/main/README.md | |
| --> | |
| <!-- | |
| Set the meta title and meta description in the frontmatter | |
| --> | |
| --- | |
| #https://www.notion.so/n8n/Frontmatter-432c2b8dff1f43d4b1c8d20075510fe4 | |
| 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, reference] | |
| --- | |
| <!-- | |
| 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 node | |
| <!-- Briefly summarize the node. For example:_ | |
| Use the _Name_ Trigger node to respond to events in [_Name_](_service-url.com_) 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. | |
| /// note | Credentials | |
| You can find authentication information for this node [here](/integrations/builtin/credentials/_Name_.md). | |
| /// | |
| ## Events | |
| * _Bullet list_ | |
| * _Of events this node responds to_. | |
| ## Related resources | |
| <!-- provide a link to the app node docs, if there is an app node for this service --> | |
| n8n provides an app node for _Name_. You can find the node docs [here](/integrations/builtin/app-nodes/n8n-nodes-base._Name_.md). | |
| <!-- add a link to the node page on n8n's website. For example: https://n8n.io/integrations/356-gmail/ --> | |
| View [example workflows and related content](https://n8n.io/integrations/_Name_/) on n8n's website. | |
| <!-- add a link to the service's documentation. This should usually go direct to the API docs --> | |
| Refer to [_Name_'s documentation]() for details about their API. | |
| ## Common issues | |
| <!-- | |
| if the node is small enough for a single page, add the sentence below. Create a subheading below this for each error, quirk, pain point, or other complex topic that might trip people up | |
| --> | |
| Here are some common errors and issues with the _Name_ node and steps to resolve or troubleshoot them. | |
| <!-- | |
| 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/_filepath_.md). | |
| --> | |