<!--
# 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
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.
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
-->
# _Name_ trigger

<!-- 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 . . .
-->

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_/).
///

## 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_/).

<!-- 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_/){:target=_blank .external-link} 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](){:target=_blank .external-link} for details about their API.

<!-- 
Add any other sections here. 
You should include: quirks, pain points, complex topics that trip people up
You should not include: basic usage examples
-->