Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
This node interacts with the "Connect Secure" API to retrieve event tickets associated with a company. It is designed to fetch ticket data based on user-specific and query parameters, allowing users to filter, paginate, and order the results. This node is useful in scenarios where you need to integrate event ticket information from the Connect Secure platform into your workflows, such as syncing ticket data with CRM systems, generating reports, or triggering follow-up actions based on ticket details.
Practical examples:
- Retrieve all event tickets for a specific user to analyze attendance.
- Fetch a limited number of tickets ordered by date for display in a dashboard.
- Query tickets matching certain conditions (e.g., status or event type) for targeted marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User Id header value to identify the user making the request. |
| Condition | Query condition string to filter the event tickets returned by the API. |
| Skip | Number of records to skip for pagination purposes. |
| Limit | Maximum number of records to return. |
| Order By | Field(s) by which to order the returned event tickets. |
Output
The node outputs JSON data representing the retrieved event tickets. Each item in the output corresponds to an event ticket record fetched from the Connect Secure API, containing fields as defined by the API's response schema. The structure typically includes ticket details such as ticket ID, event information, user association, status, and other relevant metadata.
If the API supports binary data related to tickets (e.g., ticket PDFs or images), this node would handle it accordingly; however, based on the provided code and properties, the primary output is JSON data.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- Depends on the Connect Secure API being accessible and properly configured.
- Uses the
@devlikeapro/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled within the node for operation definitions. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Missing or invalid X USER ID: Since the user ID is required in the request header, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
- Invalid query parameters: Incorrectly formatted or unsupported values in the
condition,skip,limit, ororder_byfields may result in API errors or empty responses. Validate these inputs against the API documentation. - API connectivity issues: Network problems or incorrect API credentials can cause failures. Verify network access and credential validity.
- Empty results: If no tickets match the query conditions, the output will be empty. Adjust filters or pagination settings accordingly.
Links and References
- Connect Secure API Documentation (Replace with actual URL)
- n8n OpenAPI Node Integration Guide