Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
The node operation "List Triggers" under the "Triggers" resource is designed to retrieve a paginated list of triggers from an external service or API. This functionality is useful when you want to fetch and process multiple trigger definitions or configurations in batches, for example, to display them in a UI, synchronize with another system, or perform bulk operations.
Typical use cases include:
- Retrieving all available triggers to allow users to select one for further processing.
- Synchronizing trigger metadata from an external system into n8n workflows.
- Auditing or reporting on existing triggers by fetching their details programmatically.
Properties
| Name | Meaning |
|---|---|
| Page Number | The page number to retrieve. Starts at 0. Defaults to 0. Used for pagination control. |
| Page Size | The number of results per page. Defaults to 10. Controls how many triggers are returned. |
Output
The output of this operation is a JSON array containing trigger objects retrieved from the external service. Each item in the array represents a single trigger with its associated properties as defined by the external API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to triggers, but based on the provided code and properties, the output is purely JSON data representing trigger information.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service providing the triggers.
- The base URL for the API is expected to be set in the node credentials.
- The node uses query parameters
pageNumberandpageSizeto paginate through the list of triggers.
Troubleshooting
- Empty Results: If no triggers are returned, verify that the page number and size are correctly set and that the external service actually has triggers available.
- Authentication Errors: Ensure that the API key or authentication token is valid and has sufficient permissions to list triggers.
- Pagination Issues: Requesting a page number beyond the available range may return empty results; adjust the page number accordingly.
- Network or API Errors: Check network connectivity and API endpoint availability if requests fail.
Links and References
- Refer to the external service's API documentation for detailed information about the triggers endpoint, pagination parameters, and authentication requirements.
- n8n documentation on creating and using API credentials for secure access.